Re: sys32_ioctl issue

"Tom 'spot' Callaway" <[email protected]>
Newsgroups gmane.linux.aurora.devel
Organization Red Hat
Message-ID <1051627737.1914.165.camel@zorak>
On Tue, 2003-04-29 at 09:43, Kevin Curtis wrote:
> Hi,
> 	many thanks to the list for getting me of the ground with porting
> our Intel 32 bit drivers to sparc64.  I have now managed to compile and load
> the driver module successfully.  
> 
> The next step is to load our card with it's firmware.  We do this through an
> ioctl interface to the driver with a loader program.  I was getting on fine
> with this until I came to the first ioctl operation.  In the 32 bit Intel
> version the ioctl command is calculated (with the _IO macro) as 0x7800, and
> this comes out as 0x20007800 on sparc64 with the same calculation.  The
> sys32_ioctl function reports the following error:
> Apr 29 15:37:16 icarus kernel: sys32_ioctl(fsx25load:5058): Unknown cmd
> fd(3) cmd(20007800) arg(00000000)
> 
> How is sys32_ioctl making the conversion of the ioctl and what does my
> fsx25load program or driver need to do to solve the problem?

Sparc64 ioctls have to be listed in the list inside
arch/sparc64/kernel/ioctl32.c, and translated if needed.

~spot
---
Tom "spot" Callaway <tcallawa(a)redhat*com> SAIR LCA, RHCE
Red Hat Enterprise Architect :: http://www.redhat.com
Project Leader for Aurora Sparc Linux :: http://auroralinux.org
GPG: D786 8B22 D9DB 1F8B 4AB7  448E 3C5E 99AD 9305 4260

The words and opinions reflected in this message do not necessarily
reflect those of my employer, Red Hat, and belong solely to me.

"Immature poets borrow, mature poets steal." --- T. S. Eliot
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.