From: Pavel Roskin <proski@gnu.org>
To: linux-kernel@vger.kernel.org
Cc: David Hinds <dhinds@sonic.net>
Subject: Driver for PLX9052 based PCMCIA-to-PCI bridges
Date: Sun, 06 Apr 2003 01:42:18 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.51.0304060011390.11914@localhost.localdomain> (raw)
Hello!
I have written a driver for PLX9052 based PCMCIA-to-PCI bridges commonly
used in "PCI wireless cards" that consist of a PCMCIA wireless card and a
PCMCIA-to-PCI bridge.
Such "PCI" cards cost almost as much as PCMCIA cards, so the cost of the
bridge is essentially zero. It's important to have support for hardware
that people can get almost for free.
Due to limitations of the chip, this driver doesn't support relocation of
memory or I/O windows. It turns out some PCMCIA drivers really don't like
it (in particular pcnet-cs), so essentially this driver is just another
way to support PLX-based wireless cards that are already supported by
orinoco_plx. The only upshot is that it's possible to swap cards without
doing anything with the driver.
However, if there is enough interest, the driver can be improved to
support more cards. In particular, I think it's possible to put a memory
window after the CIS within the same PCI memory resource.
It's also important to have a driver that cannot relocate memory and I/O
(i.e. the one that uses io_offset and SS_CAP_STATIC_MAP). There are
already two such drivers in the 2.4 tree: au1000_generic and
sa1100_generic. They both are for embedded hardware. Having a driver for
PC would make it easy to fix incompatible card drivers.
Since io_offset is used, this driver cannot be used with pcmcia-cs
drivers.
The driver and the documentation are here:
http://www.red-bean.com/~proski/plx9052/
--
Regards,
Pavel Roskin
reply other threads:[~2003-04-06 6:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Pine.LNX.4.51.0304060011390.11914@localhost.localdomain \
--to=proski@gnu.org \
--cc=dhinds@sonic.net \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®