How is WLAN card of SL6000L addressed?

[dhns]

Hi all SL6000 owners,

I am currently preparing an application using PCMCIA raw access. Since I do not have access to an SL6000 but want to be prepared, please could somebody issue the following commands

Code: [Select]

more /var/lib/pcmcia/stab
cardctl status
cardctl config
and post the results?

Many thanks,

-- hns

[boosalis]

Here you go (Note I have expansion jacket with barcode reader)

BusyBox on alpha login: zaurus
$ su
# more /var/lib/pcmcia/stab
Socket 0: ATA/IDE Fixed Disk
0       ide     ide_cs  0       hda     3       0
Socket 1: SDG Systems MobiliScan HS2
1       sdgmhs  sdgmhs_cs       0       sdgmhs0 251   0
*****************************************************
$ cardctl status
Socket 0:
  3.3V 16-bit PC Card
  function 0: [ready], [bat dead], [bat low]
Socket 1:
  3.3V 16-bit PC Card
  function 0: [ready]
******************************************************
$ cardctl config
Socket 0:
  Vcc 3.3V  Vpp1 0.0V  Vpp2 0.0V
  interface type is "memory and I/O"
  irq 43 [exclusive] [level]
  function 0:
    config base 0x0200
      option 0x41 status 0x00 pin 0x00 copy 0x00
    io 0xf6000000-0xf600000f [auto]
Socket 1:
  Vcc 3.3V  Vpp1 0.0V  Vpp2 0.0V
  interface type is "memory and I/O"
  irq 58 [exclusive] [level]
  function 0:
    config base 0x0400
      option 0x4d status 0x00
    io 0xf70003f8-0xf70003ff [8bit]
$

[dhns]

Many thanks,

could you please also issue a cardctl ident command?

But I already suspect that my assumption that it is simply a CF card attached to the second PCMCIA slot seems not to be correct. Rather, the second slot is used by the expansion jackedt.

So WiFi appears to have its own driver. Does anybody have an idea? SDIO? Serial?

-- hns

[nevarrie]

So WiFi appears to have its own driver. Does anybody have an idea? SDIO? Serial?

I believe it is using USB.  Here is what dmesg gives if I disconnect and then reconnect to my AP

Code: [Select]

usb.c: USB disconnect on device 10
hub.c: USB new device connect on bus1/2, assigned device number 11
ident: nic h/w: id=0x8026 1.0.0
ident: pri f/w: id=0x15 1.1.3
ident: sta f/w: id=0x1f 1.7.4
MFI:SUP:role=0x00:id=0x01:var=0x01:b/t=1/1
CFI:SUP:role=0x00:id=0x02:var=0x02:b/t=1/1
PRI:SUP:role=0x00:id=0x03:var=0x01:b/t=1/4
STA:SUP:role=0x00:id=0x04:var=0x01:b/t=1/12
PRI-CFI:ACT:role=0x01:id=0x02:var=0x02:b/t=1/1
STA-CFI:ACT:role=0x01:id=0x02:var=0x02:b/t=1/1
STA-MFI:ACT:role=0x01:id=0x01:var=0x01:b/t=1/1
Prism2 card SN: \x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00
p80211knetdev_hard_start_xmit: Tx attempt prior to association, frame dropped.
linkstatus=CONNECTED

[boosalis]

cardcntl ident produces:
BusyBox on alpha login: zaurus
$ su
# cd /sbin
# ./cardctl ident
Socket 0:
  product info: "SunDisk", "SDP", "5/3 0.6"
  manfid: 0x0045, 0x0401
  function: 4 (fixed disk)
Socket 1:
  product info: "SDG Systems LLC", "MobiliScan HS", "Rev 2.3", "0001"
  manfid: 0x0104, 0x009f
  function: 2 (serial)
#

[dhns]

I believe it is using USB.  Here is what dmesg gives if I disconnect and then reconnect to my AP

Yes, it looks like - and would be a reasonable solution if it is not CF/PCMCIA as the logs from bosalis have shown.

Makes it much more difficult to write my architecture in a way that it addresses either CF WiFi cards and and the USB based SL6000L...

Many thanks,
Nikolaus