All of lore.kernel.org
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Xose Vazquez Perez <xose.vazquez@gmail.com>
Cc: Thomas Rosenkranz <tom.rosary@googlemail.com>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: FW: 0bda:819a RTL8188CUS WLAN doesn't work out of the box in downstream and upstreamkernel
Date: Tue, 05 Feb 2013 14:23:15 -0600	[thread overview]
Message-ID: <51116A33.9070207@lwfinger.net> (raw)
In-Reply-To: <511163BA.7060902@gmail.com>

On 02/05/2013 01:55 PM, Xose Vazquez Perez wrote:
> On 02/05/2013 12:00 AM, Thomas Rosenkranz wrote:
>
> Larry, are you able to identify the chip of that device
> with the 8192cu output ?
>
> what should he do ? open the device to see the chip ??

What difference does it make what chip it has? It is obviously some flavor of 
RTL8188CU/RTL8192CU that is different enough that it does not work with the 
kernel version of rtl8192cu. A few months ago, I ran across a new B-CUT 
RTL8188CE that took new programming for rtl8192ce, and I suspect this device 
also has the B-CUT chip.

The crash on unloading is a known fault of the vendor driver. It happens with 
devices that work OK with the standard rtl8192cu. I have no desire to find out 
what causes the crash.

If someone wants to supply me with a sample of this 0bda:819a device, I'll make 
it work in the kernel. I have no desire to try to purchase one on my own.

Larry




  reply	other threads:[~2013-02-05 20:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-04 21:41 FW: 0bda:819a RTL8188CUS WLAN doesn't work out of the box in downstream and upstreamkernel Xose Vazquez Perez
     [not found] ` <CAOAX8-k-Nbx4Om8fkEHRW2jmZCxKpsMY6oEZMAvdEQpXWn9Mdw@mail.gmail.com>
2013-02-04 23:13   ` Larry Finger
2013-02-04 23:26   ` Xose Vazquez Perez
     [not found]     ` <CAOAX8-kFtWuwEvz9v7hBzOwtohJx0NezrDHC0iVwXF29YYSCgQ@mail.gmail.com>
2013-02-05 18:33       ` Thomas Rosenkranz
2013-02-05 19:03       ` Larry Finger
     [not found]   ` <CAOAX8-mMsXu5h-7q2EJEc9SehWS=yqAb4YvbfOVBQKhdH+LqTQ@mail.gmail.com>
2013-02-05 18:36     ` Fwd: " Thomas Rosenkranz
2013-02-05 19:55   ` Xose Vazquez Perez
2013-02-05 20:23     ` Larry Finger [this message]
2013-02-05 21:18       ` Thomas Rosenkranz
2013-02-05 21:28       ` Xose Vazquez Perez
2013-02-05 21:54         ` Larry Finger
2013-02-05 22:37           ` Xose Vazquez Perez
2013-02-05 23:45             ` Larry Finger
2013-02-06  0:03               ` Xose Vazquez Perez
  -- strict thread matches above, loose matches on Subject: below --
2013-02-04 17:50 Thomas Rosenkranz
2013-02-04 19:49 ` 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=51116A33.9070207@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=tom.rosary@googlemail.com \
    --cc=xose.vazquez@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.