linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Pavel Roskin <proski@gnu.org>
Cc: Balaji Rao <balajirrao@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: Question on Wireless NICs
Date: Thu, 27 Mar 2008 11:58:42 -0400	[thread overview]
Message-ID: <20080327155842.GA3624@tuxdriver.com> (raw)
In-Reply-To: <1206498769.23595.6.camel@dv>

On Tue, Mar 25, 2008 at 10:32:48PM -0400, Pavel Roskin wrote:
> On Tue, 2008-03-25 at 15:32 -0400, John W. Linville wrote:
> 
> > The gPXE (formerly etherboot) project seems to support PCI-based
> > (e.g. cardbus, but not PCMCIA) orinoco devices.  I cannot verify that,
> > since I have no such device (donations accepted!)...
> 
> Just to set the record straight, I'm unaware of any CardBus devices
> compatible with the orinoco driver, i.e. Prism 2-3, Symbol Trilogy or
> Hermes I based 802.11b device.
> 
> At the first glance, gPXE appears to support Prism chipset only, either
> native PCI or PCMCIA behind PLX9052 bridge.

I'm not sure where you are looking.  I have a git tree from here:

	git://git.etherboot.org/scm/gpxe.git

The gpxe source file src/drivers/net/prism2_pci.c claims to support
PCI ID 1260:3873 which is listed as a prism 2.5 device supported by
drivers/net/wireless/orinoco_pci.c in the linux tree.  Similarly the
gpxe src/drivers/net/prism2_plx.c claims to support all of the PCI IDs
listed in drivers/net/wireless/orinoco_plx.c from the linux tree as
well as one that is not listed there (126c:8030 -- perhaps we should
add it?).

As I said, I do not have _any_ pci-based prism2-3 hardware (donations
welcome!), so I can not verify whether or not the gpxe code (or for
that matter the linux code) actually works -- YMMV.  I'm just going
by what information I have.

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

  reply	other threads:[~2008-03-27 16:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-25 18:41 Question on Wireless NICs Balaji Rao
2008-03-25 19:32 ` John W. Linville
2008-03-25 21:15   ` Ivo van Doorn
2008-03-26  2:32   ` Pavel Roskin
2008-03-27 15:58     ` John W. Linville [this message]
2008-03-27 19:32       ` Pavel Roskin

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=20080327155842.GA3624@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=balajirrao@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=proski@gnu.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).