On 26 February 2013 19:29, Luis R. Rodriguez <mcgrof@xxxxxxxxxxxxxxxx> wrote: > NACK. This comes up every now and then and this is not a valid device > ID, this is an issue with the card, so what you can do is adjust the > device ID post bootup. Not sure if distros have an easy way to set > this up, if not perhaps this should be considered as this has come up > twice before. The erroneous 0xFFFF value comes from using one of eeprom_ops implementations. Do you suggest I should fool ath regd code to think this is a different card so it picks a different (perhaps correct, if at all) eeprom_ops variant? How do I do that? >From what I can tell this is in the pci probing and I can't see any way to skip the regd initialisation. I don't see how current_rd can have a value other than 0xFFFF for this device in this code path. Or am I missing something? -- Michal. -- 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
