Re: OpenBoot callback function

2005-01-17 Thread Ben Collins
On Mon, Jan 17, 2005 at 01:26:34PM +0100, Vincent Pelletier wrote:
> Ben Collins wrote :
> >I believe things are passed in an array. I think the reason it is in
> >mostly asm is because silo is a 32-bit program, and the openboot commands
> >are expected to be sent in a 64-bit array. So normal C calling conventions
> >don't mix.
> 
> Grub2 can be built as 64bits I think. And the less I use asm, the more 
> easily it could be ported to other OpenFirmware (maybe OpenBot) platforms.

I don't think you want it 64-bit for the boot loader. Might want to talk
to Dave Miller about why it's 32-bit, even for sparc64.

> >Just copy the p1275 command stuff from silo. It's a simple and clean
> >interface.
> 
> 
> Grub2 is a GNU project, so I can't copy-paste code - or, afaik, the 
> original author would have to sign some kind of copyright assignment. 
> That's why I would highly prefer a doc over source code.

Just talk to Dave Miller and Jakub Jelinik. I'm pretty sure both already
have FSF copyright assignment agreements, and both would be willing to
allow the SILO code to be added to grub.

-- 
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
WatchGuard - http://www.watchguard.com/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: OpenBoot callback function

2005-01-17 Thread Vincent Pelletier
Ben Collins wrote :
I believe things are passed in an array. I think the reason it is in
mostly asm is because silo is a 32-bit program, and the openboot commands
are expected to be sent in a 64-bit array. So normal C calling conventions
don't mix.
Grub2 can be built as 64bits I think. And the less I use asm, the more 
easily it could be ported to other OpenFirmware (maybe OpenBot) platforms.

Just copy the p1275 command stuff from silo. It's a simple and clean
interface.

Grub2 is a GNU project, so I can't copy-paste code - or, afaik, the 
original author would have to sign some kind of copyright assignment. 
That's why I would highly prefer a doc over source code.

Vincent Pelletier
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]


Re: OpenBoot callback function

2005-01-16 Thread Ben Collins
I believe things are passed in an array. I think the reason it is in
mostly asm is because silo is a 32-bit program, and the openboot commands
are expected to be sent in a 64-bit array. So normal C calling conventions
don't mix.

Just copy the p1275 command stuff from silo. It's a simple and clean
interface.

On Sat, Jan 15, 2005 at 09:29:55PM +0100, Vincent Pelletier wrote:
> Hi.
> I'm working on grub2 port on ultrasparc, and I'm searching for docs 
> describing how args are passed to the callback function, and how to read 
> the result.
> I saw silo and kernel uses lots of asm to do that, and I would like to 
> avoid it as much as possible.
> 
> Thanks,
> Vincent Pelletier
> 
> 
> -- 
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact 
> [EMAIL PROTECTED]
> 

-- 
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
WatchGuard - http://www.watchguard.com/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: OpenBoot callback function

2005-01-16 Thread Richard Mortimer
Hi,

I don't know of any exact references but the following may have helpful
information. Of course it may be that the best course of action is just
to copy the existing examples in silo and kernel.

http://playground.sun.com/1275/
http://docs.sun.com/app/docs/doc/806-1379-10
http://www.firmworks.com/

As I said none really describe how the client interface works but may
have useful pointers.

Richard

On Sat, 2005-01-15 at 21:29 +0100, Vincent Pelletier wrote:
> Hi.
> I'm working on grub2 port on ultrasparc, and I'm searching for docs 
> describing how args are passed to the callback function, and how to read 
> the result.
> I saw silo and kernel uses lots of asm to do that, and I would like to 
> avoid it as much as possible.
> 
> Thanks,
> Vincent Pelletier
> 
> 
-- 
Richard Mortimer <[EMAIL PROTECTED]>


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]