* Re: how to add 32/64 compatible ioctls at runtime via module?
@ 2004-12-14 17:27 Mikael Pettersson
2004-12-14 17:31 ` Jan Engelhardt
2004-12-14 17:40 ` Chris Friesen
0 siblings, 2 replies; 4+ messages in thread
From: Mikael Pettersson @ 2004-12-14 17:27 UTC (permalink / raw)
To: cfriesen, linux-kernel
On Tue, 14 Dec 2004 10:39:14 -0600, Chris Friesen wrote:
>I'm working on a driver for 2.6.
>
>I'd like to be able to load the driver as a module, and have it register for
>various ioctl() calls on a device node (which can be dynamic, so no problem there).
>
>I'm not sure how to go about registering at runtime for 32/64 bit compatibility
>so that I can load a module into a ppc64 kernel, and have 32-bit userspace code
>call those ioctls.
>
>Can anyone give some pointers, or direct me to existing code?
register_ioctl32_conversion(ioctl, handler)
tells your 64-bit kernel that the given ioctl, when issued by
a 32-bit mode task, should be routed to the given handler.
The handler can be NULL, in which case the ioctl is routed to
the normal handler via the filp.
/Mikael
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: how to add 32/64 compatible ioctls at runtime via module?
2004-12-14 17:27 how to add 32/64 compatible ioctls at runtime via module? Mikael Pettersson
@ 2004-12-14 17:31 ` Jan Engelhardt
2004-12-14 17:40 ` Chris Friesen
1 sibling, 0 replies; 4+ messages in thread
From: Jan Engelhardt @ 2004-12-14 17:31 UTC (permalink / raw)
To: Mikael Pettersson; +Cc: cfriesen, linux-kernel
>register_ioctl32_conversion(ioctl, handler)
>
>tells your 64-bit kernel that the given ioctl, when issued by
>a 32-bit mode task, should be routed to the given handler.
Hah, so there is a way to determine whether a task is 32/64-bit? That could
solve the problem of one of the recent posters...
Jan Engelhardt
--
ENOSPC
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: how to add 32/64 compatible ioctls at runtime via module?
2004-12-14 17:27 how to add 32/64 compatible ioctls at runtime via module? Mikael Pettersson
2004-12-14 17:31 ` Jan Engelhardt
@ 2004-12-14 17:40 ` Chris Friesen
1 sibling, 0 replies; 4+ messages in thread
From: Chris Friesen @ 2004-12-14 17:40 UTC (permalink / raw)
To: Mikael Pettersson; +Cc: linux-kernel
Mikael Pettersson wrote:
> register_ioctl32_conversion(ioctl, handler)
>
> tells your 64-bit kernel that the given ioctl, when issued by
> a 32-bit mode task, should be routed to the given handler.
> The handler can be NULL, in which case the ioctl is routed to
> the normal handler via the filp.
Excellent. Thanks very much.
Chris
^ permalink raw reply [flat|nested] 4+ messages in thread
* how to add 32/64 compatible ioctls at runtime via module?
@ 2004-12-14 16:39 Chris Friesen
0 siblings, 0 replies; 4+ messages in thread
From: Chris Friesen @ 2004-12-14 16:39 UTC (permalink / raw)
To: Linux kernel
I'm working on a driver for 2.6.
I'd like to be able to load the driver as a module, and have it register for
various ioctl() calls on a device node (which can be dynamic, so no problem there).
I'm not sure how to go about registering at runtime for 32/64 bit compatibility
so that I can load a module into a ppc64 kernel, and have 32-bit userspace code
call those ioctls.
Can anyone give some pointers, or direct me to existing code?
Thanks,
Chris
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2004-12-14 17:42 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-12-14 17:27 how to add 32/64 compatible ioctls at runtime via module? Mikael Pettersson
2004-12-14 17:31 ` Jan Engelhardt
2004-12-14 17:40 ` Chris Friesen
-- strict thread matches above, loose matches on Subject: below --
2004-12-14 16:39 Chris Friesen
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.