From: Jeff Garzik <jgarzik@pobox.com>
To: Max Krasnyansky <maxk@qualcomm.com>
Cc: "David S. Miller" <davem@redhat.com>,
pavel@ucw.cz, linux-kernel@vger.kernel.org,
torvalds@transmeta.com, ak@suse.de
Subject: Re: ioctl32 consolidation
Date: Thu, 20 Feb 2003 20:40:13 -0500 [thread overview]
Message-ID: <3E55837D.5010607@pobox.com> (raw)
In-Reply-To: <5.1.0.14.2.20030220172624.0d4c5070@mail1.qualcomm.com>
Max Krasnyansky wrote:
> Hmm. It seems to that all you need for SIOCDEVPRIVATE is ability to register
> ranges of ioctls.
> i.e. something like this
> int register_ioctl32_conversion_rage(uint start, uint end, handler);
>
> net/core/dev.c
> register_ioctl32_conversion_range(SIOCDEVPRIVATE, SIOCDEVPRIVATE + 15, siocdevprivate_ioctl);
>
> Am I missing something here ?
Yes. Think about the name of the ioctl :)
It is impossible for generic arch code to implement support for
driver-private ioctls, because these naturally differ between each driver.
Jeff
next prev parent reply other threads:[~2003-02-21 1:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-20 22:31 ioctl32 consolidation Pavel Machek
2003-02-20 22:44 ` Jeff Garzik
2003-02-21 11:34 ` Pavel Machek
2003-02-21 11:58 ` Andi Kleen
2003-02-21 23:21 ` David S. Miller
2003-03-01 19:49 ` Anton Blanchard
2003-02-20 22:56 ` Max Krasnyansky
2003-02-20 23:10 ` Jeff Garzik
2003-02-21 0:36 ` David S. Miller
2003-02-21 1:31 ` Max Krasnyansky
2003-02-21 1:40 ` Jeff Garzik [this message]
2003-02-21 3:20 ` David S. Miller
[not found] <20030221114011$5b98@gated-at.bofh.it>
[not found] ` <20030221114011$7728@gated-at.bofh.it>
[not found] ` <20030221114011$25df@gated-at.bofh.it>
2003-02-21 22:27 ` Arnd Bergmann
-- strict thread matches above, loose matches on Subject: below --
2003-02-24 10:05 Martin Schwidefsky
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=3E55837D.5010607@pobox.com \
--to=jgarzik@pobox.com \
--cc=ak@suse.de \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maxk@qualcomm.com \
--cc=pavel@ucw.cz \
--cc=torvalds@transmeta.com \
/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.