2009/8/27 Luis R. Rodriguez <mcgrof@xxxxxxxxx>: > On Thu, Aug 27, 2009 at 11:17 AM, Bob Copeland<bcopeland@xxxxxxxxx> wrote: >> On Thu, Aug 27, 2009 at 8:58 AM, Nick Kossifidis<mickflemm@xxxxxxxxx> wrote: >>> 2009/8/27 Pavel Roskin <proski@xxxxxxx>: >> >>> Current code works fine (i 've checked it against various cards), >>> there is nothing wrong >>> with having another function for reading turbo modes, i find it's >>> cleaner that way. >> >> Well, we also don't use the turbo modes at all and that's where the >> error is (IIRC) so it shouldn't have any impact. :) > > Again, why don't we just remove all that fucking turbo cruft? > > Luis > Why should we remove it, we are discussing on implementing channel width setting for 5 and 10 MHz channels already so where is the problem supporting turbo mode (40MHz) ? Also EEPROM code should read the eeprom and fill the structs, since these infos are there we should read them, i don't see any reason to skip them, i thought our goal was to support this hw as much as possible, if we want to get rid of MadWiFi we 'll have to at least support 5, 10 and 40MHz (turbo) channels. I understand that there is no support yet on mac80211/cfg80211 but i don't think removing all this stuff and bring it back is the right thing to do. -- GPG ID: 0xD21DB2DB As you read this post global entropy rises. Have Fun ;-) Nick -- 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
