Hi,
Would you be interested in Power Lunix users for your email marketing campaign? We provide the Database across North America, EMEA, APAC and Latin America.
We can provide you with titles of Decision Makers regarding the technology.
We also have other technology users like
SUSE
Red Hat
CELAD
Tanner EDA
Callabora
iXsystem
Linaro and many more…
List Contains: Name, Company's Name, Phone Number, Fax Number, Job Title, Email address, Complete Mailing Address, SIC code, Company revenue, size, Web address etc.
We offer:
Complete list with Email address in an Excel Sheet for unlimited usage.
Do an email blast endorsing your product/services and providing your contact information.
Email appending, multiple contacts appending, Data appending which will append or add the
missing information to your existing database.
Let me know your thoughts or pass on the message to the right person in your company.
Thanks & regards,
JaniceWhite
Information Specialist
If you don’t want to receive any message from us then please type “Leave Out” in the Subject Line.
Good day to all,
The CS specification defines replicators that are not showing on the
AMBA bus and can't be configured - they simply provide a hard wire
between components. Earlier this week someone wrote to me on the open
mailing list asking for guidance in dealing with a new type of funnel
their company has introduced in a design. Just like a replicator it
doesn't show up on the AMBA bus and can't be configured.
It makes sense to deal with this new component the same way we do with
the above-mentioned replicator, i.e use a platform driver that does
nothing and add it to the CS topology when specified in the device
tree. It also make sense to re-use the same code [1] for that.
But moving forward with this also means we need to re-brand the
current coresight-replicator.c file, along with adding new
"compatible" strings. Here is what I suggest:
1) Keep the "arm,coresight-replicator" compatible string for backward
compatibility (I'm seriously tempted not to [2]).
2) Add a new "arm,coresight-hw-replicator" compatible string for
replicators that don't show up on the AMBA bus.
3) Add a new "arm,coresight-hw-funnel" compatible string for funnels
that don't show up on the AMBA bus.
4) Use a match table to deal with the above two new compatible string
and the old one (if we keep it around).
5) Rename coresight-replicator.c to coresight-hw-link.c.
I'm reaching out to the list because once we have a naming convention
it is hard to modify it. Let me know what you think of the above.
Thanks,
Mathieu
[1]. https://elixir.bootlin.com/linux/latest/source/drivers/hwtracing/coresight/…
[2]. We could also delete the old "arm,coresight-replicator" and make
the changes in the DT for current users. People that haven't upstream
their in-house solution will have to adapt, but that's something that
happens with all the out-of-tree code.
Hi Zhi,
On 7 March 2018 at 08:57, Zhi Li <lznuaa(a)gmail.com> wrote:
> Mathieu:
>
> I am working one enable coresight in our SOC.
>
> But our SOC's cluster funnel have not export program interface.
> Our cluster included 4 A53.
>
> 4 ETM of A53 connect to funnel, which have NOT program
> interface. Funnel is default enabled.
>
> Do you have suggest how to bypass or use dummy funnel in dts file?
Is the funnel discoverable on the AMBA bus or is it like the original
version of replicators?
>
>
> best regards
> Frank Li
