All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Gerards <metgerards@student.han.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [patch] set prefix on PPC - briQ results
Date: Thu, 21 Apr 2005 09:18:18 +0200	[thread overview]
Message-ID: <87br88oax1.fsf@student.han.nl> (raw)
In-Reply-To: <927b71c54c4ae6806ebfe44cd1671580@penguinppc.org> (Hollis Blanchard's message of "Wed, 20 Apr 2005 21:16:50 -0500")

Hollis Blanchard <hollis@penguinppc.org> writes:

>>> Does the Pegasos have a SmartFirmware-version property?
>>
>> It does.  It has both a CodeGen and bplan copyright property.  The
>> SmartFirmware-version is 1.2 here.  The model is "Pegasos2,1.2".  It
>> seems to me that this SmartFirmware-version is not interesting because
>> it looks like this version is not changed for every build.
>>
>> The most interesting property is "built-on", which we can use to
>> detect if a specific version has the bug or not.
>
> Right now I'm inclined to set a "0_BASED_PARTITION" flag if the
> SmartFirmware-version property exists. Later on if bplan fixes it then
> they will need to provide some other property we can examine.

Agreed.

> After I check in my patch I will work on these workarounds.

Fine for me.

Thanks,
Marco




      reply	other threads:[~2005-04-21  7:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-17 18:33 [patch] set prefix on PPC Hollis Blanchard
2005-04-17 19:38 ` Marco Gerards
2005-04-17 20:32   ` Hollis Blanchard
2005-04-19  3:59     ` [patch] set prefix on PPC - briQ results Hollis Blanchard
2005-04-19 17:36       ` Marco Gerards
2005-04-21  2:16         ` Hollis Blanchard
2005-04-21  7:18           ` Marco Gerards [this message]

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=87br88oax1.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.