From: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
To: Dan Williams <dcbw-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: Marcel Holtmann <marcel-kz+m5ild9QBg9hUCZPvPmw@public.gmane.org>,
netdev <netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Jean Tourrilhes <jt-sDzT885Ts8HQT0dZR+AlfA@public.gmane.org>,
linux-wireless
<linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Linux Kernel list
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [RFC] make wext wireless bits optional and deprecate them
Date: Mon, 19 May 2008 14:16:08 +0200 [thread overview]
Message-ID: <1211199368.6252.19.camel@johannes.berg> (raw)
In-Reply-To: <1211117795.686.15.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 589 bytes --]
> 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.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2008-05-19 12:16 UTC|newest]
Thread overview: 17+ 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
[not found] ` <1211026337.3827.25.camel-YfaajirXv214zXjbi5bjpg@public.gmane.org>
2008-05-17 12:16 ` Johannes Berg
2008-05-17 13:45 ` Marcel Holtmann
[not found] ` <CD993362-B1DE-4E4D-8A5B-E9E2AD7DA04C-kz+m5ild9QBg9hUCZPvPmw@public.gmane.org>
2008-05-17 13:54 ` Johannes Berg
2008-05-17 14:36 ` Marcel Holtmann
[not found] ` <31B1A5D6-8E8B-4148-860F-326FEEE5A3EE-kz+m5ild9QBg9hUCZPvPmw@public.gmane.org>
2008-05-17 14:42 ` Johannes Berg
[not found] ` <1211032475.6252.2.camel-YfaajirXv214zXjbi5bjpg@public.gmane.org>
2008-05-18 13:36 ` Dan Williams
[not found] ` <1211117795.686.15.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2008-05-19 12:16 ` Johannes Berg [this message]
2008-05-19 15:24 ` Dan Williams
[not found] ` <1211210686.12187.6.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2008-05-19 15:39 ` Johannes Berg
[not found] ` <1211211547.6252.54.camel-YfaajirXv214zXjbi5bjpg@public.gmane.org>
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:28 ` Marcel Holtmann
[not found] ` <1211303731.6252.105.camel-YfaajirXv214zXjbi5bjpg@public.gmane.org>
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=1211199368.6252.19.camel@johannes.berg \
--to=johannes-cdvu00un1vgdhxzaddlk8q@public.gmane.org \
--cc=dcbw-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=jt-sDzT885Ts8HQT0dZR+AlfA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=marcel-kz+m5ild9QBg9hUCZPvPmw@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).