LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
* Ioctl
@ 2011-01-31 19:39 Brian D. McGrew
  2011-01-31 19:51 ` Ioctl Randy Dunlap
  2011-01-31 19:55 ` Ioctl Jonathan Corbet
  0 siblings, 2 replies; 3+ messages in thread
From: Brian D. McGrew @ 2011-01-31 19:39 UTC (permalink / raw)
  To: linux-kernel

Hello,

I'm very new at working with the kernel and device drivers and I'm trying to
bring ours drivers up from a 2.6.16 kernel to 2.6.37.  I'm noticing that
ioctl() doesn't seem to be raound anymore, or at least I can't find it.

There is tons of stuff in my code that I don't yet understand which requires
the ioctl function.  What is the best way for me to either get the ioctl
working in 2.6.37, or the quickest way to work around it???

Thanks,

-b


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Ioctl
  2011-01-31 19:39 Ioctl Brian D. McGrew
@ 2011-01-31 19:51 ` Randy Dunlap
  2011-01-31 19:55 ` Ioctl Jonathan Corbet
  1 sibling, 0 replies; 3+ messages in thread
From: Randy Dunlap @ 2011-01-31 19:51 UTC (permalink / raw)
  To: Brian D. McGrew; +Cc: linux-kernel

On Mon, 31 Jan 2011 11:39:13 -0800 Brian D. McGrew wrote:

> Hello,
> 
> I'm very new at working with the kernel and device drivers and I'm trying to
> bring ours drivers up from a 2.6.16 kernel to 2.6.37.  I'm noticing that
> ioctl() doesn't seem to be raound anymore, or at least I can't find it.
> 
> There is tons of stuff in my code that I don't yet understand which requires
> the ioctl function.  What is the best way for me to either get the ioctl
> working in 2.6.37, or the quickest way to work around it???

ioctl() is still around.

fs/ioctl.c:
SYSCALL_DEFINE3(ioctl, unsigned int, fd, unsigned int, cmd, unsigned long, arg)
{

---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Ioctl
  2011-01-31 19:39 Ioctl Brian D. McGrew
  2011-01-31 19:51 ` Ioctl Randy Dunlap
@ 2011-01-31 19:55 ` Jonathan Corbet
  1 sibling, 0 replies; 3+ messages in thread
From: Jonathan Corbet @ 2011-01-31 19:55 UTC (permalink / raw)
  To: Brian D. McGrew; +Cc: linux-kernel

On Mon, 31 Jan 2011 11:39:13 -0800
"Brian D. McGrew" <brian@visionpro.com> wrote:

> I'm very new at working with the kernel and device drivers and I'm trying to
> bring ours drivers up from a 2.6.16 kernel to 2.6.37.  I'm noticing that
> ioctl() doesn't seem to be raound anymore, or at least I can't find it.

What you almost certainly want is unlocked_ioctl(), which handles ioctl()
calls but lacks the protection of the (soon to be removed) big kernel
lock.  If your driver is properly written, you should have no problem
using unlocked_ioctl(), but do note that the function prototype is a
little different.

jon

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2011-01-31 20:23 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-01-31 19:39 Ioctl Brian D. McGrew
2011-01-31 19:51 ` Ioctl Randy Dunlap
2011-01-31 19:55 ` Ioctl Jonathan Corbet

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).