[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110311152938.GB29920@sirena.org.uk>
Date: Fri, 11 Mar 2011 15:29:38 +0000
From: Mark Brown <broonie@...nsource.wolfsonmicro.com>
To: Arnd Bergmann <arnd@...db.de>
Cc: andy.green@...aro.org, Linux USB list <linux-usb@...r.kernel.org>,
lkml <linux-kernel@...r.kernel.org>
Subject: Re: RFC: Platform data for onboard USB assets
On Fri, Mar 11, 2011 at 01:31:13PM +0100, Arnd Bergmann wrote:
> I understand the problem, but IMHO there really needs to be a better
> solution for this. As far as I understand, the underlying problem is
> that USB ethernet devices with a proper MAC address get a different
> device name from devices with a generated random MAC address, and
> the people that designed this board were trying to save a few cents
> by not allocating a MAC address for the ethernet device [1], right?
> I believe we should fix this particular problem locally, instead of
> coming up with generic infrastructure for broken hardware.
It's arguable if this stuff is broken at all, from a hardware design
point of view it's perfectly reasonable and if you're shipping volumes
in the millions very small savings add up to interesting numbers easily.
> One relatively easy solution would be to allow passing a MAC address
> to this particular device driver as a module parameter, and generating
> a fixed MAC address in the regular vendor space when installing the
> boot loader. That would also solve the problem that a DHCP server
> currently assigns a new IP address to a panda board at every boot.
There's other uses for this stuff, it seems to be quite common for
various radio related things to end up hanging off USB too.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists