From: Gerd Knorr <kraxel@bytesex.org>
To: linux-kernel@vger.kernel.org
Subject: Re: [V4L] [PATCH/RFC] videodev.[ch] redesign
Date: 10 Feb 2002 08:59:45 GMT [thread overview]
Message-ID: <slrna6cdk1.ret.kraxel@bytesex.org> (raw)
In-Reply-To: <20020209194602.A23061@bytesex.org> <200202100203.g1A23To32387@devserv.devel.redhat.com>
Alan Cox wrote:
> > It also provides a ioctl wrapper function which handles copying the
> > ioctl args from/to userspace, so we have this at one place can drop all
> > the copy_from/to_user calls within the v4l device driver ioctl handlers.
> >
> > Comments?
>
> I'm not sure 2.4 should change but for 2.5 this is absolutely bang on
> perfect
For 2.5 I want switch over to using file_operations completely and drop
the old stuff. Thus 2.4 should provide both old+new way to handle
stuff: The old one for backward compatibility and the new one to allow
backporting 2.5.x drivers to 2.4 ...
Yesterday I've booted a 2.5.x kernel the first time and managed to make
bttv work there. 2.5.x version of the will follow ...
Gerd
--
#define ENOCLUE 125 /* userland programmer induced race condition */
next prev parent reply other threads:[~2002-02-10 9:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-09 18:46 [PATCH/RFC] videodev.[ch] redesign Gerd Knorr
2002-02-09 20:53 ` Oliver Neukum
2002-02-09 20:44 ` Gerd Knorr
2002-02-10 0:32 ` Oliver Neukum
2002-02-10 8:34 ` Gerd Knorr
2002-02-09 20:53 ` Oliver Neukum
2002-02-10 2:03 ` [V4L] " Alan Cox
2002-02-10 8:59 ` Gerd Knorr [this message]
2002-02-11 21:10 ` [PATCH/RFC] videodev.[ch] redesign -- take #2 Gerd Knorr
2002-02-10 3:58 ` [V4L] [PATCH/RFC] videodev.[ch] redesign Mark McClelland
2002-02-10 9:11 ` Gerd Knorr
2002-02-10 12:54 ` Mark McClelland
2002-02-11 9:55 ` Gerd Knorr
2002-02-11 11:58 ` Mark McClelland
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=slrna6cdk1.ret.kraxel@bytesex.org \
--to=kraxel@bytesex.org \
--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