mini-PCI support for orinoco_cs

[Manoj Kasichainula]

[Please keep me cc:ed on any replies, I'm not on the wireless mailing
list at the moment]
On Wed, Oct 24, 2001 at 09:55:15AM -0700, Jean Tourrilhes wrote:
> 	Unpack attached stuff in .../drivers/net/wireless/, apply the
> patch and compile. It doesn't work on my box (but wlan-ng doesn't
> either), but maybe you can beat it into submission.

Well, a simple pleading with it hasn't worked so far. Here's the
kernel output when I load the module:

PCI: Found IRQ 11 for device 02:02.0
PCI: Sharing IRQ 11 with 00:1d.2
PCI: Sharing IRQ 11 with 00:1f.1
Detected Orinoco/Prism2 PCI device at 02:02.0, mem:0xEC000000 to
0xEC000FFF -> 0xe8914000, irq:11
Reset
done......................................................................................................................................................................................................................................................;
Clear
Reset.....................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................;
pci_cor : reg = 0x0 - 7D6 - 7A4
eth1: MAC address 00:20:E0:89:0C:AD
eth1: Station identity 001f:0001:0001:0001
eth1: Unknown vendor, assuming it's an Intersil card.
eth1: You may want to report the MAC address and model of the card
eth1: Looks like an Intersil firmware version 1.01
eth1: Ad-hoc demo mode supported.
eth1: IEEE standard IBSS ad-hoc mode supported.
eth1: WEP supported, "128"-bit key.
eth1: Station name "Prism  I"
eth1: ready

My mini-PCI card is actually (allegedly) a prism 2.5, but I don't see
anywhere in the driver source where "Prism  I" could come from. I
guess that comes from the card itself.

I get this error when trying to set up the network interface

eth1: Channel out of range (0)!

And, for good measure, I sometimes get a few of:

eth1: EIO reading info frame.
eth1: Error -110 writing packet header to BAP

This looks like an ETIMEDOUT from hermes_bap_seek. Does that mean that
the BAP (whatever it is) wasn't found properly?

> 	Lastly, if you look at the wlan-ng list archive, there is a
> patch to add some Wireless Extension support to the driver.o

Yeah, but it doesn't let me set any of the things I actually want to
set. :) Still, I want to investigate it further.