From: Grant Grundler <grundler@cup.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] platform detection at run-time
Date: Wed, 25 Sep 2002 20:45:21 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590701906065@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701906051@msgid-missing>
Sane_Purushottam@emc.com wrote:
> The reason, I have to detect the architecture at run time has to do with the
> interface with (sg) driver. Since the driver is natively compiled for
> 64-bit, it expects the data structure handed over to it, to be 64-bit wide.
> Thus my 32-bit application cannot issue ioctl calls successfully.
isn't "arch/*/kernel/ioctl32.c" the place to handle this kind of conversion?
grundler <514>fgrep SG arch/parisc/kernel/ioctl32.c
COMPATIBLE_IOCTL(FDMSGON)
COMPATIBLE_IOCTL(FDMSGOFF)
COMPATIBLE_IOCTL(FDSETEMSGTRESH)
/* SG stuff */
COMPATIBLE_IOCTL(SG_SET_TIMEOUT)
COMPATIBLE_IOCTL(SG_GET_TIMEOUT)
COMPATIBLE_IOCTL(SG_EMULATED_HOST)
COMPATIBLE_IOCTL(SG_SET_TRANSFORM)
...
ia64 seems to drop this kind of thing in arch/ia64/ia32/ia32_ioctl.c
> So, in my application, based on the platform, I fill the appropriate
> structure before ioctl call.
putting it in the application sounds like the wrong thing to do.
grant
next prev parent reply other threads:[~2002-09-25 20:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-25 18:18 [Linux-ia64] platform detection at run-time Sane_Purushottam
2002-09-25 18:22 ` Don Dugger
2002-09-25 18:35 ` Nathan Straz
2002-09-25 18:46 ` David Mosberger
2002-09-25 18:48 ` David Mosberger
2002-09-25 18:57 ` Nathan Straz
2002-09-25 19:00 ` Joe Griffin
2002-09-25 19:05 ` David Mosberger
2002-09-25 19:28 ` Van Maren, Kevin
2002-09-25 19:33 ` Sane_Purushottam
2002-09-25 19:40 ` Wichmann, Mats D
2002-09-25 19:48 ` David Mosberger
2002-09-25 20:45 ` Grant Grundler [this message]
2002-09-25 21:07 ` Don Dugger
2002-09-25 21:25 ` Sane_Purushottam
2002-09-25 23:29 ` David Mosberger
2002-09-26 4:32 ` Don Dugger
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=marc-linux-ia64-105590701906065@msgid-missing \
--to=grundler@cup.hp.com \
--cc=linux-ia64@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