mini-pci card under 6.3

GENERAL Help
1

Hi there,

I’ve been using qnx for a few days now and have got most of it sorted, but one thing I cannot get going is my mini-pci wireless nic. The problem is that the mini-pci slot doesn’t show up under “pin”, just the two pcmcia slots. “cardctl ident” under linux shows

Socket 0:
no product info available
Socket 1:
no product info available
Socket 2:
product info: “Dell”, “TrueMobile 1150 Series PC Card”, “Version 01.01”, “”
manfid: 0x0156, 0x0002
function: 6 (network)

whereas “pin” just shows

Sock Func Type Flags PID Base Size IRQ
1 Empty ----MF---------- None
1 Empty ----MF---------- None
2 0 Network C—I-±–X----- 69643 0x300 64 3
2 Empty ----MF---------- None

(ignore the card in slot 2, it’s my girlfriends wireless pcmcia card which I’m using until I can get my internal one running)

pci -v shows the mini-pci slot as being a Texas Instruments PCI1410 cardbus controller which is listed as being supprted on the QNX website (fwiw the two external pcmcia slots are controleld by PCI1420 controllers).

Does qnx have a limit of two controllers? Is there some way to “force” the internal one to load? Is there some other way of handling mini-pci cards under qnx? I have high hopes of the card working if I can get the slot to show up using pin because the pcmcia wireless card I’m currently using has the same chipset (prism) as the mini-pci one, but my girlfriend wants it back :frowning:

Any ideas?

Cheers,
Andrew

here’s the full pci -v output for that controller:

Class = Bridge (CardBus)
Vendor ID = 104ch, Texas Instruments
Device ID = ac50h, PCI1410 PC card cardBus Controller
PCI index = 0h
Class Codes = 060700h
Revision ID = 1h
Bus number = 0
Device number = 16
Function num = 0
Status Reg = 210h
Command Reg = 107h
Header type = 2h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 20h
Cache Line Size= 8h un-cacheable
ExCA Base Address = 10002000h
Capabilities Pointer = ffh
Secondary Status = ffffh
Primary Bus Number = 0
Secondary Bus Number = 4
Subordinate Bus Number = 4
Secondary Latency Timer = b0h
Memory Base 0 = 11400000h
Memory Limit 0 = 117ff000h
Memory Base 1 = 11800000h
Memory Limit 1 = 11bff000h
I/O Base 0 = 5000h
I/O Limit 0 = 0h
I/O Base 1 = 5400h
I/O Limit 1 = 54fch
PCI Int Pin = 1
PCI Int Pin = INT A
Interrupt line = 11
CPU Interrupt = 0h
Bridge Control = 5c0h
Subsystem Vendor ID = 12a3h
Subsystem ID = ab01h
Legacy Mode Base Address = 0h
System Control = 44f060h
Retry Status = c0h
Card Control = 1h
Device Control = 60h
Buffer Control = 61h
Socket DMA Register 0 = 0h
Socket DMA Register 1 = 0h

2

some more poking around and I discovered some more info.

I can’t actually find the vendor id for Texas Instruments in /etc/system/enum/include/pci-vendors (or anywhere else for that matter) so I’m wondering where devp-pccard gets its vendor and device ids from.

All three controllers (two cardbus, one mini-pci) show up under enum-pci (The bottom on is the internal minipci):

B1339451 bus=pci ven=104c dev=ac51 class=06 subclass=07 progif=00 busnum=0 device=3 function=0 index=0 irq=11 pin=A
B1339451 bus=pci ven=104c dev=ac51 class=06 subclass=07 progif=00 busnum=0 device=3 function=1 index=1 irq=11 pin=A
B1339451 bus=pci ven=104c dev=ac50 class=06 subclass=07 progif=00 busnum=0 device=16 function=0 index=0 irq=11 pin=A

but enum-devices -n shows the mini-pci slot as being unknown:

echo bridge bus=pnpbios devid=PNP0E03 type=06 subclass=07 progif=00 >/etc/system/trap/unknown

(btw, I only just discovered this because I didn’t realise that /etc/system/trap/unknown gets overwritten each time an unknown device is found, so only shows the last one found!)

I also tried forcing it using devp-pccard ss -V 104c -D ac50 which executes without errors but doesn’t actually help (still only two slots listed).

So, any ideas on where devp-pccard gets its device and vendor ids from? Under both linux and BeOS all three contrllers show up as standard cardbus slots. One thing I did notice is throughout the help documentation they refer to “both slots” and “the other slot” making me wonder if QNX can only support two slots at a time?

Anyways, any ideas let me know! I’m starting to think it’s a lost cause. Still, at least my audio and video both work which is better than my last pc :slight_smile:

Cheers,
Andrew

3

I too have been struggling with wireless on QNX
Your main problem is that the wireless card is not supported by QNX.
They have a fairly limited supprot for wireless cards, i.e. Orioco based or prism based.
They will soon be releasing a driver for the Broadcom 43xx chipset.
qnx.com/developers/hardware_ … index.html

The other point to note is that it is most likely that the PC card bridge chip is on the wireless card, not on the motherboard.
I was fooled by this for a while, you may be able to get this running properly by following these steps:
qnx.com/developers/docs/6.3. … ARD_PCMCIA

But even if you get the pccard server running, you probably won’t get a driver for your wireless card:-(

4

bren-uk, where did you see that they’ll be releasing a Broadcom 43xx driver? I’m waiting on that driver, and would like to get more information. Thanks.