On Tue, Mar 17, 2009 at 03:36:32PM -0700, Luis R. Rodriguez wrote: > > ACK on FF1A -- 802.11abg, NACK on the others, we don't at least have > > them in our own windows driver INF file. > > Actually so any 0xFF1x device ID where x is any value would > be the ID if the card has issues reading our EEPROM and in that > case you can expect the card to simply not be operational, so feel > free to add it but be sure to inform the user the card is having > issues reading the EEPROM and simply disable the device. In light of that, I'm inclined to just leave it alone then unless someone appears with such IDs. -- Bob Copeland %% www.bobcopeland.com -- 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
