From: Bart Grantham <bart-grubdevel@bartgrantham.com>
To: grub-devel@gnu.org
Subject: Re: GRUB2 Sparc
Date: Sun, 25 Sep 2005 15:14:24 -0400 [thread overview]
Message-ID: <4336F710.8030000@bartgrantham.com> (raw)
In-Reply-To: <87vf0pa067.fsf@student.han.nl>
Marco Gerards wrote:
> Bart Grantham <bart@chumps.net> writes:
>
>>Didn't want to pollute the list with my dumb questions, so this is
>>addressed only to you. :)
>
>
> You can send anything related to GRUB2 to grub-devel, don't worry
> about that. The advantage of a mailinglist is that everyone can
> reply.
Ok. Replied to list.
>>Is this to say that an f-code bootsector is underway (or maybe even
>>complete)?
>
> At the moment only Vincent is working on the sparc specific part of
> GRUB 2. I think making GRUB 2 actually useful on the sparc is of
> higher priority to him (for example writing a linux loader). Would
> you like to help us writing a f-code bootsector?
Well, I did halfway learn Forth a couple years ago in an attempt to port
my hobby OS over to sparc, and I have both an Ultra 5 and a Blue&White
Mac G3, so I can do some cross-platform testing. Desite this, I find it
hard to believe I'm the most qualified of this crowd to do this. ;)
Let me think about it some. I'd be in WAY over my head, as I haven't
really thought through how the f-code<->grub2 interface would be
structured. Are there any docs or thoughts on this from the group? How
is the direct stage1 -> stage2 process being handled on x86 without the
stage1.5 middleman? Specifically, how are you handling different
filesystem structures in the boot sector?
Bart
next prev parent reply other threads:[~2005-09-25 19:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-11 4:35 GRUB2 Sparc Bart Grantham
2005-09-12 7:25 ` Vincent Pelletier
2005-09-23 7:29 ` Bart Grantham
2005-09-23 13:56 ` Marco Gerards
[not found] ` <4335D770.6050002@chumps.net>
[not found] ` <87vf0pa067.fsf@student.han.nl>
2005-09-25 19:14 ` Bart Grantham [this message]
2005-09-25 19:44 ` Marco Gerards
2005-09-27 3:14 ` Bart Grantham
2005-09-27 8:51 ` Marco Gerards
2005-09-26 8:39 ` Vincent Pelletier
2005-09-26 8:33 ` Vincent Pelletier
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=4336F710.8030000@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 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.