From: Piotr Hosowicz <piotr@hosowicz.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Sam Ravnborg <sam@ravnborg.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: ioctl definition - has it changed recently?
Date: Mon, 16 Aug 2010 09:59:36 +0200 [thread overview]
Message-ID: <4C68EFE8.20202@example.com> (raw)
In-Reply-To: <201008160917.23260.arnd@arndb.de>
On 16.08.2010 09:17, Arnd Bergmann wrote:
> On Monday 16 August 2010 09:11:33 Piotr Hosowicz wrote:
>>> and then make it use the unlocked_ioctl operation.
>>
>> This I do not know. Can You help me?
>>
>
> Just take a look at all the other patches that went into the
> kernel to do this for other drivers. You only really
> need to change the line with .ioctl=... to .unlocked_ioctl=
> and change the prototype of the referenced function to
>
> static long foo_ioctl(struct file *file, unsigned int cmd, unsigned long arg)
int nv_kern_ioctl(struct inode *, struct file *, unsigned int,
unsigned long);
It seems different. How to change it? Now it works, I built it without
your remarks, exactly how I described on my blog:
http://phosowicz.jogger.pl/2010/08/15/nvidia-graphics-in-fresh-kernels/
Regards,
Piotr Hosowicz
--
Polsat: oglądasz z rodzinką reklamy, a tu nagle - trach! - film!
NP: Patrick O'Hearn - Chance
NB: 2.6.36-rc1
next prev parent reply other threads:[~2010-08-16 7:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-14 20:53 ioctl definition - has it changed recently? Piotr Hosowicz
2010-08-14 21:00 ` Sam Ravnborg
2010-08-14 22:10 ` Piotr Hosowicz
2010-08-16 6:58 ` Arnd Bergmann
2010-08-16 7:11 ` Piotr Hosowicz
2010-08-16 7:17 ` Arnd Bergmann
2010-08-16 7:59 ` Piotr Hosowicz [this message]
2010-08-17 13:11 ` Piotr Hosowicz
2010-08-17 13:18 ` Arnd Bergmann
2010-08-17 13:51 ` Piotr Hosowicz
2010-08-17 13:59 ` Piotr Hosowicz
2010-08-17 14:33 ` Piotr Hosowicz
2010-08-14 21:02 ` Piotr Hosowicz
[not found] ` <20100814212007.GA26128@nuttenaction>
2010-08-15 8:24 ` Piotr Hosowicz
2010-08-15 11:57 ` Piotr Hosowicz
2010-08-15 14:22 ` Piotr Hosowicz
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=4C68EFE8.20202@example.com \
--to=piotr@hosowicz.com \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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.