On Friday 29 April 2011 03:19:21 Sujith wrote: > Christian Lamparter wrote: > > On Thursday 28 April 2011 10:58:33 Sujith wrote: > > > From: Sujith Manoharan <Sujith.Manoharan@xxxxxxxxxxx> > > > > > > Debugfs file location: <debugfs_mnt>/ieee80211/phy#/ath9k_htc/base_eeprom > > > > > If you just want to dump the eeprom, then why not with a userspace utility? > > It's pretty easy to write such a thing with libusb, furthermore it's more > > versatile and portable so the *BSD-folks are not left out! > > We do have an eeprom dump tool for PCI cards, but hardly any one uses > that. Oh, I used ath_info for ath5k a lot. Especially to get around regdom restrictions. Sure, your tool won't be able to do that, but never the less. > It's much more convenient to use debugging features that are present > in the driver itself. On an embedded board, it makes things a little bit easier. Do you really think that everyone will be happy to recompile their stripped & heavily customised embedded kernels/or compat-wireless just to enable DEBUG and waste precious resources? Even with a PC, this is not necessarily straightforward, especially if the user has never done it before. Regards, Chr -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
