Re: RFC: Platform data for onboard USB assets

Andy Green
2011-03-23T12:02:45Z

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