From: Maxime Bizon <mbizon@freebox.fr>
To: Florian Fainelli <florian@openwrt.org>
Cc: David Miller <davem@davemloft.net>,
netdev@vger.kernel.org, ralf@linux-mips.org,
John Crispin <blogic@openwrt.org>,
Linux-MIPS <linux-mips@linux-mips.org>,
jogo@openwrt.org, Kevin Cernekee <cernekee@gmail.com>
Subject: Re: [PATCH net-next] bcm63xx_enet: add support Broadcom BCM6345 Ethernet
Date: Thu, 13 Jun 2013 16:24:07 +0200 [thread overview]
Message-ID: <1371133447.3032.37.camel@sakura.staff.proxad.net> (raw)
In-Reply-To: <CAGVrzcaqbdLPcuL0m56aBLuG9ruaQ1p4JfTWZV9DJ4zSrNcXtg@mail.gmail.com>
On Thu, 2013-06-13 at 10:49 +0100, Florian Fainelli wrote:
> We are in the slow process to switch to Device Tree to precisely
> eliminate all of this (although not everyone agrees yet on the
> details). Hopefully you should not see such things in the future.
I don't see how DT help here (hint: it never does)
if the driver knows at compile time how registers are shuffled, it can
remove the indirection
if you use runtime cpu detection or DT, it cannot
in fact, this patch already adds another layer of indirection with that
"dma_chan_width" thing that the compiler has no way to optimize out,
defeating the purpose of single SOC optimization.
so we might as well force multi SOC support
--
Maxime
prev parent reply other threads:[~2013-06-13 14:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-12 19:53 [PATCH net-next] bcm63xx_enet: add support Broadcom BCM6345 Ethernet Florian Fainelli
2013-06-13 8:44 ` David Miller
[not found] ` <CAGVrzcYE4VDWtL_Uj1DrkZ6GqX6ghqPAXPpyLptc6PGwReixSQ@mail.gmail.com>
2013-06-13 9:25 ` David Miller
2013-06-13 9:49 ` Florian Fainelli
2013-06-13 9:55 ` Florian Fainelli
2013-06-13 9:56 ` David Miller
2013-06-13 13:59 ` Ralf Baechle
2013-06-14 0:22 ` David Miller
2013-06-13 14:24 ` Maxime Bizon [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=1371133447.3032.37.camel@sakura.staff.proxad.net \
--to=mbizon@freebox.fr \
--cc=blogic@openwrt.org \
--cc=cernekee@gmail.com \
--cc=davem@davemloft.net \
--cc=florian@openwrt.org \
--cc=jogo@openwrt.org \
--cc=linux-mips@linux-mips.org \
--cc=netdev@vger.kernel.org \
--cc=ralf@linux-mips.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).