From: "Stefan Lippers-Hollmann" <s.L-H@gmx.de>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rtl8192cu: add USB ID for Belkin n300 Micro USB wireless adapter
Date: Wed, 3 Aug 2011 00:35:48 +0200 [thread overview]
Message-ID: <201108030035.50214.s.L-H@gmx.de> (raw)
In-Reply-To: <4E386FB9.2040507@lwfinger.net>
Hi
On Wednesday 03 August 2011, Larry Finger wrote:
> On 08/02/2011 03:43 PM, Stefan Lippers-Hollmann wrote:
> > On Tuesday 02 August 2011, Stefan Lippers-Hollmann wrote:
[...]
> >> + {RTL_USB_DEVICE(0x050D, 0x2103, rtl92cu_hal_cfg)}, //Belkin - Edimax
Sorry about the C++ style comments, I meant to fix it, but forgot about
it in the end.
[...]
> > [1] http://aptosid.com/index.php?name=PNphpBB2&file=viewtopic&t=1550&start=0
> > [2] http://pastebin.com/ppZJ0GmU
>
> I have been holding a few new ID's that are in the vendor driver awaiting a
> test. These include the following:
>
> + {RTL_USB_DEVICE(USB_VENDER_ID_REALTEK, 0x817f, rtl92cu_hal_cfg)},
> + {RTL_USB_DEVICE(0x13d3, 0x3357, rtl92cu_hal_cfg)}, /* AzureWave */
> + {RTL_USB_DEVICE(0x13d3, 0x3358, rtl92cu_hal_cfg)}, /*Azwave 8188CE-VAU*/
> - {RTL_USB_DEVICE(0x3359, 0x13d3, rtl92cu_hal_cfg)},
> + {RTL_USB_DEVICE(0x13d3, 0x3359, rtl92cu_hal_cfg)},
> + {RTL_USB_DEVICE(0x4855, 0x0090, rtl92cu_hal_cfg)}, /* Feixun */
> + {RTL_USB_DEVICE(0x4855, 0x0091, rtl92cu_hal_cfg)}, /* NetweeN-Feixun */
> + {RTL_USB_DEVICE(0x9846, 0x9041, rtl92cu_hal_cfg)}, /* Netgear Cameo */
> + {RTL_USB_DEVICE(0x050d, 0x2102, rtl92cu_hal_cfg)}, /*Belkin-Sercomm*/
> + {RTL_USB_DEVICE(0x050d, 0x2103, rtl92cu_hal_cfg)}, /*Belkin-Edimax*/
>
> The deleted entry has the vendor and product reversed. The first one in the list
> has been tested and works.
>
> Based on your report, I will drop the 050d entries. If you get a confirmation
> that 050d,2103 works, then submit that patch.
I have now asked the reporter to check the state of rtl8192cu again,
current state is (with a kernel including my original patch):
- functionality confirmed on an unencrypted network
- WPA2-psk not conclusively tested, it may be out of range for his device.
("EDIT: With my netbook I can get an IP address and use the neighbor's
unsecured network. Also, the Belkin device reports it at -47 dBm
signal strength, but my Toshiba netbook gives it -80 to -83 (which
may explain why the Belkin couldn't get an IP address), so there are
still some issues to sort.")
- no Oops if his USB ID is compiled into the module, that only happens
if he tries to inject it into an unpatched kernel with:
echo -n "050d 2103"> /sys/bus/usb/drivers/rtl8192cu/new_id
(and I'm reluctant to raise this as potential issue completely, due
to the tainted kernel condition on his system).
Hopefully he'll answer my further inquiries about the stability of his
Belkin n300 Micro USB soon.
Regards
Stefan Lippers-Hollmann
next prev parent reply other threads:[~2011-08-02 22:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-02 20:29 Stefan Lippers-Hollmann
2011-08-02 20:43 ` Stefan Lippers-Hollmann
2011-08-02 21:44 ` Larry Finger
2011-08-02 22:35 ` Stefan Lippers-Hollmann [this message]
2011-08-02 23:06 ` Larry Finger
2011-08-02 23:20 ` Stefan Lippers-Hollmann
2011-08-02 23:46 ` Larry Finger
2011-08-02 21:42 ` Larry Finger
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=201108030035.50214.s.L-H@gmx.de \
--to=s.l-h@gmx.de \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
/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
all inboxes | Powered by JetHome®