Accessing Orinoco wireless card registers under QNX 4.25

[Adam_Howell]

Hello everyone,

Sorry for any cross posting, but I am attempting to get a device driver
written for the Orinoco Silver wireless cards under QNX 4.25 based on
the GPL orinoco_cs driver for linux, and I am having trouble with simply
being able to read from the Hermes chipset registers on the card.
Basically, the card is detected by Pcmcia.generic, and allocated I/O
memory and an IRQ. So I thought that I would simply be able to read
directly from the designated I/O memory to see what is in the registers,
however all I get back is junk (either all 0x0000 or 0xffff). Reading
the same registers under QNX 6.2 and Linux result in reasonable (ie.
plausible values Is there something that else that needs to be
setup for me to interact with the card? If so, what?

I also noticed that there is some type of versioning problem with the
CIS tuples (see pin cis output below), which may be the culprit, but
hopefully someone can give me an idea about what the problem is and if
there is any fix/workaround. I’ve appended the output of pin, pin cis
and pin config below for reference.

Also, I have tried changing the resources used (I/O port and IRQ) to the
settings allocated under both Linux and QNX 6, but I recieved the same
results.

Any help would be greatly appreciated,
-Adam

pin

Sock Win Type Flags PID Base Size IRQ Base
Size DMA
1 0 Network C—I-±-------W None 0x240 64 11

2 Empty ----MF---------- None

pin config

; socket 1
[device]
manufacturer = “Lucent Technologies”
product = “WaveLAN/IEEE”
info1 = “Version 01.01”
info2 = “”
regbase = 0x3e0
config = 0x01, 0x0601, irq any, io any+64 (width=16)
register = 0, 0x40, 0x40 ; level mode interrupts

pin cis

Socket : 1
Device : Null 0k
Attribute Device : SRAM 1k
Other conditions (att) : MWait
Attribute Device : SRAM 1k
Could be version problem, found 5.76, need 4.01
Card tuple version : 5.00
Manufacturer : Lucent Technologies
Name of Product : WaveLAN/IEEE
Add’nl info (lot #) : Version 01.01
Add’nl info (programming):
Manufacturer ID : 0x156 0x2
PC Card function : NetworkLAN Adapter
POST : 0x0
Tuple 0x22 link=2 : 01 07
Tuple 0x22 link=5 : 02 40 42 0f 00
Tuple 0x22 link=5 : 02 80 84 1e 00
Tuple 0x22 link=5 : 02 60 ec 53 00
Tuple 0x22 link=5 : 02 c0 d8 a7 00
Tuple 0x22 link=2 : 03 07
Tuple 0x22 link=8 : 04 06 00 02 2d 53 29 9d
Tuple 0x22 link=2 : 05 01
Configuration base/st : 0x3e0 0-subtuples
Configuration Index : 0x1 Last Default
Interface : I/O
Feature : 0x19
IO Space : Bus16 0x0-0x3F(6 lines)
IRQ Description : Pulse Level VEND BERR IOCK NMI 0 1 2 3 4 5 6
7 8 9 10 11 12 13 14 15

[Hugh_Brown1]

This could be a PCMCIA width issue. You can try using the latest pccard
software which you can download from http://developers.qnx.com under
“new stuff”.

Previously, Adam Howell wrote in qdn.public.qnx4:

Hello everyone,

Sorry for any cross posting, but I am attempting to get a device driver
written for the Orinoco Silver wireless cards under QNX 4.25 based on
the GPL orinoco_cs driver for linux, and I am having trouble with simply
being able to read from the Hermes chipset registers on the card.
Basically, the card is detected by Pcmcia.generic, and allocated I/O
memory and an IRQ. So I thought that I would simply be able to read
directly from the designated I/O memory to see what is in the registers,
however all I get back is junk (either all 0x0000 or 0xffff). Reading
the same registers under QNX 6.2 and Linux result in reasonable (ie.
plausible > > values Is there something that else that needs to be
setup for me to interact with the card? If so, what?

I also noticed that there is some type of versioning problem with the
CIS tuples (see pin cis output below), which may be the culprit, but
hopefully someone can give me an idea about what the problem is and if
there is any fix/workaround. I’ve appended the output of pin, pin cis
and pin config below for reference.

Also, I have tried changing the resources used (I/O port and IRQ) to the
settings allocated under both Linux and QNX 6, but I recieved the same
results.

Any help would be greatly appreciated,
-Adam

pin

Sock Win Type Flags PID Base Size IRQ Base
Size DMA
1 0 Network C—I-±-------W None 0x240 64 11

2 Empty ----MF---------- None

pin config

; socket 1
[device]
manufacturer = “Lucent Technologies”
product = “WaveLAN/IEEE”
info1 = “Version 01.01”
info2 = “”
regbase = 0x3e0
config = 0x01, 0x0601, irq any, io any+64 (width=16)
register = 0, 0x40, 0x40 ; level mode interrupts

pin cis

Socket : 1
Device : Null 0k
Attribute Device : SRAM 1k
Other conditions (att) : MWait
Attribute Device : SRAM 1k
Could be version problem, found 5.76, need 4.01
Card tuple version : 5.00
Manufacturer : Lucent Technologies
Name of Product : WaveLAN/IEEE
Add’nl info (lot #) : Version 01.01
Add’nl info (programming):
Manufacturer ID : 0x156 0x2
PC Card function : NetworkLAN Adapter
POST : 0x0
Tuple 0x22 link=2 : 01 07
Tuple 0x22 link=5 : 02 40 42 0f 00
Tuple 0x22 link=5 : 02 80 84 1e 00
Tuple 0x22 link=5 : 02 60 ec 53 00
Tuple 0x22 link=5 : 02 c0 d8 a7 00
Tuple 0x22 link=2 : 03 07
Tuple 0x22 link=8 : 04 06 00 02 2d 53 29 9d
Tuple 0x22 link=2 : 05 01
Configuration base/st : 0x3e0 0-subtuples
Configuration Index : 0x1 Last Default
Interface : I/O
Feature : 0x19
IO Space : Bus16 0x0-0x3F(6 lines)
IRQ Description : Pulse Level VEND BERR IOCK NMI 0 1 2 3 4 5 6
7 8 9 10 11 12 13 14 15

[Adam_Howell]

Hi Hugh,

I downloaded and installed the latest pccard software, and I tried
running pccard with both widths, ie.

pccard -v -w16
and
pccard -v -w8

however, I still get nothing from the registers. Also, just as a note,
I don’t get the tuple version problem warning when I run ‘pin cis’ using
the pccard server. What should I try next?

Thanks for the help,
-Adam



Hugh Brown wrote:

This could be a PCMCIA width issue. You can try using the latest pccard
software which you can download from > http://developers.qnx.com > under
“new stuff”.

Previously, Adam Howell wrote in qdn.public.qnx4:

Hello everyone,

Sorry for any cross posting, but I am attempting to get a device driver
written for the Orinoco Silver wireless cards under QNX 4.25 based on
the GPL orinoco_cs driver for linux, and I am having trouble with simply
being able to read from the Hermes chipset registers on the card.
Basically, the card is detected by Pcmcia.generic, and allocated I/O
memory and an IRQ. So I thought that I would simply be able to read
directly from the designated I/O memory to see what is in the registers,
however all I get back is junk (either all 0x0000 or 0xffff). Reading
the same registers under QNX 6.2 and Linux result in reasonable (ie.
plausible > > values Is there something that else that needs to be
setup for me to interact with the card? If so, what?

[Hugh_Brown1]

What I/O ports are being use by Linux? Maybe you can try a different I/O
port range by starting pccard as ‘pccard -a0xppp’ where ppp is the I/O port
that Linux is using.

Previously, Adam Howell wrote in qdn.public.qnx4:

Hi Hugh,

I downloaded and installed the latest pccard software, and I tried
running pccard with both widths, ie.

pccard -v -w16
and
pccard -v -w8

however, I still get nothing from the registers. Also, just as a note,
I don’t get the tuple version problem warning when I run ‘pin cis’ using
the pccard server. What should I try next?

Thanks for the help,
-Adam



Hugh Brown wrote:
This could be a PCMCIA width issue. You can try using the latest pccard
software which you can download from > http://developers.qnx.com > under
“new stuff”.

Previously, Adam Howell wrote in qdn.public.qnx4:

Hello everyone,

Sorry for any cross posting, but I am attempting to get a device driver
written for the Orinoco Silver wireless cards under QNX 4.25 based on
the GPL orinoco_cs driver for linux, and I am having trouble with simply
being able to read from the Hermes chipset registers on the card.
Basically, the card is detected by Pcmcia.generic, and allocated I/O
memory and an IRQ. So I thought that I would simply be able to read
directly from the designated I/O memory to see what is in the registers,
however all I get back is junk (either all 0x0000 or 0xffff). Reading
the same registers under QNX 6.2 and Linux result in reasonable (ie.
plausible > > values Is there something that else that needs to be
setup for me to interact with the card? If so, what?

[Adam_Howell]

Linux uses i/o port 0x100, and I tried to force these settings using
pccard -a 0x100 -w16
but this didn’t change anything coming from the registers. Also, I did
notice that Linux assigns IRQ 3 to the card, but for some reason QNX
won’t use this IRQ (it’s not currently in use by anything else, and I
included it in pcmcia.1 and pcmcia.cfg) but automatically assigns IRQ 5.
What next?

Thanks,
-Adam

Hugh Brown wrote:

What I/O ports are being use by Linux? Maybe you can try a different I/O
port range by starting pccard as ‘pccard -a0xppp’ where ppp is the I/O port
that Linux is using.

Previously, Adam Howell wrote in qdn.public.qnx4:

Hi Hugh,

I downloaded and installed the latest pccard software, and I tried
running pccard with both widths, ie.

pccard -v -w16
and
pccard -v -w8

however, I still get nothing from the registers. Also, just as a note,
I don’t get the tuple version problem warning when I run ‘pin cis’ using
the pccard server. What should I try next?

Thanks for the help,
-Adam



Hugh Brown wrote:

This could be a PCMCIA width issue. You can try using the latest pccard
software which you can download from > http://developers.qnx.com > under
“new stuff”.

Previously, Adam Howell wrote in qdn.public.qnx4:


Hello everyone,

Sorry for any cross posting, but I am attempting to get a device driver
written for the Orinoco Silver wireless cards under QNX 4.25 based on
the GPL orinoco_cs driver for linux, and I am having trouble with simply
being able to read from the Hermes chipset registers on the card.
Basically, the card is detected by Pcmcia.generic, and allocated I/O
memory and an IRQ. So I thought that I would simply be able to read
directly from the designated I/O memory to see what is in the registers,
however all I get back is junk (either all 0x0000 or 0xffff). Reading
the same registers under QNX 6.2 and Linux result in reasonable (ie.
plausible > > values Is there something that else that needs to be
setup for me to interact with the card? If so, what?

[Hugh_Brown1]

I would imagine that this card needs some bit(s) written to a register
to enable it. Have a look at the specs.

Previously, Adam Howell wrote in qdn.public.qnx4:

Linux uses i/o port 0x100, and I tried to force these settings using
pccard -a 0x100 -w16
but this didn’t change anything coming from the registers. Also, I did
notice that Linux assigns IRQ 3 to the card, but for some reason QNX
won’t use this IRQ (it’s not currently in use by anything else, and I
included it in pcmcia.1 and pcmcia.cfg) but automatically assigns IRQ 5.
What next?

Thanks,
-Adam

Hugh Brown wrote:
What I/O ports are being use by Linux? Maybe you can try a different I/O
port range by starting pccard as ‘pccard -a0xppp’ where ppp is the I/O port
that Linux is using.

Previously, Adam Howell wrote in qdn.public.qnx4:

Hi Hugh,

I downloaded and installed the latest pccard software, and I tried
running pccard with both widths, ie.

pccard -v -w16
and
pccard -v -w8

however, I still get nothing from the registers. Also, just as a note,
I don’t get the tuple version problem warning when I run ‘pin cis’ using
the pccard server. What should I try next?

Thanks for the help,
-Adam



Hugh Brown wrote:

This could be a PCMCIA width issue. You can try using the latest pccard
software which you can download from > http://developers.qnx.com > under
“new stuff”.

Previously, Adam Howell wrote in qdn.public.qnx4:


Hello everyone,

Sorry for any cross posting, but I am attempting to get a device driver
written for the Orinoco Silver wireless cards under QNX 4.25 based on
the GPL orinoco_cs driver for linux, and I am having trouble with simply
being able to read from the Hermes chipset registers on the card.
Basically, the card is detected by Pcmcia.generic, and allocated I/O
memory and an IRQ. So I thought that I would simply be able to read
directly from the designated I/O memory to see what is in the registers,
however all I get back is junk (either all 0x0000 or 0xffff). Reading
the same registers under QNX 6.2 and Linux result in reasonable (ie.
plausible > > values Is there something that else that needs to be
setup for me to interact with the card? If so, what?


\

[Adam_Howell]

Hugh,

I have also worked this angle based on the GPL orinoco_cs driver,
essentially trying to both reset the hardware and/or detect the chipset,
however both the detection and reset look at a specific register for a
response, and since the registers are always 0x000, both calls fail.
For this reason, I’m wondering if pccard is not initially setting up the
card’s resources correctly, so is there any way to check or replicate
how pccard interacts with CIS? Short of writing something up myself to
read the CIS tuples…

Thanks again,
-Adam


Hugh Brown wrote:

I would imagine that this card needs some bit(s) written to a register
to enable it. Have a look at the specs.

Previously, Adam Howell wrote in qdn.public.qnx4:

Linux uses i/o port 0x100, and I tried to force these settings using
pccard -a 0x100 -w16
but this didn’t change anything coming from the registers. Also, I did
notice that Linux assigns IRQ 3 to the card, but for some reason QNX
won’t use this IRQ (it’s not currently in use by anything else, and I
included it in pcmcia.1 and pcmcia.cfg) but automatically assigns IRQ 5.
What next?

Thanks,
-Adam

Hugh Brown wrote:

What I/O ports are being use by Linux? Maybe you can try a different I/O
port range by starting pccard as ‘pccard -a0xppp’ where ppp is the I/O port
that Linux is using.

Previously, Adam Howell wrote in qdn.public.qnx4:


Hi Hugh,

I downloaded and installed the latest pccard software, and I tried
running pccard with both widths, ie.

pccard -v -w16
and
pccard -v -w8

however, I still get nothing from the registers. Also, just as a note,
I don’t get the tuple version problem warning when I run ‘pin cis’ using
the pccard server. What should I try next?

Thanks for the help,
-Adam



Hugh Brown wrote:


This could be a PCMCIA width issue. You can try using the latest pccard
software which you can download from > http://developers.qnx.com > under
“new stuff”.

Previously, Adam Howell wrote in qdn.public.qnx4:



Hello everyone,

Sorry for any cross posting, but I am attempting to get a device driver
written for the Orinoco Silver wireless cards under QNX 4.25 based on
the GPL orinoco_cs driver for linux, and I am having trouble with simply
being able to read from the Hermes chipset registers on the card.
Basically, the card is detected by Pcmcia.generic, and allocated I/O
memory and an IRQ. So I thought that I would simply be able to read
directly from the designated I/O memory to see what is in the registers,
however all I get back is junk (either all 0x0000 or 0xffff). Reading
the same registers under QNX 6.2 and Linux result in reasonable (ie.
plausible > > values Is there something that else that needs to be
setup for me to interact with the card? If so, what?
\

[Hugh_Brown1]

There must be some initialization that has to be done to the Orinoco
card to make the I/O space visible. The CIS is memory mapped and is not
accessed in the same manner. The pccard software is a back port of
devp-pccard under QNX6 and the Orinoco driver works under QNX6. If I
plug the Orinoco card into a QNX6 machine I get exactly the same behaviour
as I do under QNX4 - all registers read 0.

Previously, Adam Howell wrote in qdn.public.qnx4:

Hugh,

I have also worked this angle based on the GPL orinoco_cs driver,
essentially trying to both reset the hardware and/or detect the chipset,
however both the detection and reset look at a specific register for a
response, and since the registers are always 0x000, both calls fail.
For this reason, I’m wondering if pccard is not initially setting up the
card’s resources correctly, so is there any way to check or replicate
how pccard interacts with CIS? Short of writing something up myself to
read the CIS tuples…

Thanks again,
-Adam


Hugh Brown wrote:
I would imagine that this card needs some bit(s) written to a register
to enable it. Have a look at the specs.

Previously, Adam Howell wrote in qdn.public.qnx4:

Linux uses i/o port 0x100, and I tried to force these settings using
pccard -a 0x100 -w16
but this didn’t change anything coming from the registers. Also, I did
notice that Linux assigns IRQ 3 to the card, but for some reason QNX
won’t use this IRQ (it’s not currently in use by anything else, and I
included it in pcmcia.1 and pcmcia.cfg) but automatically assigns IRQ 5.
What next?

Thanks,
-Adam

Hugh Brown wrote:

What I/O ports are being use by Linux? Maybe you can try a different I/O
port range by starting pccard as ‘pccard -a0xppp’ where ppp is the I/O port
that Linux is using.

Previously, Adam Howell wrote in qdn.public.qnx4:


Hi Hugh,

I downloaded and installed the latest pccard software, and I tried
running pccard with both widths, ie.

pccard -v -w16
and
pccard -v -w8

however, I still get nothing from the registers. Also, just as a note,
I don’t get the tuple version problem warning when I run ‘pin cis’ using
the pccard server. What should I try next?

Thanks for the help,
-Adam



Hugh Brown wrote:


This could be a PCMCIA width issue. You can try using the latest pccard
software which you can download from > http://developers.qnx.com > under
“new stuff”.

Previously, Adam Howell wrote in qdn.public.qnx4:



Hello everyone,

Sorry for any cross posting, but I am attempting to get a device driver
written for the Orinoco Silver wireless cards under QNX 4.25 based on
the GPL orinoco_cs driver for linux, and I am having trouble with simply
being able to read from the Hermes chipset registers on the card.
Basically, the card is detected by Pcmcia.generic, and allocated I/O
memory and an IRQ. So I thought that I would simply be able to read
directly from the designated I/O memory to see what is in the registers,
however all I get back is junk (either all 0x0000 or 0xffff). Reading
the same registers under QNX 6.2 and Linux result in reasonable (ie.
plausible > > values Is there something that else that needs to be
setup for me to interact with the card? If so, what?



\

[Adam_Howell]

Hi Hugh,

I completely agree, but I believe that this initialization is done in
Card Services under Linux, but done by the driver under QNX. The reason
for this is that I have a program that runs the hardware reset under all
three OS’s (Linux, QNX 6, and QNX 4). When I display the registers
under Linux, I found that the hardware reset is able to read/write from
the registers, while the same code under either QNX still cannot access
them. The only code that touches the card before the hardware reset
under Linux is Card Services, which writes configuration info to some
CIS registers on the card.

This is why I was hoping there is some way that I can reproduce and find
out exactly what pccard does to the card when it is inserted, and how
pccard interacts with CIS on the card. In fact, if there is anyway I
can find out what the QNX 6 driver does to initialize the card, that
would be great. (Also, this is a project I am doing for work, and if
some type of nondisclosure agreement is required, I can arrange for it:)

Thanks,
-Adam




Hugh Brown wrote:

There must be some initialization that has to be done to the Orinoco
card to make the I/O space visible. The CIS is memory mapped and is not
accessed in the same manner. The pccard software is a back port of
devp-pccard under QNX6 and the Orinoco driver works under QNX6. If I
plug the Orinoco card into a QNX6 machine I get exactly the same behaviour
as I do under QNX4 - all registers read 0.

Previously, Adam Howell wrote in qdn.public.qnx4:

Hugh,

I have also worked this angle based on the GPL orinoco_cs driver,
essentially trying to both reset the hardware and/or detect the chipset,
however both the detection and reset look at a specific register for a
response, and since the registers are always 0x000, both calls fail.
For this reason, I’m wondering if pccard is not initially setting up the
card’s resources correctly, so is there any way to check or replicate
how pccard interacts with CIS? Short of writing something up myself to
read the CIS tuples…

Thanks again,
-Adam


Hugh Brown wrote:

I would imagine that this card needs some bit(s) written to a register
to enable it. Have a look at the specs.

Previously, Adam Howell wrote in qdn.public.qnx4:


Linux uses i/o port 0x100, and I tried to force these settings using
pccard -a 0x100 -w16
but this didn’t change anything coming from the registers. Also, I did
notice that Linux assigns IRQ 3 to the card, but for some reason QNX
won’t use this IRQ (it’s not currently in use by anything else, and I
included it in pcmcia.1 and pcmcia.cfg) but automatically assigns IRQ 5.
What next?

Thanks,
-Adam

Hugh Brown wrote:


What I/O ports are being use by Linux? Maybe you can try a different I/O
port range by starting pccard as ‘pccard -a0xppp’ where ppp is the I/O port
that Linux is using.

Previously, Adam Howell wrote in qdn.public.qnx4:



Hi Hugh,

I downloaded and installed the latest pccard software, and I tried
running pccard with both widths, ie.

pccard -v -w16
and
pccard -v -w8

however, I still get nothing from the registers. Also, just as a note,
I don’t get the tuple version problem warning when I run ‘pin cis’ using
the pccard server. What should I try next?

Thanks for the help,
-Adam



Hugh Brown wrote:



This could be a PCMCIA width issue. You can try using the latest pccard
software which you can download from > http://developers.qnx.com > under
“new stuff”.

Previously, Adam Howell wrote in qdn.public.qnx4:




Hello everyone,

Sorry for any cross posting, but I am attempting to get a device driver
written for the Orinoco Silver wireless cards under QNX 4.25 based on
the GPL orinoco_cs driver for linux, and I am having trouble with simply
being able to read from the Hermes chipset registers on the card.
Basically, the card is detected by Pcmcia.generic, and allocated I/O
memory and an IRQ. So I thought that I would simply be able to read
directly from the designated I/O memory to see what is in the registers,
however all I get back is junk (either all 0x0000 or 0xffff). Reading
the same registers under QNX 6.2 and Linux result in reasonable (ie.
plausible > > values Is there something that else that needs to be
setup for me to interact with the card? If so, what?

\

[Hugh_Brown1]

I’m afraid that I cannot give you this information, as we have a C library
that we obtained from Lucent under NDA. You would have to sign an NDA with
Lucent to obtain this information.

As far as the CIS is concerned, the QNX pccard software does write the
configuration information back to the CIS, so the card is enabled from that
perspective.


Previously, Adam Howell wrote in qdn.public.qnx4:

Hi Hugh,

I completely agree, but I believe that this initialization is done in
Card Services under Linux, but done by the driver under QNX. The reason
for this is that I have a program that runs the hardware reset under all
three OS’s (Linux, QNX 6, and QNX 4). When I display the registers
under Linux, I found that the hardware reset is able to read/write from
the registers, while the same code under either QNX still cannot access
them. The only code that touches the card before the hardware reset
under Linux is Card Services, which writes configuration info to some
CIS registers on the card.

This is why I was hoping there is some way that I can reproduce and find
out exactly what pccard does to the card when it is inserted, and how
pccard interacts with CIS on the card. In fact, if there is anyway I
can find out what the QNX 6 driver does to initialize the card, that
would be great. (Also, this is a project I am doing for work, and if
some type of nondisclosure agreement is required, I can arrange for it:)

Thanks,
-Adam




Hugh Brown wrote:
There must be some initialization that has to be done to the Orinoco
card to make the I/O space visible. The CIS is memory mapped and is not
accessed in the same manner. The pccard software is a back port of
devp-pccard under QNX6 and the Orinoco driver works under QNX6. If I
plug the Orinoco card into a QNX6 machine I get exactly the same behaviour
as I do under QNX4 - all registers read 0.

Previously, Adam Howell wrote in qdn.public.qnx4:

Hugh,

I have also worked this angle based on the GPL orinoco_cs driver,
essentially trying to both reset the hardware and/or detect the chipset,
however both the detection and reset look at a specific register for a
response, and since the registers are always 0x000, both calls fail.
For this reason, I’m wondering if pccard is not initially setting up the
card’s resources correctly, so is there any way to check or replicate
how pccard interacts with CIS? Short of writing something up myself to
read the CIS tuples…

Thanks again,
-Adam


Hugh Brown wrote:

I would imagine that this card needs some bit(s) written to a register
to enable it. Have a look at the specs.

Previously, Adam Howell wrote in qdn.public.qnx4:


Linux uses i/o port 0x100, and I tried to force these settings using
pccard -a 0x100 -w16
but this didn’t change anything coming from the registers. Also, I did
notice that Linux assigns IRQ 3 to the card, but for some reason QNX
won’t use this IRQ (it’s not currently in use by anything else, and I
included it in pcmcia.1 and pcmcia.cfg) but automatically assigns IRQ 5.
What next?

Thanks,
-Adam

Hugh Brown wrote:


What I/O ports are being use by Linux? Maybe you can try a different I/O
port range by starting pccard as ‘pccard -a0xppp’ where ppp is the I/O port
that Linux is using.

Previously, Adam Howell wrote in qdn.public.qnx4:



Hi Hugh,

I downloaded and installed the latest pccard software, and I tried
running pccard with both widths, ie.

pccard -v -w16
and
pccard -v -w8

however, I still get nothing from the registers. Also, just as a note,
I don’t get the tuple version problem warning when I run ‘pin cis’ using
the pccard server. What should I try next?

Thanks for the help,
-Adam



Hugh Brown wrote:



This could be a PCMCIA width issue. You can try using the latest pccard
software which you can download from > http://developers.qnx.com > under
“new stuff”.

Previously, Adam Howell wrote in qdn.public.qnx4:




Hello everyone,

Sorry for any cross posting, but I am attempting to get a device driver
written for the Orinoco Silver wireless cards under QNX 4.25 based on
the GPL orinoco_cs driver for linux, and I am having trouble with simply
being able to read from the Hermes chipset registers on the card.
Basically, the card is detected by Pcmcia.generic, and allocated I/O
memory and an IRQ. So I thought that I would simply be able to read
directly from the designated I/O memory to see what is in the registers,
however all I get back is junk (either all 0x0000 or 0xffff). Reading
the same registers under QNX 6.2 and Linux result in reasonable (ie.
plausible > > values Is there something that else that needs to be
setup for me to interact with the card? If so, what?




\