On 23.11.2009 08:45 you wrote: > I see it differently. Debugfs is for debugging, not for API. If > you'd use debugfs for it, then you'd force every embedded > developer to compile debugfs into the kernel. Ugly. I agree, but at least it would be some solution for us. We can't afford to maintain patches to ath5k, mac80211 and iw forever.
> Better IMHO is a module parameter if only one hardware / driver > supports this. It couldn't be a module parameter, because it needs to be different for every device. And it would be best if it was tunable at runtime, like it was in Madwifi (via sysctl). > Or really go the way via iw, nl80211, cfg80211 > etc if several drivers support this feature (now or in future). What about providing a higher abstraction, a "distance" parameter instead of acktimeout, csttimeout and slottime? For example 'iw phy0 set distance 3000'. Definitely at least ath9k hardware supports this feature. Lukas Turek
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ ath5k-devel mailing list ath5k-devel@lists.ath5k.org https://lists.ath5k.org/mailman/listinfo/ath5k-devel
