[Fwd: Re: GRUB device names wrt. ieee1275]

[Fwd: Re: GRUB device names wrt. ieee1275]

[phcoder]

[-- Attachment #1: Type: text/plain, Size: 44 bytes --]


-- 

Regards
Vladimir 'phcoder' Serbinenko

[-- Attachment #2: Re: GRUB device names wrt. ieee1275.eml --]
[-- Type: message/rfc822, Size: 1687 bytes --]

From: phcoder <phcoder@gmail.com>
To: David Miller <davem@davemloft.net>
Subject: Re: GRUB device names wrt. ieee1275
Date: Mon, 23 Mar 2009 11:11:58 +0100
Message-ID: <49C7606E.1070404@gmail.com>

David Miller wrote:
> From: phcoder <phcoder@gmail.com>
> Date: Sun, 22 Mar 2009 23:51:14 +0100
> 
>> 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
> 
> Sure we could do that.
> 
> But I'm trying to figure out why to bother with this if I
> already have all of the (tested) logic and infrastructure to
> fill in the device path already?

What about booting from removable device? In this case you can't assume 
that device path during install is still valid at booting
> 
> It just seems like another case in the matrix which needs to
> be tested, and can thus go wrong.


-- 

Regards
Vladimir 'phcoder' Serbinenko