On 09/30/2011 01:15 AM, Stefan Zwanenburg wrote: > On 09/29/2011 10:55 AM, 李朝明 wrote: >> Dear Larry: >> >> I don't kown why this efuse is wrong, did Zwanenburg use the same >> driver with yours ? > Hi! > I may be no Larry, but I just diffed the latest version of the > drivers/net/wireless/rtlwifi directory (obtained from the github mirror > of linus' repository) with the one from the kernel I'm currently > running, and I don't notice a whole lot of changes (besides code > cleanups and differences in the debugging macro "calls"), but there is > something going on in efuse.c with no more "hoffset" variable in > efuse_get_current size, but that shouldn't matter, as the variable was > assigned but never used again. > I also see there was a whole lot of work put into pci.c, as it looks > it's had a revamp. I'm not sure it will fix my problems, but I'm going > to try to run 3.1-rc4 and see if I can get an 802.11n link going. > > I'll get back to you on how that went later! > > Stefan Zwanenburg Well, I just compiled 3.0-rc4, and I'm now running it, but alas, still no 802.11n link to my AP, and (perhaps unsurprisingly) the EEPROM that gets dumped upon detecting the PCI NIC is exactly the same as it was before, so there couldn't be some problem with the EFUSE reading code. I guess that leaves us with the possibility my AP is not sending some packets (see Larry's message about that) during the association, which makes the driver not work as it should... Is there anything else I can try to help you guys figure out what may be wrong? Stefan Zwanenburg PS: I'll keep running this kernel for a few days to see if I get the same problem as in mentioned in the discussion "3.1-rc6 + rtl8192se issue", even though I apparently don't have the very latest kernel source. -- 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
