From: Dan Williams <dcbw@redhat.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Marcel Holtmann <marcel@holtmann.org>,
netdev <netdev@vger.kernel.org>, Jean Tourrilhes <jt@hpl.hp.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] make wext wireless bits optional and deprecate them
Date: Mon, 19 May 2008 11:24:46 -0400 [thread overview]
Message-ID: <1211210686.12187.6.camel@localhost.localdomain> (raw)
In-Reply-To: <1211199368.6252.19.camel@johannes.berg>
On Mon, 2008-05-19 at 14:16 +0200, Johannes Berg wrote:
> > Instead of testing for wireless/, best thing would probably be to call
> > SIOCGIWRANGE on the device and if it returns EOPNOTSUP then it's not
> > wireless. Some drivers may have to load firmware to figure out
> > supported rates and encryption capabilities, but to be honest, NM does
> > this to detect wireless devices and I haven't run into any issues in 4
> > years using it. If there are issues with drivers, then we need to fix
> > the driver too.
>
> I was about to propose calling SIOCGIWNAME since that is what
> wireless-tools do and that linux/wireless.h indicates.
Hmm; NAME is pretty useless. That's fine to do, I guess WEXT requires
that NAME return _something_ at least. NAME should never ever be used
for anything more, but since wireless-tools appears to do this that's
fine.
Dan
next prev parent reply other threads:[~2008-05-19 15:28 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-17 12:12 [RFC] make wext wireless bits optional and deprecate them Johannes Berg
2008-05-17 12:12 ` Johannes Berg
2008-05-17 12:16 ` Johannes Berg
2008-05-17 12:16 ` Johannes Berg
2008-05-17 13:45 ` Marcel Holtmann
2008-05-17 13:54 ` Johannes Berg
2008-05-17 13:54 ` Johannes Berg
2008-05-17 14:36 ` Marcel Holtmann
2008-05-17 14:42 ` Johannes Berg
2008-05-17 14:42 ` Johannes Berg
2008-05-18 13:36 ` Dan Williams
2008-05-18 13:36 ` Dan Williams
2008-05-19 12:16 ` Johannes Berg
2008-05-19 12:16 ` Johannes Berg
2008-05-19 15:22 ` Johannes Berg
2008-05-22 5:59 ` Luis R. Rodriguez
2008-05-19 15:24 ` Dan Williams [this message]
2008-05-19 15:39 ` Johannes Berg
2008-05-19 15:39 ` Johannes Berg
2008-05-19 15:53 ` Dan Williams
2008-05-19 15:53 ` Dan Williams
2008-05-19 17:03 ` Jean Tourrilhes
2008-05-19 17:01 ` Jean Tourrilhes
2008-05-20 17:15 ` Johannes Berg
2008-05-20 17:15 ` Johannes Berg
2008-05-20 17:28 ` Marcel Holtmann
2008-05-21 21:03 ` John W. Linville
2008-05-21 21:03 ` John W. Linville
2008-05-21 21:37 ` Johannes Berg
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=1211210686.12187.6.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--cc=johannes@sipsolutions.net \
--cc=jt@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=netdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.