linux-kernel - Re: RFC: Platform data for onboard USB assets

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <201103111655.45832.arnd@arndb.de>
Date:	Fri, 11 Mar 2011 16:55:45 +0100
From:	Arnd Bergmann <arnd@...db.de>
To:	Roger Quadros <roger.quadros@...ia.com>
Cc:	andy.green@...aro.org, ext Andy Green <andy@...mcat.com>,
	Linux USB list <linux-usb@...r.kernel.org>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: RFC: Platform data for onboard USB assets

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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/