On Tue, 2007-10-23 at 22:25 -0600, Eric W Anderson wrote: > I realize that primary role of the driver is for actual use, rather than for > research, but... It's very useful in experiments to have /proc entries for all > the settings that you don't normally think of as tunable. (e.g. turning off > antenna diversity, or ACKs, or changing the CCA thresholds). I'd really hate for > knobs to go away because someone things they're not "really" needed, or because > they're not worth merging into the new configuration framework. debugfs is one answer here. The point is to make it 110% crystal clear what options are long-term supportable as API/ABI and which ones are not. > -Eric > > Nick Kossifidis wrote: > > 2007/10/17, Luis R. Rodriguez <mcgrof@xxxxxxxxx>: > >> On 10/17/07, Dan Williams <dcbw@xxxxxxxxxx> wrote: > >>> On Wed, 2007-10-17 at 13:14 +0200, Johannes Berg wrote: > >>>> On Tue, 2007-10-16 at 22:20 +0900, Bruno Randolf wrote: > >>>> > >>>>> the proc interface changed too from /proc/sys/dev/ath/ to /proc/sys/dev/ath5k/ > >>>> Ok, and why exactly is there a proc interface at all? > >>> Yeah, it needs to die, we're not adding new proc interfaces to the > >>> kernel. Stuff should be evaluated to see whether it's _really_ needed, > >>> and if for some reason it is, merged into mac80211 or cfg80211, and then > >>> if that doesn't work, > >> Agreed 200%. Die proc usage! > >> > >>> then maybe something in sysfs. > >> Nah, configfs for generic configuration of kernel objects. I already > >> have such module but it just had regdomain support. I plan on adding > >> add/remove iface. > >> > >> 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 > >> > > > > I've already removed the whole proc stuff along with debug stuff in > > base.c in madwifi-svn, i'll port patch here asap. > > > - 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
