linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Galbraith <bitbucket@online.de>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Norbert Preining <preining@logic.at>,
	linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: dire state of rtl driver in 3.7
Date: Mon, 24 Dec 2012 05:27:49 +0100	[thread overview]
Message-ID: <1356323269.5656.43.camel@marge.simpson.net> (raw)
In-Reply-To: <50D7572E.8060908@lwfinger.net>

On Sun, 2012-12-23 at 13:10 -0600, Larry Finger wrote:

> Note, the RTL8188CE uses rtl8192ce, while the RTL8191SE uses rtl8192se. They 
> share the underlying plumbing in driver rtlwifi, but the rest is completely 
> different.

Driver here is rtl8192se.

08:00.0 0280: 10ec:8172 (rev 10)
	Subsystem: 10ec:8181
	Flags: bus master, fast devsel, latency 0, IRQ 17
	I/O ports at 4000 [size=256]
	Memory at c0900000 (32-bit, non-prefetchable) [size=16K]
	Capabilities: [40] Power Management version 3
	Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
	Capabilities: [70] Express Legacy Endpoint, MSI 00
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [140] Virtual Channel
	Capabilities: [160] Device Serial Number 88-55-22-fe-ff-4c-e0-00
	Kernel driver in use: rtl8192se

Point was, driver state may still be dire for some hardware, but here,
the same driver for very similar looking hardware went from useless to
works fine.

My desktop box has this thing in it, which also used to be completely
useless with the in kernel driver, but now works (it's still useless,
router sits on top of that box;).  Both devices now seem to work just
fine, whereas both used to be a PITA if I wanted to use them.

Bus 001 Device 004: ID 13d3:3247 IMC Networks 802.11 n/g/b Wireless LAN Adapter
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x13d3 IMC Networks
  idProduct          0x3247 802.11 n/g/b Wireless LAN Adapter
  bcdDevice            8.01
  iManufacturer           1 Ralink
  iProduct                2 802.11 n WLAN
  iSerial                 3 1.0





      reply	other threads:[~2012-12-24  4:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-22 15:09 dire state of rtl driver in 3.7 Norbert Preining
2012-12-22 16:36 ` Larry Finger
2012-12-22 22:55   ` dire state of rtl8192se " Norbert Preining
2012-12-23  1:49     ` Larry Finger
2013-01-19  3:06       ` Norbert Preining
2012-12-23  5:49 ` dire state of rtl " Mike Galbraith
2012-12-23 13:21   ` Borislav Petkov
2012-12-23 19:13     ` Larry Finger
2012-12-23 19:18       ` Borislav Petkov
2012-12-23 19:10   ` Larry Finger
2012-12-24  4:27     ` Mike Galbraith [this message]

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=1356323269.5656.43.camel@marge.simpson.net \
    --to=bitbucket@online.de \
    --cc=Larry.Finger@lwfinger.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=preining@logic.at \
    /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).