From: Vincent Pelletier <subdino2004@yahoo.fr>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: sparc64 port : diffs to powerpc branches
Date: Wed, 13 Jul 2005 22:40:49 +0200 [thread overview]
Message-ID: <42D57C51.9080302@yahoo.fr> (raw)
In-Reply-To: <87oe96ae86.fsf@student.han.nl>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 1566 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Marco Gerards wrote:
> In that case the usparc port needs a GRUB_IEEE1275_FLAG_... to
> indicate it is not possible to change colors or that it works
> differently.
Good idea.
> Perhaps... Can you put the bug report on the wiki so we will not
> forget about it?
Done. Btw, I hope my wiki clean up (pages full of links) is ok. I
wondered if it was worth the noise it made in the change log...
> You did not load ext2 as a module, but linked it into the binary.
> I assume you did not use grub-mkimage yet...
Oh, I thought you meant it was used to add them statically in grubof.
> Ok, cool. I am looking forwards to that patch.
I think patches should be applied in this order :
- - Apply file moving patch for ieee1275 common files.
- - Apply the general patchs I sent (so we have a clean status to add the
sparc64 port, like grub_get_rtc prototype change, the already-applied
mm.c patch to correct behaviour on 64 bits archs, ...)
- - Finally apply the sparc64 specific adds (should be only file additions
at this step, excepts for changes in configure[.ac] and ChangeLog :) ).
Vincent Pelletier
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFC1XxRFEQoKRQyjtURAgciAKCYAeqt7PGpx85WOj0iciC4P49FLwCffFMe
wwtEclilaG6A8+SUUO4KIGQ=
=NR2U
-----END PGP SIGNATURE-----
___________________________________________________________________________
Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger
Téléchargez cette version sur http://fr.messenger.yahoo.com
next prev parent reply other threads:[~2005-07-13 20:53 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-11 12:21 [PATCH] Huge changes in mm.c Vincent Pelletier
2005-07-11 12:56 ` Marco Gerards
2005-07-11 13:20 ` Vincent Pelletier
2005-07-11 13:09 ` Vincent Guffens
2005-07-12 11:14 ` Vincent Pelletier
2005-07-12 10:58 ` Yoshinori K. Okuji
2005-07-12 12:31 ` Vincent Pelletier
2005-07-12 12:55 ` Marco Gerards
2005-07-12 13:41 ` Vincent Pelletier
2005-07-12 15:12 ` Hollis Blanchard
2005-07-12 15:46 ` Marco Gerards
2005-07-12 18:46 ` sparc64 port : diffs to powerpc branches Vincent Pelletier
2005-07-12 19:40 ` Marco Gerards
2005-07-12 20:49 ` Vincent Pelletier
2005-07-13 15:59 ` Marco Gerards
2005-07-13 20:40 ` Vincent Pelletier [this message]
2005-07-13 21:27 ` Marco Gerards
2005-07-12 22:17 ` Hollis Blanchard
2005-07-13 1:01 ` common ieee1275 code Hollis Blanchard
2005-07-13 16:13 ` Marco Gerards
2005-07-14 3:38 ` Hollis Blanchard
2005-07-14 9:55 ` Marco Gerards
2005-07-14 14:23 ` Hollis Blanchard
2005-07-14 22:54 ` Vincent Pelletier
2005-07-16 18:45 ` Marco Gerards
2005-07-16 20:10 ` Hollis Blanchard
2005-07-16 22:07 ` Vincent Pelletier
2005-07-18 17:19 ` Marco Gerards
2005-07-18 18:59 ` Hollis Blanchard
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=42D57C51.9080302@yahoo.fr \
--to=subdino2004@yahoo.fr \
--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.