[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 7 Aug 2012 19:31:41 -0500
From: Matt Sealey <matt@...esi-usa.com>
To: David Miller <davem@...emloft.net>
Cc: ian.molton@...ethink.co.uk, thomas.petazzoni@...e-electrons.com,
andrew@...n.ch, arnd@...db.de, netdev@...r.kernel.org,
ben.dooks@...ethink.co.uk, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v3 0/7] mv643xx.c: Add basic device tree support.
On Tue, Aug 7, 2012 at 6:29 PM, David Miller <davem@...emloft.net> wrote:
> From: Ian Molton <ian.molton@...ethink.co.uk>
> Date: Tue, 7 Aug 2012 15:34:45 +0100
>
>> Fixed all comments.
>>
>> * Dropped csb1724 defconfig.
>> * Added patch to remove MV643XX_ETH_SHARED_NAME and MV643XX_ETH_NAME
>> * Dropped un-necessary D-T irq fixup code
>
> Who is going to take this series?
Would anyone mind too much if I *didn't* break out a Pegasos II and
test it? Our platform has a Marvell northbridge (Discovery II)
implementing this, with a Marvell PHY, and it's OpenFirmware (as in,
REAL OpenFirmware) so the device tree isn't about to change to fit new
bindings. But I'm not sure we even have one in the office that boots
anymore.. there may be users out there but they're well beyond
warranty support (early 2005 or so was the last time we sold one).
If anyone needs the original device tree entries to compare and
contrast I may be able to provide them such that any parsing and
initializing of the driver take into account this old
board/northbridge/implementation. I'm just curious if anyone cares
enough..
--
Matt Sealey <matt@...esi-usa.com>
Product Development Analyst, Genesi USA, Inc.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists