netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michal Simek <monstr@monstr.eu>
To: Jean Delvare <jdelvare@suse.de>
Cc: Mark Brown <broonie@kernel.org>,
	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:35:55 +0200	[thread overview]
Message-ID: <5357897B.6020105@monstr.eu> (raw)
In-Reply-To: <20140423094010.17d2d763@endymion.delvare>

[-- Attachment #1: Type: text/plain, Size: 1983 bytes --]

On 04/23/2014 09:40 AM, Jean Delvare wrote:
> Hi Mark, Michal,
> 
> On Wed, 23 Apr 2014 09:16:49 +0200, Michal Simek wrote:
>> On 04/22/2014 10:32 PM, Mark Brown wrote:
>>> On Mon, Apr 14, 2014 at 03:38:49PM +0200, Jean Delvare wrote:
>>>> The Cadence ethernet chipsets are only used on specific ARM
>>>> architectures. Add Kconfig dependencies so that drivers for these
>>>> chipsets are only buildable on the relevant architectures.
>>>
>>> Are you sure they're not used on any of the FPGA platforms like
>>> Microblaze?
> 
> I'm not sure of anything, embedded isn't my area.
> 
>>> Cadence are an IP company,
> 
> I can't parse this, sorry. What is an "IP company"?

Company which is creating this piece of HW which is called IP.


>>> 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.

Microblaze is soft-core cpu or soft IP if you like. It means it is written
in VHDL/Verilog or in different hardware description language.

>> macb driver can be used by Microblaze too.
> 
> Thanks for the information. I will send a patch adding MICROBLAZE to
> the dependencies. Out of curiosity, is there any way I could have found
> out by myself?

Microblaze doesn't need to be only one. I am not sure if there is
any AXI bridge for openrisc.
IMHO you should just add COMPILE_TEST and do not try to extend that
list of dependencies.

Thanks,
Michal

-- 
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
Maintainer of Linux kernel - Xilinx Zynq ARM architecture
Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]

  reply	other threads:[~2014-04-23  9:36 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 [this message]
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

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=5357897B.6020105@monstr.eu \
    --to=monstr@monstr.eu \
    --cc=broonie@kernel.org \
    --cc=grant.likely@linaro.org \
    --cc=jdelvare@suse.de \
    --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).