public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Kilian <kilian@bobodyne.com>
To: linux-kernel@vger.kernel.org
Subject: Where is a reference for ioctl32() usage?
Date: Fri, 18 Mar 2005 08:53:52 -0600	[thread overview]
Message-ID: <1111157632.11071.92.camel@desk> (raw)
In-Reply-To: <1111103837.11071.83.camel@desk>



    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>



  reply	other threads:[~2005-03-18 14:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-17 23:57 Where is a reference for ioctl32() usage? Alan Kilian
2005-03-18 14:53 ` Alan Kilian [this message]
2005-03-18 15:12   ` Arnd Bergmann

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=1111157632.11071.92.camel@desk \
    --to=kilian@bobodyne.com \
    --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