All of lore.kernel.org
 help / color / mirror / Atom feed
From: phcoder <phcoder@gmail.com>
To: David Miller <davem@davemloft.net>,
	 The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: GRUB device names wrt. ieee1275
Date: Sun, 22 Mar 2009 23:51:14 +0100	[thread overview]
Message-ID: <49C6C0E2.7020308@gmail.com> (raw)
In-Reply-To: <20090322.153022.233646325.davem@davemloft.net>

You could do it the way similar to how it's done on i386-pc:
jmp use_hardcoded
<code to retrieve boot block path>
use_hardcoded:
And then the grub-setup tool nops out the first jump if stage2 resides 
on a disk different than where bootblock is
David Miller wrote:
> From: phcoder <phcoder@gmail.com>
> Date: Sun, 22 Mar 2009 12:17:17 +0100
> 
>> As for the boot block I would prefer to acquire bootpath from OFW
>> instead of hardcoding in the boot sector. It has an obvious
>> advantage of e.g. USB booting even if no "usb" alias is defined. Is
>> it possible? (It seems it is but I'm not familiar with OFW yet,
>> looking at nvram is a bad idea because user may manually boot
>> another device from OFW console)
> 
> You can obtain the disk where the boot block was loaded from but with
> GRUB that can be miles away from where the second stage boot block and
> rest of the GRUB kernel reside.
> 
> I've been through this thought process already, that's why I've
> designed it this way with the full path encoded into the first stage
> boot block.


-- 

Regards
Vladimir 'phcoder' Serbinenko



  parent reply	other threads:[~2009-03-22 22:51 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-14 22:14 GRUB device names wrt. ieee1275 David Miller
2009-03-14 23:44 ` phcoder
2009-03-15  5:24   ` David Miller
2009-03-15  9:22 ` Vesa Jääskeläinen
2009-03-15 22:52   ` David Miller
2009-03-15 15:45 ` Robert Millan
2009-03-15 22:41   ` David Miller
2009-03-18 10:18     ` Robert Millan
2009-03-18 20:55       ` David Miller
2009-03-18 21:01         ` David Miller
2009-03-22  0:41           ` phcoder
2009-03-22  0:48             ` phcoder
2009-03-22  1:57               ` David Miller
2009-03-22  1:56             ` David Miller
     [not found]               ` <49C61E3D.3040901@gmail.com>
     [not found]                 ` <20090322.153022.233646325.davem@davemloft.net>
2009-03-22 22:51                   ` phcoder [this message]
2009-03-23  1:13                     ` David Miller
2009-03-22 12:22             ` Robert Millan
2009-03-23  4:23               ` David Miller

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=49C6C0E2.7020308@gmail.com \
    --to=phcoder@gmail.com \
    --cc=davem@davemloft.net \
    --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.