From: "John W. Linville" <linville@tuxdriver.com>
To: wei.li4@elf.mcgill.ca
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Wireless Linux(802.11) for Embedded PowerPC
Date: Wed, 6 Sep 2006 09:54:30 -0400 [thread overview]
Message-ID: <20060906135425.GA30051@tuxdriver.com> (raw)
In-Reply-To: <20060905160355.4f7qhwwwg80cs00s@webmail.mcgill.ca>
On Tue, Sep 05, 2006 at 04:03:55PM -0400, wei.li4@elf.mcgill.ca wrote:
> Where is the best access point for this topic? Did anyone work on this
> with MPC8xx? Thanks.
Probably netdev@vger.kernel.org. Is there anything about your wireless
needs that is specific to embedded work?
John
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2006-09-06 14:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-05 20:03 Wireless Linux(802.11) for Embedded PowerPC wei.li4
2006-09-06 13:54 ` John W. Linville [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-09-06 1:30 Chun Chung Lo
2006-09-06 13:58 ` John W. Linville
2006-09-07 1:23 Chun Chung Lo
2006-09-07 13:16 ` John W. Linville
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=20060906135425.GA30051@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=wei.li4@elf.mcgill.ca \
/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).