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] [day] [month] [year] [list]
Date:	Sat, 07 Jan 2012 09:42:58 -0600
From:	Larry Finger <Larry.Finger@...inger.net>
To:	Dario Lucia <dario.lucia@...il.com>
CC:	florian.c.schilhabel@...glemail.com, gregkh@...e.de,
	devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org
Subject: Re: Patch for SITECOM WLA-1000 V1 001 WLAN USB Adapter (Realtek RTL8188S)

On 01/07/2012 09:04 AM, Dario Lucia wrote:
> Dear Larry and Florian,
>
> I'm sending you this email, because you are marked as maintainers for the module
> r8712u. I had to patch it, in order to let it recognize my USB WLAN adapter from
> Sitecom (WLA-1000). Basically, I had to add the following line inside
> drivers/staging/rtl8712/usb_intf.c (line 89):
>
> {USB_DEVICE(0x0DF6, 0x005B)},
>
> Would it be possible to have the following included in the next kernel version,
> so that we don't have to patch and recompile the kernel everytime?
> I created the patch on kernel 3.1.7. The driver is working fine using the latest
> firmware from Realtek (2.6.6.0.20110401).
>
> The output I have from lsusb is the following:
>
> Bus 002 Device 005: ID 0df6:005b Sitecom Europe B.V.
> Device Descriptor:
> bLength 18
> bDescriptorType 1
> bcdUSB 2.00
> bDeviceClass 0 (Defined at Interface level)
> bDeviceSubClass 0
> bDeviceProtocol 0
> bMaxPacketSize0 64
> idVendor 0x0df6 Sitecom Europe B.V.
> idProduct 0x005b
> bcdDevice 2.00
> iManufacturer 1 Manufacturer Realtek
> iProduct 2 RTL8188S WLAN Adapter
> iSerial 3 00e04c000001
> bNumConfigurations 1
> Configuration Descriptor:
> bLength 9
> bDescriptorType 2
> wTotalLength 46
> bNumInterfaces 1
> bConfigurationValue 1
> iConfiguration 0
> bmAttributes 0x80
> (Bus Powered)
> MaxPower 500mA
> Interface Descriptor:
> bLength 9
> bDescriptorType 4
> bInterfaceNumber 0
> bAlternateSetting 0
> bNumEndpoints 4
> bInterfaceClass 255 Vendor Specific Class
> bInterfaceSubClass 255 Vendor Specific Subclass
> bInterfaceProtocol 255 Vendor Specific Protocol
> iInterface 0
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x83 EP 3 IN
> bmAttributes 2
> Transfer Type Bulk
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0200 1x 512 bytes
> bInterval 0
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x04 EP 4 OUT
> bmAttributes 2
> Transfer Type Bulk
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0200 1x 512 bytes
> bInterval 0
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x06 EP 6 OUT
> bmAttributes 2
> Transfer Type Bulk
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0200 1x 512 bytes
> bInterval 0
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x0d EP 13 OUT
> bmAttributes 2
> Transfer Type Bulk
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0200 1x 512 bytes
> bInterval 0
> Device Qualifier (for other device speed):
> bLength 10
> bDescriptorType 6
> bcdUSB 2.00
> bDeviceClass 0 (Defined at Interface level)
> bDeviceSubClass 0
> bDeviceProtocol 0
> bMaxPacketSize0 64
> bNumConfigurations 1
> Device Status: 0x0000
> (Bus Powered)
>
> The following is the output I get from dmesg, after having plugged the WLAN
> adapter in:
>
> [ 2854.704802] usb 2-1.7: new high speed USB device number 5 using ehci_hcd
> [ 2854.791717] r8712u: DriverVersion: v7_0.20100831
> [ 2854.791728] r8712u: register rtl8712_netdev_ops to netdev_ops
> [ 2854.791730] r8712u: USB_SPEED_HIGH with 4 endpoints
> [ 2854.792265] r8712u: Boot from EFUSE: Autoload OK
> [ 2855.553071] r8712u: CustomerID = 0x0000
> [ 2855.553076] r8712u: MAC Address from efuse = 00:0c:f6:b6:dd:b0
>
> I make a "ifconfig wlan0 up"
>
> [ 3006.883663] r8712u: Loading firmware from "rtlwifi/rtl8712u.bin"
> [ 3007.533552] r8712u: 1 RCR=0x153f00e
> [ 3007.534471] r8712u: 2 RCR=0x553f00e
> [ 3007.640220] ADDRCONF(NETDEV_UP): wlan0: link is not ready
>
> After configuring WPA supplicant and asked for an IP address, by running "dhcpcd
> wlan0"
>
> [ 3046.518482] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
> [ 3053.833957] r8712u: [r8712_got_addbareq_event_callback] mac =
> 00:0c:f6:be:7f:44, seq = 48, tid = 0
> [ 3057.336367] wlan0: no IPv6 routers present
>
> Iwconfig shows:
>
> wlan0 IEEE 802.11bgn ESSID:"WirelessLanDL" Nickname:"rtl_wifi"
> Mode:Managed Frequency:2.412 GHz Access Point: 00:0C:F6:BE:7F:44
> Bit Rate:150 Mb/s Sensitivity:0/0
> Retry:off RTS thr:off Fragment thr:off
> Encryption key:****-****-****-****-****-****-****-**** Security mode:open
> Power Management:off
> Link Quality=100/100 Signal level=73/100 Noise level=0/100
> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> Tx excessive retries:0 Invalid misc:0 Missed beacon:0
>
> Ifconfig shows:
>
> wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 metric 1
> inet 192.168.0.102 netmask 255.255.255.0 broadcast 192.168.0.255
> inet6 fe80::20c:f6ff:feb6:ddb0 prefixlen 64 scopeid 0x20<link>
> ether 00:0c:f6:b6:dd:b0 txqueuelen 1000 (Ethernet)
> RX packets 17 bytes 5850 (5.7 KiB)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 14 bytes 2013 (1.9 KiB)
> TX errors 0 dropped 2 overruns 0 carrier 0 collisions 0
>
> That's it. I apologize in case you already received a patch for this.

I have not seen such a patch, but yours is not quite in the right format. I'll 
reformat it and send it upstream as soon as possible with a notation to be 
applied to stable. Once the patch hits the mainline kernel, it will then be back 
propagated.

Larry


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

Powered by Openwall GNU/*/Linux Powered by OpenVZ