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 15:54:32 -0600 [thread overview]
Message-ID: <51117F98.3040900@lwfinger.net> (raw)
In-Reply-To: <51117994.1060506@gmail.com>
On 02/05/2013 03:28 PM, Xose Vazquez Perez wrote:
> On 02/05/2013 09:23 PM, Larry Finger wrote:
>
>> 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.
>
> We were trying to know, loading the
> _realtek_ driver, the chip of the device.
>
> *Because*, as Thomas said before, doing:
> # echo "0bda 819a" > /sys/bus/usb/drivers/rtl8192cu/new_id
> with the rtl8192cu _kernel driver_
> He got a _panic of the system_ .
>
> This is a severe bug in rtlwifi.
Yes, but not a bug for the devices that it is supposed to support! No one ever
says that their driver will support *future* devices! As I said earlier, there
are newer versions of the RTL8188C chip that requires different programming,
which may be the cause of the problem. On the other hand, the chip change did
not cause a crash in rtl8192ce. I just didn't work very well. As I have no such
device, I cannot test any changes; therefore, I will not make them. If you want
to write patches that let that device work with the kernel driver, I will be
happy to review them.
Larry
next prev parent reply other threads:[~2013-02-05 21:54 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
2013-02-05 21:18 ` Thomas Rosenkranz
2013-02-05 21:28 ` Xose Vazquez Perez
2013-02-05 21:54 ` Larry Finger [this message]
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=51117F98.3040900@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).