public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* Where is a reference for ioctl32() usage?
@ 2005-03-17 23:57 Alan Kilian
  2005-03-18 14:53 ` Alan Kilian
  0 siblings, 1 reply; 3+ messages in thread
From: Alan Kilian @ 2005-03-17 23:57 UTC (permalink / raw)
  To: linux-kernel


    Thanks for all the help in the past, and I'm once again knocking
    at your door for more help.

    I am trying to get my PCI bus device driver running on an Xeon 
    64-bit FC-3 distribution.

    I got the compiler warnings all cleaned up, the driver compiles and 
    loads, but the test executable which was compiled on a 32-bit FC-3 
    distribution is causing these messages in /var/log/messages:

	Mar 17 15:42:55 noble kernel: ioctl32(boardtest:3730): 
	Unknown cmd fd(3) cmd(8004440e){00} arg(ffffd824) on /dev/sse0
	Mar 17 15:42:55 noble kernel: ioctl32(boardtest:3730): 
	Unknown cmd fd(3) cmd(8004440e){00} arg(ffffd8c4) on /dev/sse0
	Mar 17 15:42:55 noble kernel: ioctl32(boardtest:3730): 
	Unknown cmd fd(3) cmd(40044414){00} arg(00000000) on /dev/sse0
	Mar 17 15:42:55 noble kernel: ioctl32(boardtest:3730): 
	Unknown cmd fd(3) cmd(80044403){00} arg(0804f780) on /dev/sse0

    It's probably a simple thing to change my ioctl() interface in the
    driver, but I googled myself blue in the face, and I didn't find it,
    so I come to you, hat-in-hand for help.

    Where can I find out how to change my driver so I can have a 32-bit
    executable talk to it using ioctl()?

    I did change the "type" argument in _IOR and _IOW to uint32_t from
    int, but that didn't change things.

			-Alan

-- 
- Alan Kilian <kilian(at)bobodyne.com>



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

* Where is a reference for ioctl32() usage?
  2005-03-17 23:57 Where is a reference for ioctl32() usage? Alan Kilian
@ 2005-03-18 14:53 ` Alan Kilian
  2005-03-18 15:12   ` Arnd Bergmann
  0 siblings, 1 reply; 3+ messages in thread
From: Alan Kilian @ 2005-03-18 14:53 UTC (permalink / raw)
  To: linux-kernel



    Thanks for all the help in the past, and I'm once again knocking
    at your door for more help.

    I am trying to get my PCI bus device driver running on an Xeon 
    64-bit FC-3 distribution for the first time. It works fine on a
    32-bit FC-3 distribution.

    I got the compiler warnings all cleaned up, the driver compiles and 
    loads, but the test executable which was compiled on a 32-bit FC-3 
    distribution is causing these messages in /var/log/messages:

	Mar 17 15:42:55 noble kernel: ioctl32(boardtest:3730): 
	Unknown cmd fd(3) cmd(8004440e){00} arg(ffffd824) on /dev/sse0
	Mar 17 15:42:55 noble kernel: ioctl32(boardtest:3730): 
	Unknown cmd fd(3) cmd(8004440e){00} arg(ffffd8c4) on /dev/sse0
	Mar 17 15:42:55 noble kernel: ioctl32(boardtest:3730): 
	Unknown cmd fd(3) cmd(40044414){00} arg(00000000) on /dev/sse0
	Mar 17 15:42:55 noble kernel: ioctl32(boardtest:3730): 
	Unknown cmd fd(3) cmd(80044403){00} arg(0804f780) on /dev/sse0

    It's probably a simple thing to change my ioctl() interface in the
    driver, but I googled myself blue in the face, and I didn't find it,
    so I come to you, hat-in-hand for help.

    Where can I find out how to change my driver so I can have a 32-bit
    executable talk to it using ioctl()?

    I did change the "type" argument in _IOR and _IOW to uint32_t from
    int, but that didn't change things.

			-Alan

-- 
- Alan Kilian <kilian(at)bobodyne.com>



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

* Re: Where is a reference for ioctl32() usage?
  2005-03-18 14:53 ` Alan Kilian
@ 2005-03-18 15:12   ` Arnd Bergmann
  0 siblings, 0 replies; 3+ messages in thread
From: Arnd Bergmann @ 2005-03-18 15:12 UTC (permalink / raw)
  To: Alan Kilian; +Cc: linux-kernel

On Freedag 18 März 2005 15:53, Alan Kilian wrote:
>     I am trying to get my PCI bus device driver running on an Xeon 
>     64-bit FC-3 distribution for the first time. It works fine on a
>     32-bit FC-3 distribution.

You should add a compat_ioctl file operation, see
http://lwn.net/Articles/119652/. If your ioctl handler is
64/32 bit clean, you can have a single function for both
unlocked_ioctl and compat_ioctl.

 Arnd <><

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

end of thread, other threads:[~2005-03-18 15:14 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-03-17 23:57 Where is a reference for ioctl32() usage? Alan Kilian
2005-03-18 14:53 ` Alan Kilian
2005-03-18 15:12   ` Arnd Bergmann

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox