From: Ralf Baechle <ralf@linux-mips.org>
To: colin <colin@realtek.com.tw>
Cc: linux-mips@linux-mips.org, netdev@vger.kernel.org
Subject: Re: Using 802.11x wireless usb device on MIPS platform
Date: Tue, 9 Jan 2007 14:09:31 +0000 [thread overview]
Message-ID: <20070109140931.GB6614@linux-mips.org> (raw)
In-Reply-To: <1cf601c73399$2ab7cd10$106215ac@realtek.com.tw>
On Tue, Jan 09, 2007 at 10:52:14AM +0800, colin wrote:
> I have used two 802.11x wireless usb devices successfully on MIPS platform.
> One is realtek 8187 and the other one is ralink 2571.
> I would like to put them into kernel tree and then I found that there are
> not many 802.11x devices supported in Linux.
If you want to submit a driver to the kernel, please post it to
netdev@vger.kernel.org. Don't expect a driver to be just accepted; it
will go through a thorough review and after all the issues have been
resolved it will be accepted.
> Moreover, there is no any wireless usb device supported.
Wireless support under Linux is suffering from several problems:
o some core require microcode to be loaded but the vendor does not
give such permission.
o lack of documentation, sometimes for paranoid or bogus legal reasons or
"intellectual property" concerns.
At times it really seems vendors are working to maximize pain for the user ...
> It is also very strange that 8187 and 2571 both have their own ieee802.11x
> stack and crypt drivers. It seems that Linux doesn't offer them.
> I am wondering why Linux is so complex in 802.11x.
Well, for one thing because 802.11 is complex. The Linux wireless support
has gone through several generations; some of the wireless work was for
one or the other reason never integrated in the kernel.org kernel.
Ralf
next parent reply other threads:[~2007-01-09 14:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1cf601c73399$2ab7cd10$106215ac@realtek.com.tw>
2007-01-09 14:09 ` Ralf Baechle [this message]
2007-01-09 18:52 ` Using 802.11x wireless usb device on MIPS platform Michael Wu
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=20070109140931.GB6614@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=colin@realtek.com.tw \
--cc=linux-mips@linux-mips.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).