From: Arnd Bergmann <arnd@arndb•de>
To: Ian Molton <ian.molton@codethink•co.uk>
Cc: thomas.petazzoni@free-electrons•com, andrew@lunn•ch,
netdev@vger•kernel.org, devicetree-discuss@lists•ozlabs.org,
ben.dooks@codethink•co.uk, linuxppc-dev@lists•ozlabs.org,
David Miller <davem@davemloft•net>,
linux-arm-kernel@lists•infradead.org
Subject: Re: [PATCH v3 0/7] mv643xx.c: Add basic device tree support.
Date: Mon, 10 Sep 2012 14:22:13 +0000 [thread overview]
Message-ID: <201209101422.13875.arnd@arndb.de> (raw)
In-Reply-To: <502D201E.9030304@codethink.co.uk>
On Thursday 16 August 2012, Ian Molton wrote:
> Ping :)
>
> Can we get some consensus on the right approach here? I'm loathe to code
> this if its going to be rejected.
>
> I'd prefer the driver to be properly split so we dont have the MDIO
> driver mapping the ethernet drivers address spaces, but if thats not
> going to be merged, I'm not feeling like doing the work for nothing.
>
> If the driver is to use the overlapping-address mapped-by-the-mdio
> scheme, then so be it, but I could do with knowing.
>
> Another point against the latter scheme is that the MDIO driver could
> sensibly be used (the block is identical) on the ArmadaXP, which has 4
> ethernet blocks rather than two, yet grouped in two pairs with a
> discontiguous address range.
>
> I'd like to get this moved along as soon as possible though.
Following up on the old discussion, I talked briefly about this
issue with BenH at the kernel summit. The outcome basically is that
it's a bit sad to have incompatible bindings, but it's not the end
of the world,and it's more important to do it right this time.
Just make sure that you use different values for the 'compatible'
strings and then do what you need to get the ARM hardware working.
Ideally, the new binding should be written in a way that powerpc
machines can use the same one, but the existing ones all use
an version of Open Firmware that is not going to get updated
and it's also not too likely that we are going to see new
powerpc machines based on this chip.
Arnd
next prev parent reply other threads:[~2012-09-10 14:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1344350092-24050-1-git-send-email-ian.molton@codethink.co.uk>
[not found] ` <201208071456.41412.arnd@arndb.de>
[not found] ` <50213ACB.6040301@codethink.co.uk>
2012-08-07 20:25 ` [PATCH v3 3/7] mv643xx.c: Add basic device tree support Arnd Bergmann
[not found] ` <50223428.6030506@codethink.co.uk>
[not found] ` <502252A6.4090409@codethink.co.uk>
[not found] ` <201208081239.16778.arnd@arndb.de>
[not found] ` <50226779.6060201@codethink.co.uk>
2012-08-09 10:59 ` [PATCH v3 0/7] " Ian Molton
2012-08-09 11:43 ` Arnd Bergmann
2012-08-09 15:21 ` Ian Molton
2012-08-10 10:49 ` Arnd Bergmann
2012-08-13 10:00 ` Ian Molton
2012-08-16 16:30 ` Ian Molton
2012-09-10 14:22 ` Arnd Bergmann [this message]
2012-09-11 6:03 ` Benjamin Herrenschmidt
2012-10-21 1:52 ` Jason Cooper
2012-08-17 12:13 ` Arnd Bergmann
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=201209101422.13875.arnd@arndb.de \
--to=arnd@arndb$(echo .)de \
--cc=andrew@lunn$(echo .)ch \
--cc=ben.dooks@codethink$(echo .)co.uk \
--cc=davem@davemloft$(echo .)net \
--cc=devicetree-discuss@lists$(echo .)ozlabs.org \
--cc=ian.molton@codethink$(echo .)co.uk \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=thomas.petazzoni@free-electrons$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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