On Sat, Nov 15, 2008 at 09:48:13PM -0800, Luis R. Rodriguez wrote: > Not sure why its 00000001, nor do I know if its poison. One thing I am > fairly positive about is that the reason why this was wrong all along > was because we were trying to get the device's ->driver structure to > get driver->name but the device won't get its ->driver pointer > assigned until *after* a successful probe. Lets review the PCI probe: No, as I later corrected myself, that is pci_dev->driver, but what mac80211 is using is pci_dev->dev.driver. Which actually happens to be set up fine. (I verified this by inserting a printk into the ath5k driver and it all works fine.) > Yeah don't bother, the issue on this e-mail was fixed, another issue > has come up though so that is separate. I think the second issue is just the first issue, but the fix papered over the first bug. -- 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
