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: <AA7EB9EA13B74B14BBE08C4278F7948C@realtek.com.tw>
Date:	Mon, 6 Jan 2014 11:20:43 +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] 
[...]
> Sorry, but then this makes even less sense.  The active USB
> configuration is user selectable and you should make any of 
> them work if
> possible.  Why can't the drivers figure out this at runtime?

Excuse me. I have no idea about how to switch the configuration at
the runtime ,and how to change the default configuration when a
USB device is plugged. When a user select one of the configurations,
he/she would wish to fix the configuration number after rebooting or
after the dangle is unplugged and plugged again. For these reasons,
this is the simple way which I could think. Maybe I choose the wrong
method because I don't know how to satisfy the requests. May you
provide me the relative information? Then, I could replace the current
method. Thanks.

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/