linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Chun Chung Lo <cclo@astri.org>
Cc: wei.li4@elf.mcgill.ca, linuxppc-embedded@ozlabs.org
Subject: Re: Wireless Linux(802.11) for Embedded PowerPC
Date: Thu, 7 Sep 2006 09:16:35 -0400	[thread overview]
Message-ID: <20060907131630.GA784@tuxdriver.com> (raw)
In-Reply-To: <A7B1E4DD46AA7046A4398F745240F29402737D68@ASPROEXG.astri.local>

On Thu, Sep 07, 2006 at 09:23:08AM +0800, Chun Chung Lo wrote:

> Also I cannot see any drivers existing in the upstream kernel are really
> support the "Intersil Prism 2 WLAN" cards (my card is differ from those
> Orinoco cards and Hermes cards, also the drivers are also differ a lot).

I think you may be mistaken.  The orinoco drivers in the upstream
kernel seem to support all the same device IDs as are supported
in the linux-wlan code.  If your card is missing, it is likely a
simple matter of a missing device ID.  But, major code changes are
probably not necessary.  (USB-based devices may be an exception....see
http://www.nongnu.org/orinoco/ for experimental support.)
 
> If you are going to use Intersil Prism 2 cards/chips, I would suggest
> you to use the linux-wlan driver (but seems this driver does not support
> AP mode yet...)

Please don't encourage people to patronize dead projects when the
upstream kernel should work for them.

Thanks,

John
-- 
John W. Linville
linville@tuxdriver.com

  reply	other threads:[~2006-09-07 13:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-07  1:23 Wireless Linux(802.11) for Embedded PowerPC Chun Chung Lo
2006-09-07 13:16 ` 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-05 20:03 wei.li4
2006-09-06 13:54 ` 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=20060907131630.GA784@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=cclo@astri.org \
    --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).