From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Darren Hart <dvhart@linux.intel.com>
Cc: Yocto Project <yocto@yoctoproject.org>,
"Wold, Saul" <saul.wold@intel.com>
Subject: Re: GRUB fix for 1.1: Preferred approach for default grub version
Date: Mon, 03 Oct 2011 20:01:50 +0100 [thread overview]
Message-ID: <1317668520.12684.8.camel@ted> (raw)
In-Reply-To: <4E8A0380.1030502@linux.intel.com>
On Mon, 2011-10-03 at 11:48 -0700, Darren Hart wrote:
> When grub2 was merged int oe-core, it became the default (rather than
> being explicitly requested by the 64b meta-intel BSPs). This breaks the
> live install on 32b systems, like the n450 - installing grub v1.99 with
> a grub v1 config.
>
> We have a couple options on how to fix this.
>
> 1) Set PREFERRED_PROVIDER_grub="0.97" in all 32b x86 machine configs
> 2) Set DEFAULT_PREFERENCE="-1" in the grub_1.99.bb recipe which would
> affect all of oe-core.
> 3) Some alternate approach which would be the equivalent of
> DEFAULT_PREFERENCE, but only for meta-yocto BSPs or the poky
> "distro".
>
> Given the time frame, I'd prefer to agree on the approach before writing
> and testing patches. Preferences?
I thought I'd been assured grub2 worked fine for our 32 and 64 bit
platforms? :/.
The correct question here is why doesn't grub2 work on 32 bit platforms?
The answer might be "we need for time than is available in the 1.1
release to fix it" but I'd at least like to see the answer to the
question before we start with workarounds.
Cheers,
Richard
next prev parent reply other threads:[~2011-10-03 19:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-03 18:48 GRUB fix for 1.1: Preferred approach for default grub version Darren Hart
2011-10-03 19:01 ` Richard Purdie [this message]
2011-10-03 19:07 ` Tom Zanussi
2011-10-03 20:40 ` Darren Hart
2011-10-03 23:18 ` Tom Zanussi
2011-10-03 23:25 ` Tom Zanussi
2011-10-03 19:05 ` Tom Zanussi
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=1317668520.12684.8.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=dvhart@linux.intel.com \
--cc=saul.wold@intel.com \
--cc=yocto@yoctoproject.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.