2008/5/8 Nick Kossifidis <[EMAIL PROTECTED]>: > > I stored init_val but forgot to write it at the end of the for loop ! > Static values found on ndiswrapper dumps don't show up in madwifi > traces, that's why i put the comment there, i also see them in RF2425 > ndiswrapper dumps so there is no need to remove them. > > ndiswrapper dump from 2425...
That's strange, I made my ath_pci trace with MmIoTrace and I don't see theses constants values. > > hw_post doesn't have that much impact on card's operation, even when > we didn't have hw_post and STA_ID0 had init_val all the time during > attach, 2425 didn't work. Did you see any change when you restored > init_val ? Did the card wok ? No :-D In fact I was afraid a small mistake could hide one other. > > About the eeprom, what do you mean the registers are read in the wrong > place ? All header information is simmilar with older eeprom versions, > mac address is still in the right place and other cards with EEPROM > version > 5 are working fine (2413/5413 for example). We still miss tx > power calibration data, if you have anything plz feel free to expand > ath_info tool (most development related to eeprom rev. engineering is > going on there), have in mind that power mask has changed i think from > 0x3f to 0x7f. I said that because EEPROM_MAGIC is 0 when read on an AR2425. EEPROM_PROTECT is also 0 but it's perhaps correct. And it sems that Madwifi is interested in other data offsets than the actuals. From example it reads thoses fields during the eeprom_init: _1 (value = 0) _1c (value = 0) But actually I don't have anything new for eeprom to expand ath_info. So where could be the real problem with AR2425 if EEPROM adresses are correct (for the most important fields)...?
_______________________________________________ ath5k-devel mailing list ath5k-devel@lists.ath5k.org https://lists.ath5k.org/mailman/listinfo/ath5k-devel
