All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] fix endianess in IEEE-1275 integer properties
Date: Mon, 14 Jan 2008 15:27:31 +0100	[thread overview]
Message-ID: <20080114142731.GA28109@thorin> (raw)
In-Reply-To: <1200320439.13534.4.camel@dv>

On Mon, Jan 14, 2008 at 09:20:39AM -0500, Pavel Roskin wrote:
> On Sun, 2008-01-13 at 21:30 +0100, Robert Millan wrote:
> > Integer properties are always in big endian.  This (incomplete) patch is my
> > suggested approach to deal with this.  I'd like to receive input about it
> > before I complete it (checking all calls to grub_ieee1275_get_property
> > through GRUB and replacing with grub_ieee1275_get_integer_property when
> > appropiate).
> > 
> > Again, some testing on Apple/IBM/Genesi hardware would be nice.
> 
> It doesn't apply cleanly,

It depends on my previous patch, "restrict parsing of `available'".

> and I don't see how the result of
> grub_ieee1275_get_integer_property() is used.

If something went wrong, you'd most likely see those claim-related errors
you're familiar with ;-)

-- 
Robert Millan

<GPLv2> I know my rights; I want my phone call!
<DRM> What use is a phone call, if you are unable to speak?
(as seen on /.)



  reply	other threads:[~2008-01-14 14:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-13 20:30 [PATCH] fix endianess in IEEE-1275 integer properties Robert Millan
2008-01-14 14:20 ` Pavel Roskin
2008-01-14 14:27   ` Robert Millan [this message]
2008-01-15  4:49     ` Pavel Roskin
2008-01-15 12:12       ` Robert Millan
2008-01-15 12:22         ` Robert Millan
2008-01-15 14:41           ` Pavel Roskin
2008-01-15 16:13             ` Robert Millan
2008-01-15 12:30 ` Marco Gerards
2008-01-15 12:32   ` Robert Millan

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=20080114142731.GA28109@thorin \
    --to=rmh@aybabtu.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.