linux-kernel - RE: [PATCH net-next v2 6/6] r8152: support RTL8153

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: <749DBDC9792E47BBA5884BEC7CF2D639@realtek.com.tw>
Date:	Tue, 7 Jan 2014 20:35:54 +0800
From:	hayeswang <hayeswang@...ltek.com>
To:	'Bjørn Mork' <bjorn@...k.no>
CC:	<oliver@...kum.org>, <netdev@...r.kernel.org>,
	'nic_swsd' <nic_swsd@...ltek.com>,
	<linux-kernel@...r.kernel.org>, <linux-usb@...r.kernel.org>
Subject: RE: [PATCH net-next v2 6/6] r8152: support RTL8153

 Bjørn Mork [mailto:bjorn@...k.no] 
> Sent: Monday, January 06, 2014 5:22 PM
> To: Hayeswang
> Cc: oliver@...kum.org; netdev@...r.kernel.org; nic_swsd; 
> linux-kernel@...r.kernel.org; linux-usb@...r.kernel.org
> 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?
 
Best Regards,
Hayes

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