freeipmi-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Freeipmi-users] sparc64 compilation errors


From: corentin.labbe
Subject: Re: [Freeipmi-users] sparc64 compilation errors
Date: Thu, 15 Mar 2007 22:47:14 +0100
User-agent: Thunderbird 1.5.0.10 (X11/20070304)

Al Chu a écrit :
On Thu, 2007-03-15 at 21:55 +0100, corentin.labbe wrote:
Hello

I searched a long time but i saw a major problem here: 
http://sources.redhat.com/ml/libc-alpha/2000-01/msg00158.html
No iopl on sparc.
However "GNU FreeIPMI implements their in-band IPMI driver in userspace using iopl() 
calls"
So the only solution is to use /dev/port (acording to 
http://linuxdriver.co.il/ldd3/linuxdrive3-CHP-9-SECT-2.html section 9.2.3)

I don't know too much about /dev/ports, I'd have to look into it more.
Some of the other FreeIPMI developers may know more already.  Maybe they
can chime in.

For the compilation problem i just put manual "typedef unsgned int u32;" and it 
works (yes i know it's bad).

Did just #include <asm-sparc64/types.h> work for you?

No, the typedef is included in a #ifdef __KERNEL__ ... #endif section.
I'm trying to set it but it doesn't work (and it's certainly not the correct 
solution)
I must search more but apparently on sparc64 the userland is 32bits (only 
kernel is 64).
But i get the same errors with gcc-sparc and gcc-sparc64.
And apparently it's <linux/types> the correct/good include.

I will search more about /dev/port . i grep the source and i found juste 2 
iopl. Perhaps easy to port.


For the time being, does your kernel come with the IPMI kernel driver?

Yes.

FreeIPMI 0.3.X also supports inband communication w/ the kernel driver.
So it would be another way to get the ipmi tools to work in-band for hte
time being.
Al

But the major problem is now the iopl.

Cordially

LABBE C.


_______________________________________________
Freeipmi-users mailing list
address@hidden
http://lists.gnu.org/mailman/listinfo/freeipmi-users

Do you have an irc channel?

cordially

LABBE C.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]