mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: William D Waddington <william.waddington@beezmo.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFCLUE2] 64 bit driver 32 bit app ioctl
Date: Thu, 23 Mar 2006 10:33:32 -0800	[thread overview]
Message-ID: <4422E9FC.8060303@beezmo.com> (raw)
In-Reply-To: <1143132597.3147.31.camel@laptopd505.fenrus.org>

Arjan van de Ven wrote:
> On Thu, 2006-03-23 at 07:06 -0800, William D Waddington wrote:
> 
>>Apologies for dashing this off without the proper homework.  My
>>customer is out of country doing an installation, and didn't test
>>this configuration first :(
>>
>>Customer is running RHEL3 on a 64 bit PC.  Running the 64 bit kernel
>>and my 64 bit driver.  They are calling the driver from their 32 bit
>>app.  The driver supports a whole mess of ioctls.
>>
>>It seems that the kernel is trapping the 32-bit ioctl call and returning
>>an error to the app w/out calling the driver.  It looks like
>>register_ioctl32_conversion() can convice the kernel that the driver can
>>handle 32-bit calls, but it has to be called for each ioctl cmd (??)
> 
> 
> you forgot to attach you code btw or post the url to it..

No I didn't :) It's just too ugly for public view.  And I notice it
needs some other fix-ups like fixed width data types in the ioctl
routine...

Thanks to all for the info.  I've got some typing to do.

Bill


      parent reply	other threads:[~2006-03-23 18:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-23 15:06 William D Waddington
2006-03-23 16:42 ` Mikael Pettersson
2006-03-24 19:00   ` William D Waddington
2006-03-23 16:49 ` Arjan van de Ven
2006-03-23 16:57   ` Avi Kivity
2006-03-23 18:33   ` William D Waddington [this message]

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=4422E9FC.8060303@beezmo.com \
    --to=william.waddington@beezmo.com \
    --cc=arjan@infradead.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

Powered by JetHome