hostAP suspend/resume
"Pering, Trevor" <[email protected]>
| Newsgroups | gmane.comp.handhelds.openzaurus.devel |
|---|---|
| Message-ID | <9AE298E00BCF7B469C04BE82FCE78B87021591EC@scsmsx414.amr.corp.intel.com> |
Hello, I'm having trouble with hostAP PCMCIA suspend/resume on my 2.6.17
arm-linux pxa system. It's not quite openzaurus -- but the hardware is
similar enough, and I'm just looking for general information right now.
I can get my basic system up and running ok, but not suspend/resume.
Richard Purdie had a similar problem on the OpenZaurus platform in April
2006, but there was no reply posted on the list. Also, his specific
problems seemed to be different (at least there were significant
differences in the log).
(http://lists.shmoo.com/pipermail/hostap/2006-April/013057.html
Basically, after I do a cardctl suspend/resume sequence the card no
longer works. If I then eject/insert the card it resets itself and works
properly.
Any suggestions on what's going on? I haven't been able to find much out
there about the suspend/resume operation. A bunch more log information
is included below, fwiw. (I have also tried updating the card firmware
to something more recent but it still doesn't work -- but the same card
works on an x86 ubuntu system, so I don't think that's it.)
Mainly, I'm looking for a NAK/ACK if this is working on the Zaurus for a
2.6.x kernel (and if so, which one) -- and if that's the case, I can
delve into the internals to figure out what. I didn't find anything on
the wiki or mailing list archives.
Thanks,
Trevor
[root@monkey ~]#cardctl suspend 0
ds: ds_open(socket 0)
hostap_cs: CS_EVENT_PM_SUSPEND
wifi0: hfa384x_cmd: entry still in list? (entry=c167b2e0, type=0, res=0)
wifi0: hfa384x_cmd: command was not completed (res=0, entry=c167b2e0,
type=0, cmd=0x0002, param0=0x0000, EVSTAT=8000 INTEN=0010)
hostap_cs: Shutdown failed
ds: ds_release(socket 0)
[root@monkey ~]#cardctl resume 0
ds: ds_open(socket 0)
hostap_cs: CS_EVENT_PM_RESUME
wifi0: card already removed or not configured during shutdown
wifi0: Interrupt, but dev not OK
prism2_hw_init: initialized in 300 ms
wifi0: Port type setting to 1 failed
wifi0: hfa384x_cmd: entry still in list? (entry=c167b2e0, type=0,
res=-1)
wifi0: hfa384x_cmd: interrupted; err=-110
wifi0: MAC port 0 enabling failed
ds: ds_release(socket 0)
[root@monkey ~]#cardctl ident
Socket 0:
product info: "NETGEAR", "MA701 Wireless CF Card", ""
manfid: 0xd601, 0x0002
function: 6 (network)
[root@monkey ~]#iwconfig -v
iwconfig Wireless-Tools version 28
Compatible with Wireless Extension v11 to v19.
Kernel Currently compiled with Wireless Extension v20.
wifi0 Recommend Wireless Extension v18 or later,
Currently compiled with Wireless Extension v20.
wlan0 Recommend Wireless Extension v18 or later,
Currently compiled with Wireless Extension v20.
[root@monkey ~]#cardctl insert 0
ds: ds_open(socket 0)
pccard: PCMCIA card inserted into slot 0
pcmcia: registering new device pcmcia0.0
hostap_cs: setting Vcc=33 (constant)
Checking CFTABLE_ENTRY 0x01 (default 0x01)
IO window settings: cfg->io.nwin=1 dflt.io.nwin=1
io->flags = 0x0046, io.base=0x0000, len=64
hostap_cs: Registered netdevice wifi0
hostap_cs: index 0x01: , irq 113, io 0xc2860000-0xc286003f
prism2_hw_init: initialized in 440 ms
wifi0: NIC: id=0x800c v1.0.0
wifi0: PRI: id=0x15 v1.0.7
wifi0: STA: id=0x1f v1.3.6
wifi0: defaulting to host-based encryption as a workaround for firmware
bug in Host AP mode WEP
wifi0: defaulting to bogus WDS frame as a workaround for firmware bug in
Host AP mode WDS
wifi0: registered netdevice wlan0
ds: ds_release(socket 0)
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV