Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Jiri Benc <jbenc@suse.cz>
Cc: linux-wireless@vger.kernel.org
Subject: Re: question: /sys/class/net/*/wireless
Date: Wed, 21 Mar 2007 15:16:44 +0100	[thread overview]
Message-ID: <1174486604.4230.41.camel@johannes.berg> (raw)
In-Reply-To: <20070321151231.0a912abf@griffin.suse.cz>

[-- Attachment #1: Type: text/plain, Size: 730 bytes --]

On Wed, 2007-03-21 at 15:12 +0100, Jiri Benc wrote:

> Why it won't work? If you have wext-compat configured, you have the
> 'wireless' directory (and 'ieee80211' as well). If you don't have
> wext-compat, you don't have the 'wireless' directory. But tools which
> depend on wext won't work then anyway, so no difference here.
> 
> Or am I missing some special cases?

No, that's all ok, but I don't think people (will) realise that wext has
influence into sysfs. Actually, it isn't created by wext-common but
net/core/net-sysfs.c so we'll have to actually make that create all the
stuff with wext-compat too. Which again sucks but may work out
differently after all if James makes wext-compat use wext.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]

      reply	other threads:[~2007-03-21 14:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-03 11:18 question: /sys/class/net/*/wireless Johannes Berg
2007-03-03 11:27 ` Johannes Berg
2007-03-03 17:40   ` Jouni Malinen
2007-03-03 19:53     ` Johannes Berg
2007-03-04  0:21   ` Johannes Berg
2007-03-16 14:03     ` Jiri Benc
2007-03-16 17:07       ` Johannes Berg
2007-03-21 14:12         ` Jiri Benc
2007-03-21 14:16           ` Johannes Berg [this message]

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=1174486604.4230.41.camel@johannes.berg \
    --to=johannes@sipsolutions.net \
    --cc=jbenc@suse.cz \
    --cc=linux-wireless@vger.kernel.org \
    /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