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 for Android: free password hash cracker in your pocket

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

Date:	Wed, 23 Mar 2011 12:02:39 +0000
From:	Andy Green <andy@...mcat.com>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
CC:	Arnd Bergmann <arnd@...db.de>,
	Benjamin Herrenschmidt <benh@...nel.crashing.org>,
	Nicolas Pitre <nicolas.pitre@...aro.org>,
	Jaswinder Singh <jaswinder.singh@...aro.org>,
	Linux USB list <linux-usb@...r.kernel.org>,
	lkml <linux-kernel@...r.kernel.org>,
	broonie@...nsource.wolfsonmicro.com, roger.quadros@...ia.com,
	greg@...ah.com, grant.likely@...retlab.ca
Subject: Re: RFC: Platform data for onboard USB assets

On 03/23/2011 11:34 AM, Somebody in the thread at some point said:
>> business to know, but that the usb device on the specific wired-up USB
>> port to the RJ45 soldered on the board should be guided a particular way
>> when the interface name is registered.  That can only be done properly
>> in-kernel by passing in a flag to usbnet specific to the device instance
>> to guide its choice.
>
> To my mind the MAC case is a bit different to the name case. It's really
> not about policy in that situation it's a USB widget with a non standard
> "retrieve mac address" method.
>
> You could fix it up in user space from firmware tables, or in either from
> looking in your device tree.
>
> There is one way you could actually hide all this in your board specific
> gunge at the moment without touching the core kernel I think. Take a look
> at how register_netdev_notifier() works.
>
> That will give you a NETDEV_REGISTER event for each device being
> registered so you can then pick out your usb network device.
>
> It might need some slightly unclean knowledge of the usb net driver in
> your glue but in the short term until there is a nice device tree type
> answer it would allow you to get your MAC address set up properly I
> think ?

Sounds like a good way...  it's register_netdevice_notifier().

I'll study this and try adapt the patches accordingly.

Thanks a lot for this hint.

-Andy

--
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/