From: Marco Gerards <metgerards@student.han.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: release planning
Date: Mon, 18 Jul 2005 18:32:35 +0200 [thread overview]
Message-ID: <87d5pgoz18.fsf@student.han.nl> (raw)
In-Reply-To: <42DBCAF8.4070209@iinet.net.au> (James Buchanan's message of "Tue, 19 Jul 2005 01:30:00 +1000")
James Buchanan <jamesb.au@iinet.net.au> writes:
Hi James,
> Would be nice to have GRUB2 for the IA-64 as well. Intel documents
> the Extensible Firmware Interface and makes a lot of docs and tools
> available, plus driver writer guides and oodles of examples.
Right, I completely agree. It is wise to make the EFI code as generic
as possible so it can be used for other (non-IA64) EFI systems. The
sme is currently done for the IEEE 1275 code (Open Firmware).
> I might be lucky enough to have an IA-64 system (HP workstation,
> Itanium2 900MHz, 2GB RAM, 2x 36GB SCSI-3 disks, picked up second hand
> on eBay...) later this week. It's interesting enough for me to have
> spent the last 5 hours transfixed by the docs. :)
Nice box! please tell us if you need any help or visit our IRC
channel.
> I'll be sure to hack up the GRUB2 sources for IA-64 and give it a go.
Good luck :)
--
Marco
next prev parent reply other threads:[~2005-07-18 16:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-17 15:39 release planning Yoshinori K. Okuji
2005-07-17 20:23 ` Marco Gerards
2005-07-17 20:30 ` Gregg C Levine
2005-07-17 21:13 ` Marco Gerards
2005-07-17 21:39 ` Gregg C Levine
2005-07-18 9:07 ` Yoshinori K. Okuji
2005-07-18 20:01 ` Gregg C Levine
2005-07-18 15:03 ` GRUB history Hollis Blanchard
2005-07-19 10:32 ` Marco Gerards
2005-07-18 7:28 ` release planning Tobias Wollgam
2005-07-18 15:01 ` Hollis Blanchard
2005-07-18 15:30 ` James Buchanan
2005-07-18 16:32 ` Marco Gerards [this message]
2005-07-18 20:33 ` Yoshinori K. Okuji
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=87d5pgoz18.fsf@student.han.nl \
--to=metgerards@student.han.nl \
--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.