From: "John W. Linville" <linville@tuxdriver.com>
To: Hin-Tak Leung <hintak.leung@gmail.com>
Cc: "Larry Finger" <Larry.Finger@lwfinger.net>,
"Gábor Stefanik" <netrolller.3d@gmail.com>,
"Luis R. Rodriguez" <mcgrof@gmail.com>,
"Tobias Schlemmer" <keinstein_junior@gmx.net>,
linux-wireless@vger.kernel.org, greg@kroah.com
Subject: Re: rtl8187b Problem with tx level
Date: Tue, 1 Sep 2009 09:13:33 -0400 [thread overview]
Message-ID: <20090901131333.GA7650@tuxdriver.com> (raw)
In-Reply-To: <3ace41890908311616k4040d59fub051d21e822604d0@mail.gmail.com>
On Tue, Sep 01, 2009 at 12:16:04AM +0100, Hin-Tak Leung wrote:
> 2009/8/31 Larry Finger <Larry.Finger@lwfinger.net>:
> > Gábor Stefanik wrote:
> >>
> >> The driver is not actually closed-source; they just don't provide any
> >> drivers on their site anymore, instead they send their reference
> >> drivers to OEMs, expecting the OEMs to release their own versions
> >> (with sources - most vendors who do release Linux drivers in fact only
> >> release sources, without binaries). The reason for this appears to be
> >> that Realtek now encourages vendors to sell RTL81xx wireless chips
> >> with modified USB IDs. (Or are you seeing a binary-only driver on
> >> realtek.com.tw? That would definitely be a GPL violation, given that
> >> they use a modified version of the GPLed libipw stack.)
> >
> >
> > No driver at all. I looked at the Toshiba site, but found only Windows
> > drivers. Which OEM has the driver available?
> >
> > Larry
>
> The r8187 is distributed from OEMs - stand to reason, as realtek don't
> really sell their own brand on high-street shops? We got one release
> e-mailed to us, and there are a few floating around on the internet
> under some laptop or usb hardware vendors. It is available under this,
> for example: http://service.one.de/index.php?&direction=0&order=&directory=NOTEBOOKS/ONE_A1XX/LINUX/Source-code/Wireless
> r8187mesh is the one in the mesh directory.
*sigh*
So Realtek is actually going backwards in their level of support?
Wonderful.
Anyone have any real-life contacts at Realtek? We really need to
get them on-board with the drivers in the kernel.
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2009-09-01 13:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-30 20:44 rtl8187b Problem with tx level Tobias Schlemmer
2009-08-30 23:00 ` Larry Finger
2009-08-31 9:59 ` Tobias Schlemmer
2009-08-31 15:49 ` Larry Finger
2009-08-31 16:51 ` Tobias Schlemmer
2009-08-31 17:55 ` Hin-Tak Leung
2009-08-31 18:02 ` Luis R. Rodriguez
2009-08-31 18:32 ` Hin-Tak Leung
2009-08-31 18:41 ` Luis R. Rodriguez
2009-08-31 18:57 ` Hin-Tak Leung
2009-08-31 21:10 ` Larry Finger
2009-08-31 21:18 ` Gábor Stefanik
2009-08-31 21:38 ` Larry Finger
2009-08-31 23:16 ` Hin-Tak Leung
2009-09-01 13:13 ` John W. Linville [this message]
2009-09-01 16:37 ` Larry Finger
2009-09-02 10:28 ` Hin-Tak Leung
2009-08-31 23:37 ` Luis R. Rodriguez
2009-08-31 23:46 ` Gábor Stefanik
2009-08-31 23:56 ` Luis R. Rodriguez
2009-09-01 0:21 ` Greg KH
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=20090901131333.GA7650@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=Larry.Finger@lwfinger.net \
--cc=greg@kroah.com \
--cc=hintak.leung@gmail.com \
--cc=keinstein_junior@gmx.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
--cc=netrolller.3d@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).