Ok, I got my Airport to generate Beacons on this BE machine. There was a bug hiding in bcm43xx_ram_write(). Current in-tree buggy ram_write() expects swapped input value. So on a LE system it takes a BE value and on a BE system it takes a LE value. After fixing that so that ram_write() takes input in CPU order (as it should be) and after fixing some other endianess bugs in the patch, it generates beacons correctly.
But I can not associate to the bcm43xx-AP. But it seems like a dscape problem. The authentication packet arrives at the machine (I can capture it with the new cool virtual monitor interface), but it is not processed. So the STA does not receive a response. Do you see similiar behaviour? On Monday 12 June 2006 22:01, Alexander Tsvyashchenko wrote: > Hello All, > > Here is AP mode patch that is adapted to the current wireless-dev version > of bcm43xx. > > Signed-off-by: Alexander Tsvyashchenko <[EMAIL PROTECTED]> > > Differencies to the previous version: > > 1) This version deals with TIM in cleaner way (though, PS mode is still > not supported) - instead of patching dscape stack to skip TIM > generation, it strips TIM when writing probe response template and > leaves it when writing beacon template. > > 2) As in current dscape stack management interface seems to be no longer > passed to the driver, all interface handling is left as it is, no > changes there should be made anymore. > > 3) cpu_to_be/le32 were added in the places that seem appropriate for that > (but I still not sure about that enough; my CPU is LE) > > 4) This version includes some fixes to CONFIG_BCM947XX SPROM code: for > each value to be read from nvram it checks whether it is present or not > and uses it only in the case it is present. This change is not strictly > related to AP mode, but just is added as it seems to be more correct, > and I had to do it for my hardware anyway. > > 5) To make debugging of LE/BE issues easier, I've left some debugging > output in templates generation, it can be stripped once all things are > verified & fixed. > > Known limitations: > > 1) PS mode is not supported. > > Testing instructions: > > Although my previous patch to hostapd to make it interoperable with > bcm43xx & dscape has been merged already in their CVS version, due to > the subsequent changes in dscape stack current hostapd is again > incompartible :-( So, to test this patch, the patch to hostapd should be > applied. > I used hostapd snapshot 0.5-2006-06-10, patch for it is attached. > The patch is very hacky and requires tricky way to bring everything up, > but as dscape stack is changed quite constantly, I just do not want to > waste time fixing it in "proper" way only to find a week later that > dscape handling of master interface was changed completely once more and > everything is broken again ;-) > > The patch for dscape stack that is attached is not 100% necessary, but it > seems to allow operating clients that request PS mode to be enabled at > AP (verified with PDA client), the only thing it contains is disabling > actual PS handling in dscape. > > So, the following sequence should be used to test AP mode: > > 1) take hostapd snapshot 0.5-2006-06-10 (other recent versions should > work OK also, though), apply the hostapd patch attached. > > 2) Insert modules (80211, rate_control and bcm43xx-d80211) > > 3) "iwconfig wlan0 mode master" > > 4) "ifconfig wlan0 up" (this should be done by hostapd actually, but > its operation with current dscape stack seems to be broken) > > 5) Start hostapd (f.e. "hostapd -B /etc/hostapd.conf"), config file can > look like: > ===== > interface=wlan0 > driver=devicescape > ssid=OpenWrt > channel=1 > send_probe_response=0 > logger_syslog=-1 > logger_syslog_level=2 > logger_stdout=-1 > logger_stdout_level=2 > debug=4 > ===== > > 6) "iwconfig wlan0 essid <your-SSID-name>" (this also should not be > required, but current combination of hostapd + dscape doesn't seem to > generate config_interface callback when setting beacon, so this is > required just to force call of config_interface). > > That's should be it. > > Please comment! > > Good luck! Alexander > -- Greetings Michael. _______________________________________________ Bcm43xx-dev mailing list [email protected] http://lists.berlios.de/mailman/listinfo/bcm43xx-dev
