netdev - RE: RTL8153 fails to get link after applying c7de7dec2 to 3.8 kernel

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: <FB59F84B1E5E42AA98F0906286C444DF@realtek.com.tw>
Date:	Thu, 20 Feb 2014 12:00:46 +0800
From:	hayeswang <hayeswang@...ltek.com>
To:	'Grant Grundler' <grundler@...gle.com>
CC:	'Inki Yoo' <inky.yoo@...sung.com>,
	'netdev' <netdev@...r.kernel.org>
Subject: RE: RTL8153 fails to get link after applying c7de7dec2 to 3.8 kernel

Grant Grundler [mailto:grundler@...gle.com] 
> Sent: Thursday, February 20, 2014 8:08 AM
> To: hayeswang
> Cc: Inki Yoo; netdev
> Subject: Re: RTL8153 fails to get link after applying 
> c7de7dec2 to 3.8 kernel
> 
> On Fri, Feb 14, 2014 at 1:53 PM, Grant Grundler 
> <grundler@...gle.com> wrote:
[...]
> I will temporarily add the udev rule you previously
> posted in order to automate testing this until I can get HW that comes
> up in "vendor mode".

Excuse me if I misunderstand your meaning. Our device has two
configurations and I don't think you would get one with vendor
mode only without ECM mode. Besides, according to the information
from one of the maintainers of the kernel, when a USB device with
more than one configuration is plugged, the USB core would select
the configuration which is not vendor mode first if it exists.
Therefore, it is reasonably considered that the configuration 2
would be set by default for our device if you do nothing.

Best Regards,
Hayes

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html