From: Arnd Bergmann <arnd@arndb.de>
To: Roger Quadros <roger.quadros@nokia.com>
Subject: Re: RFC: Platform data for onboard USB assets
Date: Fri, 11 Mar 2011 16:55:45 +0100
User-Agent: KMail/1.12.2 (Linux/2.6.37; KDE/4.3.2; x86_64; ; )
Cc: andy.green@linaro.org, ext Andy Green <andy@warmcat.com>,
        Linux USB list <linux-usb@vger.kernel.org>,
        lkml <linux-kernel@vger.kernel.org>
References: <4D79F068.2080009@linaro.org> <201103111622.10722.arnd@arndb.de> <4D7A44E0.5080605@nokia.com>
In-Reply-To: <4D7A44E0.5080605@nokia.com>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <201103111655.45832.arnd@arndb.de>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 851
Lines: 20

On Friday 11 March 2011, Roger Quadros wrote:
> > A udev rule would solve the problem at hand, but I'd consider that
> > an ugly workaround as well. The naming in the kernel is really
> > bogus -- any USB device that has a fixed address gets treated
> > as eth0, while others become usb0, with the same driver,
> > see the code fragment below.
> 
> but isn't that sensible? a real ethernet hardware will have a MAC
> address. no?

I have just verified with my Pandaboard that the pins on the SMSC9514
usb ethernet that are meant to be connected to a serial EEPROM are
indeed not connected anywhere.

	Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/