On 11/13/2009 06:45 PM, Felix Fietkau wrote: > Gus Wirth wrote: >> On 11/13/2009 03:59 PM, Pavel Roskin wrote: >>> On Fri, 2009-11-13 at 15:26 -0800, Gus Wirth wrote: >>> >>>> # ath_info 0xb0000000 >>>> >>>> And it promptly reboots. >>>> >>>> So at this point I'm not sure if the problem is in the madwifi_multi or >>>> if this won't work with a WiSoC type device to begin with or maybe >>>> something else. >>> >>> You can prevent MadWifi modules from loading by moving them away and >>> rebooting. ath_info doesn't need MadWifi. >>> >>> But if you see ath_info sources, you'll find many references to PCI. >>> Some may be just addresses in EEPROM corresponding to the PCI data, but >>> some may need to be changed for AHB. As the first step, you could run >>> ath_info under gdb to find out where exactly it causes the system to >>> reboot. >>> >> >> Thanks for the tips. It's been a while since I've played with gdb. Guess >> I have my work cut out for me.
> You cannot use ath_info on WiSoC. Not only is the register layout > different from 5212 (especially the reset registers), but it also does > not have a separate EEPROM chip. The eeprom data is stored on the system > flash chip. OK. Guess I don't need to learn how to use gdb again :) Is there some equivalent to ath_info for WiSoC chips or is that something that still needs to be written? Gus _______________________________________________ ath5k-devel mailing list ath5k-devel@lists.ath5k.org https://lists.ath5k.org/mailman/listinfo/ath5k-devel
