All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.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: Wed, 21 May 2008 17:03:52 -0400	[thread overview]
Message-ID: <20080521210352.GA11827@tuxdriver.com> (raw)
In-Reply-To: <1211303731.6252.105.camel@johannes.berg>

On Tue, May 20, 2008 at 07:15:31PM +0200, Johannes Berg wrote:
> On Sat, 2008-05-17 at 15:45 +0200, Marcel Holtmann wrote:
> > Hi Johannes,
> > 
> > > The /sys/class/net/*/wireless/ direcory is, as far as I know, not
> > > used by anyone. Additionally, the same data is available via wext
> > > ioctls. Hence the sysfs files are pretty much useless. This patch
> > > makes them optional and schedules them for removal.
> > 
> > it is used by HAL to classify WiFi network cards as net.80211 instead  
> > of net.80203 and so we do have an actual user. However HAL only tests  
> > for the existence of the directory wireless/.
> > 
> > Please fix HAL first before submitting such a patch.
> 
> I have filed a patch to fix HAL to use the canonical SIOCGIWNAME at
> https://bugs.freedesktop.org/show_bug.cgi?id=16037. Any further
> objections to this patch?

I think this is going to fall under the "userland ABI" category.
We can make it a configurable option, but I don't think we are free
to remove it completely since there is at least existing versions of
HAL that use it.

John
-- 
John W. Linville
linville@tuxdriver.com

WARNING: multiple messages have this Message-ID (diff)
From: "John W. Linville" <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
To: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@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: Wed, 21 May 2008 17:03:52 -0400	[thread overview]
Message-ID: <20080521210352.GA11827@tuxdriver.com> (raw)
In-Reply-To: <1211303731.6252.105.camel-YfaajirXv214zXjbi5bjpg@public.gmane.org>

On Tue, May 20, 2008 at 07:15:31PM +0200, Johannes Berg wrote:
> On Sat, 2008-05-17 at 15:45 +0200, Marcel Holtmann wrote:
> > Hi Johannes,
> > 
> > > The /sys/class/net/*/wireless/ direcory is, as far as I know, not
> > > used by anyone. Additionally, the same data is available via wext
> > > ioctls. Hence the sysfs files are pretty much useless. This patch
> > > makes them optional and schedules them for removal.
> > 
> > it is used by HAL to classify WiFi network cards as net.80211 instead  
> > of net.80203 and so we do have an actual user. However HAL only tests  
> > for the existence of the directory wireless/.
> > 
> > Please fix HAL first before submitting such a patch.
> 
> I have filed a patch to fix HAL to use the canonical SIOCGIWNAME at
> https://bugs.freedesktop.org/show_bug.cgi?id=16037. Any further
> objections to this patch?

I think this is going to fall under the "userland ABI" category.
We can make it a configurable option, but I don't think we are free
to remove it completely since there is at least existing versions of
HAL that use it.

John
-- 
John W. Linville
linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2008-05-21 21:34 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
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 [this message]
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=20080521210352.GA11827@tuxdriver.com \
    --to=linville@tuxdriver.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.