From: Mark Brown <broonie@kernel.org>
To: Jean Delvare <jdelvare@suse.de>
Cc: monstr@monstr.eu, netdev@vger.kernel.org,
Nicolas Ferre <nicolas.ferre@atmel.com>,
Grant Likely <grant.likely@linaro.org>,
Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH v2] net: cadence: Add architecture dependencies
Date: Wed, 23 Apr 2014 11:04:42 +0100 [thread overview]
Message-ID: <20140423100442.GK12304@sirena.org.uk> (raw)
In-Reply-To: <20140423094010.17d2d763@endymion.delvare>
[-- Attachment #1: Type: text/plain, Size: 1246 bytes --]
On Wed, Apr 23, 2014 at 09:40:10AM +0200, Jean Delvare wrote:
> On Wed, 23 Apr 2014 09:16:49 +0200, Michal Simek wrote:
> > > Cadence are an IP company,
> I can't parse this, sorry. What is an "IP company"?
They sell designs for blocks that can be used to build hardware rather
than physical objects or complete chips and they are independant of chip
vendors. There are a number of other companies that do this, people
like Designware for example, and while ARM do obviously do architectures
they are also a generic soft IP company as well. This means that for
those companies (and sometimes others) you can't assume that just
because it's used on some architecture that doesn't mean it's used on
others.
> > > might be worth having a FPGA
> > > Kconfig that architectures commonly deployed with lots of soft IPs can
> > > select and the IPs depend on rather than building a custom list for each
> > > IP.
> What are "soft IPs"? I'm afraid I wouldn't be able to translate your
> proposal into a patch, I just don't understand what you mean exactly.
Components used in the design of hardware sold by the above companies.
Several architectures (at least ARM, Microblaze and PowerPC) are
available in chips where most of the chip is a FPGA.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2014-04-23 10:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-14 13:38 [PATCH v2] net: cadence: Add architecture dependencies Jean Delvare
2014-04-15 4:08 ` David Miller
2014-04-22 20:32 ` Mark Brown
2014-04-23 7:16 ` Michal Simek
2014-04-23 7:40 ` Jean Delvare
2014-04-23 9:35 ` Michal Simek
2014-04-23 10:48 ` Jean Delvare
2014-04-23 11:14 ` Michal Simek
2014-04-23 11:34 ` Mark Brown
2014-04-23 13:16 ` Michal Simek
2014-04-23 13:27 ` Jean Delvare
2014-04-23 14:23 ` Mark Brown
2014-04-23 11:27 ` Mark Brown
2014-04-23 10:04 ` Mark Brown [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140423100442.GK12304@sirena.org.uk \
--to=broonie@kernel.org \
--cc=grant.likely@linaro.org \
--cc=jdelvare@suse.de \
--cc=monstr@monstr.eu \
--cc=netdev@vger.kernel.org \
--cc=nicolas.ferre@atmel.com \
--cc=robh+dt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).