En/na Adrian Chadd ha escrit: > I think a large part of the problem here is that the focus of the > active technical developers is elsewhere.
Where? > You should see what trouble > I've had getting questions answered here for the pre-AR9200 stuff. :-) > > Eg, trying to figure out the above - I have no idea. "10% of expected > performance" is pretty low, but is it a hardware poking problem, or is > it a wifi configuration problem? How do you know, for example, that > all of the board PCI/interrupt stuff is setup right? Well, I don't, I just hope that it is so. > Are there any > other PCI devices that are working at the correct throughput? > IIRC the wifi chip is the only device on PCI (but I could be wrong, I'll double check when I can). > The fact the PCI IDs are different may also be of interest. Have you > done some digging to try and establish why that is the case? Most probably because the device has no internal eeprom. Apparently the ar71xx platform had the same kind of problem, fixed by poking some registers with the data from the flash, but I don't have any ar71xx device to test, I just inferred that from the openwrt code (hence my original question) > Finally, is there any vendor-supplied code for this board? No, the board originally uses a propietary os with no documentation (and much less sources) available (in fact they went out of their way to obfuscate the original firmware in order to make it difficult to load alternatives), however 1) from the log messages it seems it's using ath9k (i.e. the messages are exactly the same as the ones I found in ath9k sources) 2) even the original firmware identifies it as ff1d, but then it sees it as 0029 (just like after the pci fixup I copied from the ar71xx but with the endianness problem I asked about). Bye -- Luca _______________________________________________ ath9k-devel mailing list [email protected] https://lists.ath9k.org/mailman/listinfo/ath9k-devel
