Grub Development Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bart Grantham <bart-grubdevel@bartgrantham.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Sparc bootblock [Was: SFS breaks PPC build ]
Date: Mon, 17 Oct 2005 03:30:13 -0400	[thread overview]
Message-ID: <43535305.3050002@bartgrantham.com> (raw)
In-Reply-To: <87mzl99klb.fsf@student.han.nl>

Marco Gerards wrote:

 > As GRUB 2 is ported to the ultra sparc64 it might be wise for us (GRUB
 > and solaris developers) to talk about multiboot.  Of course other
 > parties might be interested as well (the Hurd uses multiboot, for
 > example).
 >
 > Anyway, what is important for you is that we are thinking about a
 > portable multiboot and that there is also a sparc port in the making.

Speaking of which, after refreshing my forth skills, I've started work 
on the sparc bootloader.  I have it reading data from disk into mem, but 
I'm not sure if I want to share it quite yet.  Before sharing it I'd 
like to:

- have it verify that the file at the configured sector(s) is an ELF file
- follow through and make sure it properly boots an ELF image (right now 
it only gets it into memory)
- clean up the code a bunch

I'll hand it over once I get those done.  After that, the features I'd 
like to work on are:

- support of a sector-sized lookup table indicating the layout of the 
grub image on disk, allowing for more flexible configuration
- support of a sector-sized lookup table indicating additional forth 
bytecode, providing for extensibility just in case.
- verify that the code works on PPC, and if not, try to make it work so 
that there's a unified bootblock [not sure if this is reasonable as I'm 
not as familiar with how PPC OF boots... how similiar is it to Sparc?]
- same for sparc32

BG



  reply	other threads:[~2005-10-17  7:36 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-15 18:15 GRUB 1.91 is released Yoshinori K. Okuji
2005-10-15 22:57 ` [SFS breaks PPC build] " Cyril Plisko
2005-10-16  0:47   ` Dennis Clarke
2005-10-16 11:49   ` Marco Gerards
2005-10-16 19:17     ` Dennis Clarke
2005-10-16 19:28       ` Cyril Plisko
2005-10-16 19:51         ` Dennis Clarke
2005-10-16 21:12         ` Marco Gerards
2005-10-16 21:28           ` Cyril Plisko
2005-10-16 21:39             ` Marco Gerards
2005-10-16 21:48               ` Cyril Plisko
2005-10-16 22:13                 ` Marco Gerards
2005-10-17  7:30                   ` Bart Grantham [this message]
2005-10-17  8:20                     ` Sparc bootblock Marco Gerards
2005-10-17 10:37                       ` Cyril Plisko
2005-10-17 13:38                       ` Andrei Warkentin
2005-10-17 13:28                     ` Sparc bootblock [Was: SFS breaks PPC build ] Andrei Warkentin
2005-10-17 16:59                     ` Vincent Pelletier
2005-10-17 18:01                       ` Bart Grantham
2005-10-17 18:13                         ` Sparc bootblock Marco Gerards
2005-10-16 19:41 ` GRUB 1.91 is released Joe Ciccone
2005-10-16 21:06   ` Marco Gerards
2005-10-18 21:14     ` Joe Ciccone
2005-10-20 18:20       ` Marco Gerards

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=43535305.3050002@bartgrantham.com \
    --to=bart-grubdevel@bartgrantham.com \
    --cc=grub-devel@gnu.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