From: Dan Williams <dcbw@redhat.com>
To: Eric W Anderson <Eric.Anderson@Colorado.EDU>
Cc: Nick Kossifidis <mickflemm@gmail.com>,
"Luis R. Rodriguez" <mcgrof@gmail.com>,
Johannes Berg <johannes@sipsolutions.net>,
ath5k-devel@lists.ath5k.org, linux-wireless@vger.kernel.org,
John Linville <linville@tuxdriver.com>
Subject: Re: Proc usage (was: Re: [ath5k-devel] [PATCH 3/3] consistently use ath5k in printks)
Date: Wed, 24 Oct 2007 11:10:01 -0400 [thread overview]
Message-ID: <1193238601.2557.43.camel@localhost.localdomain> (raw)
In-Reply-To: <471EC944.2010700@colorado.edu>
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@gmail.com>:
> >> On 10/17/07, Dan Williams <dcbw@redhat.com> 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@vger.kernel.org
> >> 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.
> >
>
next prev parent reply other threads:[~2007-10-24 15:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-16 13:20 [PATCH 0/3] ath5k: cosmetic renames Bruno Randolf
2007-10-16 13:20 ` [PATCH 1/3] ath5k global rename of hal to hw Bruno Randolf
2007-10-16 13:20 ` [PATCH 2/3] better readability for skb dumps Bruno Randolf
2007-10-16 13:20 ` [PATCH 3/3] consistently use ath5k in printks Bruno Randolf
2007-10-16 16:11 ` Luis R. Rodriguez
2007-10-17 11:14 ` Johannes Berg
2007-10-17 14:09 ` Luis R. Rodriguez
2007-10-17 14:09 ` Dan Williams
2007-10-17 14:19 ` [ath5k-devel] " Luis R. Rodriguez
2007-10-17 16:26 ` Nick Kossifidis
2007-10-24 4:25 ` Proc usage (was: Re: [ath5k-devel] [PATCH 3/3] consistently use ath5k in printks) Eric W Anderson
2007-10-24 6:34 ` Nick Kossifidis
2007-10-24 15:10 ` Dan Williams [this message]
2007-10-24 17:25 ` Luis R. Rodriguez
2007-10-16 16:04 ` [PATCH 2/3] better readability for skb dumps Luis R. Rodriguez
2007-10-16 16:08 ` [PATCH 1/3] ath5k global rename of hal to hw Luis R. Rodriguez
2007-10-16 16:15 ` Nick Kossifidis
2007-10-16 16:23 ` [ath5k-devel] " Luis R. Rodriguez
2007-10-16 16:27 ` Nick Kossifidis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1193238601.2557.43.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--cc=Eric.Anderson@Colorado.EDU \
--cc=ath5k-devel@lists.ath5k.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@gmail.com \
--cc=mickflemm@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox