On Tue, 2014-01-07 at 20:35 +0800, hayeswang wrote: > Bjørn Mork [mailto:bjorn@xxxxxxx] > > Sent: Monday, January 06, 2014 5:22 PM > > To: Hayeswang > > Cc: oliver@xxxxxxxxxx; netdev@xxxxxxxxxxxxxxx; nic_swsd; > > linux-kernel@xxxxxxxxxxxxxxx; linux-usb@xxxxxxxxxxxxxxx > > Subject: Re: [PATCH net-next v2 6/6] r8152: support RTL8153 > [...] > > Exactly the same device, but now cfg #1 is active and a > > different set of > > drivers have bound to the interfaces. This is possible > > because none of > > the involved drivers disable the support for this device at > > build-time. > > Instead they use the available interface descriptors for matching and > > probing supported functions. > > > > End users will of course normally not go around writing stuff to sysfs > > attributes like this. Creating an udev rule to select a specific > > counfiguration when the device is plugged is more useful for normal > > usage. > > Thanks for your answer. I would study udev rule first. > Does the udev alwayes exist for all Linux system, such as > Android, embedded system, and so on? They may not have udev, but if not they will normally have an alternate such as mdev. Ben. -- Ben Hutchings, Staff Engineer, Solarflare Not speaking for my employer; that's the marketing department's job. They asked us to note that Solarflare product names are trademarked. -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
