From: "colin" <colin@realtek.com.tw>
To: <linux-mips@linux-mips.org>
Subject: Using 802.11x wireless usb device on MIPS platform
Date: Tue, 9 Jan 2007 10:52:14 +0800 [thread overview]
Message-ID: <1cf601c73399$2ab7cd10$106215ac@realtek.com.tw> (raw)
Hi all,
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. Moreover, there is no any
wireless usb device supported.
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.
Regards,
Colin
WARNING: multiple messages have this Message-ID (diff)
From: "colin" <colin@realtek.com.tw>
To: linux-mips@linux-mips.org
Subject: Using 802.11x wireless usb device on MIPS platform
Date: Tue, 9 Jan 2007 10:52:14 +0800 [thread overview]
Message-ID: <1cf601c73399$2ab7cd10$106215ac@realtek.com.tw> (raw)
Message-ID: <20070109025214.ZnUQl3q_WMiSlVyI6UuVPy0uCMGW1B2c1e7DPExTPdI@z> (raw)
Hi all,
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. Moreover, there is no any
wireless usb device supported.
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.
Regards,
Colin
next reply other threads:[~2007-01-09 2:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-09 2:52 colin [this message]
2007-01-09 2:52 ` Using 802.11x wireless usb device on MIPS platform colin
2007-01-09 14:09 ` Ralf Baechle
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='1cf601c73399$2ab7cd10$106215ac@realtek.com.tw' \
--to=colin@realtek.com.tw \
--cc=linux-mips@linux-mips.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