[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <605671F106F540BA9665A195CACB78A0@realtek.com.tw>
Date: Fri, 3 Jan 2014 10:56:02 +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: Thursday, January 02, 2014 10:25 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
>
[...]
> > +#if defined(CONFIG_USB_RTL8152) ||
> defined(CONFIG_USB_RTL8152_MODULE)
> > +/* Samsung USB Ethernet Adapters */
> > +{
> > + USB_DEVICE_AND_INTERFACE_INFO(SAMSUNG_VENDOR_ID,
> 0xa101, USB_CLASS_COMM,
> > + USB_CDC_SUBCLASS_ETHERNET, USB_CDC_PROTO_NONE),
> > + .driver_info = 0,
> > +},
> > +#endif
>
>
> We don't play the if-other-driver-is-enabled for any other of the
> blacklisted devices, including other devices supported by the RTL8152
> driver. Why do we need it here?
The USB nic have two configurations. One is the config 2 which is the ECM
mode and uses the driver of cdc_ether. The other is the config 1 which use
the driver of r8152. When the dangle is plugged, I find the configuration
is 2 and the ECM driver would be loaded. By this way, you could select
which mode you want to run. Some people would select ECM mode for
performance, and the other would select r8152 for power saving.
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/
Powered by blists - more mailing lists