From: Anders Larsen <al@alarsen.net>
To: Chris Ward <tjcw@cantab.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux device driver for USB WIFI needs integrating
Date: Fri, 24 Apr 2015 14:25:41 +0200 [thread overview]
Message-ID: <1429878341.6780.2@alarsen-lx> (raw)
In-Reply-To: <ceef3d114ec27f0f66dac23dbbcabf3b.squirrel@wm.sdf.org> (from tjcw@cantab.net on Fri Apr 24 13:59:26 2015)
[-- Attachment #1: Type: text/plain, Size: 553 bytes --]
On 2015-04-24 13:59, Chris Ward wrote:
> lsusb shows
> Bus 003 Device 024: ID 0b05:17ba ASUSTek Computer, Inc.
OK, thanks
> I've just built the OpenSUSE kernel from source, it has that CONFIG=m
> .
> I think ASUS have changed the chip set.
only the USB id AFAICT - 0b05:17ab is supported
> Do we have to wait for ASUS to debug their driver ? Supposedly it
> worked
> with an older kernel (up to 3.10 I think)
does the attached trivial patch help?
(it should make the in-tree driver recognise your ASUS device)
Cheers
Anders
[-- Attachment #2: 0001-rtlwifi-rtl8192cu-Add-USB-id-for-ASUS-USB-N10-NANO.patch --]
[-- Type: text/x-patch, Size: 1232 bytes --]
=46rom 2d7ede77347f9e2f00b248839961b3da311a27fa Mon Sep 17 00:00:00 2001
From: Anders Larsen <al@alarsen.net>
Date: Fri, 24 Apr 2015 14:17:33 +0200
Subject: [PATCH] rtlwifi/rtl8192cu: Add USB id for ASUS USB-N10 NANO
"ASUS USB-N10 NANO" wifi adapter USB id: 0b05:17ba
Signed-off-by: Anders Larsen <al@alarsen.net>
---
drivers/net/wireless/rtlwifi/rtl8192cu/sw.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/net/wireless/rtlwifi/rtl8192cu/sw.c b/drivers/net/wireless/rtlwifi/rtl8192cu/sw.c
index 1ac6383..77c4b62 100644
--- a/drivers/net/wireless/rtlwifi/rtl8192cu/sw.c
+++ b/drivers/net/wireless/rtlwifi/rtl8192cu/sw.c
@@ -364,6 +364,7 @@ static struct usb_device_id rtl8192c_usb_ids[] = {
{RTL_USB_DEVICE(0x0846, 0x9021, rtl92cu_hal_cfg)}, /*Netgear-Sercomm*/
{RTL_USB_DEVICE(0x0846, 0xf001, rtl92cu_hal_cfg)}, /*On Netwrks N300MA*/
{RTL_USB_DEVICE(0x0b05, 0x17ab, rtl92cu_hal_cfg)}, /*ASUS-Edimax*/
+ {RTL_USB_DEVICE(0x0b05, 0x17ba, rtl92cu_hal_cfg)}, /*ASUS-Edimax N10 nano*/
{RTL_USB_DEVICE(0x0bda, 0x8186, rtl92cu_hal_cfg)}, /*Realtek 92CE-VAU*/
{RTL_USB_DEVICE(0x0df6, 0x0061, rtl92cu_hal_cfg)}, /*Sitecom-Edimax*/
{RTL_USB_DEVICE(0x0e66, 0x0019, rtl92cu_hal_cfg)}, /*Hawking-Edimax*/
--
2.3.6
next prev parent reply other threads:[~2015-04-24 12:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-24 10:37 Linux device driver for USB WIFI needs integrating Chris Ward
2015-04-24 11:14 ` Anders Larsen
2015-04-24 11:42 ` Chris Ward
2015-04-24 11:44 ` Chris Ward
2015-04-24 11:59 ` Chris Ward
2015-04-24 12:25 ` Anders Larsen [this message]
2015-04-24 14:01 ` Anders Larsen
2015-04-24 17:31 ` Chris Ward
2015-04-26 14:04 ` Anders Larsen
2015-04-27 8:38 ` Chris Ward
2015-04-27 12:51 ` Anders Larsen
2015-04-27 13:52 ` Chris Ward
2015-04-27 13:58 ` Chris Ward
2015-04-27 14:04 ` Chris Ward
2015-04-27 14:23 ` Chris Ward
2015-04-27 14:49 ` Anders Larsen
2015-04-27 16:19 ` Marek Vasut
2015-05-03 19:40 ` Anders Larsen
-- strict thread matches above, loose matches on Subject: below --
2015-04-24 11:01 Chris Ward
[not found] <CAC=wTOgLstw60bq5xiXCw4PKzqDxxPNvdTUUsvHbsQJdSOy+kg@mail.gmail.com>
2015-04-24 11:49 ` Anders Larsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1429878341.6780.2@alarsen-lx \
--to=al@alarsen.net \
--cc=linux-kernel@vger.kernel.org \
--cc=tjcw@cantab.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox