From: Jean Tourrilhes <jt@bougret.hpl.hp.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Wireless Extension update
Date: Mon, 15 Oct 2001 09:37:05 -0700 [thread overview]
Message-ID: <20011015093705.A22660@bougret.hpl.hp.com> (raw)
In-Reply-To: <20011008191247.B6816@bougret.hpl.hp.com> <200110150008.RAA09482@cesium.transmeta.com>
In-Reply-To: <200110150008.RAA09482@cesium.transmeta.com>; from hpa@zytor.com on Sun, Oct 14, 2001 at 05:08:16PM -0700
On Sun, Oct 14, 2001 at 05:08:16PM -0700, H. Peter Anvin wrote:
> Followup to: <20011008191247.B6816@bougret.hpl.hp.com>
> By author: Jean Tourrilhes <jt@bougret.hpl.hp.com>
> In newsgroup: linux.dev.kernel
> > /* -------------------------- IOCTL LIST -------------------------- */
> > @@ -137,6 +144,8 @@
> > #define SIOCGIWRANGE 0x8B0B /* Get range of parameters */
> > #define SIOCSIWPRIV 0x8B0C /* Unused */
> > #define SIOCGIWPRIV 0x8B0D /* get private ioctl interface info */
> > +#define SIOCSIWSTATS 0x8B0E /* Unused */
> > +#define SIOCGIWSTATS 0x8B0F /* Get /proc/net/wireless stats */
> >
> > /* Mobile IP support */
> > #define SIOCSIWSPY 0x8B10 /* set spy addresses */
> > @@ -177,11 +186,33 @@
> > #define SIOCSIWPOWER 0x8B2C /* set Power Management settings */
> > #define SIOCGIWPOWER 0x8B2D /* get Power Management settings */
> >
>
> Please, pretty please, use _IOC() macros...
>
> -hpa
Already discussed countless times since 96, same answer as
before : not possible.
For normal devices, you have the full ioctl range, so you can
afford to "waste" this space by coding type/direction in the ioctl
number.
For networking devices, only a *very* small portion of the
ioctl space goes to the driver (because the various networking
components grab tons of them), so we are required to be more
efficient.
In summary : if you convert all the regular ifconfig ioctls
(see .../include/linux/sockios.h) to use _IOC() macros and workaround
ioctl space limitation for networking devices, then I'll fix the
wireless ioctls.
Regards,
Jean
next prev parent reply other threads:[~2001-10-15 16:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-09 2:12 Jean Tourrilhes
2001-10-09 16:22 ` Randy.Dunlap
2001-10-09 16:35 ` Jean Tourrilhes
2001-10-14 21:58 ` Riley Williams
2001-10-15 0:07 ` H. Peter Anvin
2001-10-15 19:26 ` Roeland Th. Jansen
2001-10-15 19:31 ` H. Peter Anvin
2001-10-15 21:02 ` Tobias Ringstrom
2001-10-15 0:08 ` H. Peter Anvin
[not found] ` <200110150008.RAA09482@cesium.transmeta.com>
2001-10-15 16:37 ` Jean Tourrilhes [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-03-29 2:12 Jean Tourrilhes
2000-12-20 0:59 Jean Tourrilhes
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=20011015093705.A22660@bougret.hpl.hp.com \
--to=jt@bougret.hpl.hp.com \
--cc=hpa@zytor.com \
--cc=jt@hpl.hp.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®