From: Grant Erickson <gerickson@nuovations.com>
To: Stefan Roese <sr@denx.de>, <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH v2] Parameterize EMAC Multicast Match Handling
Date: Tue, 01 Jul 2008 11:13:08 -0700 [thread overview]
Message-ID: <C48FC1C4.10254%gerickson@nuovations.com> (raw)
In-Reply-To: <200807010837.45282.sr@denx.de>
On 6/30/08 11:37 PM, Stefan Roese wrote:
> On Tuesday 01 July 2008, Benjamin Herrenschmidt wrote:
>>> Stefan and/or Ben:
>>>
>>> Any thoughts on this?
>>
>> I was hesitating a bit... do we really need to be -that- flexible ?
>>
>> That is, either that or use some new compatible entry to detect the new
>> reg layout and whack that as a feature bit instead ? The advantage
>> of the later is that we have the possibility of doing conditional
>> compile for kernels that support only a given processor or set of
>> processors (not that we have implemented much of it, but it just
>> becomes Kconfig mumbo jumbo and a little bit of defines in the .h
>> by turning the feature test into a compile-time 0 or 1.
>>
>> But this isn't a hot path and not a lot of code so maybe not worth
>> bothering... however, it does add 3 properties to the DT and I know
>> embedded people (especially Xilinx) are a bit concerned about the size
>> of the DT when they try to fit it in block RAM...
>
> Yes, this was my feeling too. Not the size of the dtb but more the increased
> complexity of the EMAC device node. I would prefer Ben's idea with this new
> compatible entry too.
In terms of the device tree expression, you would both favor something akin
to the following?
- compatible = "ibm,emac-405exr", "ibm,emac4";
+ compatible = "ibm,emac-405exr", "ibm,emac4", "ibm,emac4sync";
Regards,
Grant
next prev parent reply other threads:[~2008-07-01 18:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-25 0:08 [PATCH v2] Parameterize EMAC Multicast Match Handling Grant Erickson
2008-07-01 5:26 ` Grant Erickson
2008-07-01 6:14 ` Benjamin Herrenschmidt
2008-07-01 6:37 ` Stefan Roese
2008-07-01 18:13 ` Grant Erickson [this message]
2008-07-01 19:42 ` Stefan Roese
2008-07-01 23:52 ` Benjamin Herrenschmidt
2008-07-05 9:18 ` [PATCH v3] ibm_newemac: " Grant Erickson
2008-07-05 22:45 ` Benjamin Herrenschmidt
2008-07-06 0:15 ` [PATCH v4] " Grant Erickson
2008-07-06 0:31 ` Benjamin Herrenschmidt
2008-07-06 9:43 ` Stefan Roese
2008-07-06 23:30 ` [PATCH v5] " Grant Erickson
2008-07-07 5:58 ` Stefan Roese
2008-07-07 6:00 ` Benjamin Herrenschmidt
2008-07-07 6:29 ` Stefan Roese
2008-07-07 6:43 ` Benjamin Herrenschmidt
2008-07-07 6:18 ` Benjamin Herrenschmidt
2008-07-07 13:59 ` Jeff Garzik
2008-07-07 19:50 ` Valentine Barshak
2008-07-07 22:02 ` Grant Erickson
2008-07-07 22:03 ` [PATCH v6] " Grant Erickson
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=C48FC1C4.10254%gerickson@nuovations.com \
--to=gerickson@nuovations.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=sr@denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.