From: Eric W Anderson <Eric.Anderson@Colorado.EDU>
To: Nick Kossifidis <mickflemm@gmail.com>
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>,
Dan Williams <dcbw@redhat.com>,
Johannes Berg <johannes@sipsolutions.net>,
ath5k-devel@lists.ath5k.org, linux-wireless@vger.kernel.org,
John Linville <linville@tuxdriver.com>
Subject: Proc usage (was: Re: [ath5k-devel] [PATCH 3/3] consistently use ath5k in printks)
Date: Tue, 23 Oct 2007 22:25:40 -0600 [thread overview]
Message-ID: <471EC944.2010700@colorado.edu> (raw)
In-Reply-To: <40f31dec0710170926p3847b796gdf52f80297b7c117@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2164 bytes --]
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.
-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.
>
--
Eric W. Anderson University of Colorado
eric.anderson@colorado.edu Dept. of Computer Science
phone: +1-720-984-8864 Systems Research Lab - ECCR 1B54
PGP key fingerprints:
personal: 1BD4 CFCE 8B59 8D6E EA3E EBD5 4DC9 3E61 656C 462B
academic: D3C5 D6FF EDED 9F1F C36D 53A3 74B7 53A6 3C74 5F12
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
next prev parent reply other threads:[~2007-10-24 4:38 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 ` Eric W Anderson [this message]
2007-10-24 6:34 ` Proc usage (was: Re: [ath5k-devel] [PATCH 3/3] consistently use ath5k in printks) Nick Kossifidis
2007-10-24 15:10 ` Dan Williams
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=471EC944.2010700@colorado.edu \
--to=eric.anderson@colorado.edu \
--cc=ath5k-devel@lists.ath5k.org \
--cc=dcbw@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).