Re: Running on PowerPC


From: Michael Habermann (MHabermann_at_gmx.de)
Date: 2002-05-31 07:12:57 UTC



At 02:19 PM 5/30/2002 -0400, Pavel Roskin wrote:
>Hello!
>
> > It seems, that some guys made the host based AP running on PowerPC.
>
>What version of HostAP? What card?

yLez
hostap driver - Prism2-2002-05-19

> > I can compile the packet for a MPC855 and start it, but it returns me
> an error:
> > 'hostap_cs: %s: hfa384x_cmd - timeout - reg=0x%04x'.
>
>Are you sure? I don't think it prints '%' to the kernel log. Could you
>give some context from the output of dmesg? What happens before and after
>that error? In particular, the firmware version could be important.

My oputput is:



Starting PCMCIA services: modulesUsing /lib/modules/2.4.4/pcmcia/pcmcia_core.o .!dě

   .!d
   e
Using /lib/modules/2.4.4/pcmcia/m8xx_pcmcia.o m8xx_pcmcia:
m8xx_pcmcia: FADS using SLOT_A with IRQ 13. Using /lib/modules/2.4.4/pcmcia/ds.o
  cardmgr.

cardmgr[45]: starting, version is 3.1.26
cardmgr[45]: watching 1 sockets
cardmgr[45]: Card Services release does not match
cardmgr[45]: initializing socket 0

Setting up basic iptables rules
cardmgr[45]: socket 0: Intersil PRISM2 11 Mbps Wireless Adapter cardmgr[45]: executing: 'modprobe hostap_cs' Bringing up network devices
lo
eth1
eth0
eth2
Waiting for WLAN device eth2 to start hostap_cs: %s: hfa384x_cmd - timeout - reg=0x%04x
hostap_cs: (c) SSH Communications Security Corp <jkm_at_ssh.com>
cardmgr[45]: + Using /lib/modules/2.4.4/pcmcia/hostap_cs.o
hostap_cs:  %#05lx-%#05lx:

.cardmgr[45]: get dev info on socket 0 failed: Resource temporarily unavailable

It collides a little bit with the output of my start script and the debug output of my pcmcia-cs seems to be buggy. But so far, I could run the wvlan_cs.o driver from the pcmcia-cs package and the linux-wlan-ng driver without problems (They also produced buggy output).

>You can try the same card on a i386 system. I know that some cards with
>Intersil chipset sometimes become busy for a long time (about 4.5
>milliseconds). Then you would see the same timeout.

I've tested the same driver and card on my PC and it works. But the PC is much, much faster. I also have a Intersil chipset. I've multiplied all timeouts in the prism2.c code by 10, but it still doesn't work.



This archive was generated by hypermail 2.1.4.