On Tue, Dec 15, 2009 at 2:52 PM, Lukáš Turek <8an@xxxxxxxxxxx> wrote: > The problem is, I don't know any hardware that really sends the coverage > class. There's a lot of hardware that allows setting only the ACK timeout, > like all the Ubiquity devices, Ovislink 5000 and so on. So the client > connecting to these devices will need to specify the coverage class manually. You have a good point here. > When the coverage class is sent in beacons, it should take precedence over the > user-specified value, I'm not against that. OK. > It's just not relevant now, until > there's a hardware that sends it or until the hostap part is done. And I said > I want to do that, just not in this series, it's already problematic > enough... OK, yeah you have a good point. > And about the debugfs: originaly I thought i would just implement a simple > debugfs API for setting ACK/CTS timeout and slot time. However, Johannes Berg > recommended me to do this coverage class thing and I didn't envision how much > trouble it's gonna be... Thanks a lot for your work on this! Luis -- 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
