| 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
| ||
|
Date: Fri, 11 Mar 2011 16:03:09 +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 04:54:03PM +0100, Arnd Bergmann wrote: > On Friday 11 March 2011, Mark Brown wrote: > > 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. > It may be reasonable if you don't expect anyone to connect the > device to an ethernet port, but in that case you could save much > more by removing the ethernet chip and the socket along with the > eeprom. > Really, any machine without a fixed MAC address is a huge pain > for users, just google for "pandaboard mac address" to see > how much work this has caused people. I'm not familiar with the Pandaboard but most of the devices I've worked with that do this have unique MAC addresses but they store in other locations on the device (typically in flash). Like I say, it's not just MAC addresses that can need configuring this way - it can be other random "you're wired up this way" type information that would normally be figured out from the USB IDs. -- 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