This patch renames a few functions in util/biosdisk.c. Currently, by looking
at get_drive(), find_drive(), get_os_disk() function names it is very difficult
to figure out what's going on. They're even misleading in fact. I propose
the more descriptive names find_grub_drive(), find_system_device
There's no reason grub-probe should fail if it can't resolve drive, when we
just asked for -t fs, -t fs_uuid or -t partmap.
This patch solves the problem by spliting device/drive map[] entry registration
into a separate function, and using that from grub-probe.c to register a dummy
drive that wil
Hi,
I'm working on a multiplexer terminal device (which sends requests to
several terminals in the backend, eg. console and serial in parallel)
and ran into different behaviour in checkkey on console and serial.
console's checkkey consumes the keypress it returns (if there is one),
serial's
On Mon, 2008-06-02 at 15:50 +0200, Robert Millan wrote:
> There's no reason grub-probe should fail if it can't resolve drive, when we
> just asked for -t fs, -t fs_uuid or -t partmap.
>
> This patch solves the problem by spliting device/drive map[] entry
> registration
> into a separate function,
Uhm.. however, you still need device-specific knowledge to find the full device
containing your partition (needed for -t partmap).
I'm not sure if there's a point to continue in this direction. Should we
just exclude partmap from this?
On Mon, Jun 02, 2008 at 03:50:14PM +0200, Robert Millan wro
On Mon, Jun 2, 2008 at 10:07 PM, Patrick Georgi <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I'm working on a multiplexer terminal device (which sends requests to
> several terminals in the backend, eg. console and serial in parallel) and
> ran into different behaviour in checkkey on console and serial.
>
Hi,
This patch move the elf program header to the beginning, it should
solve the problem with coreboot.
--
Bean
diff --git a/util/elf/grub-mkimage.c b/util/elf/grub-mkimage.c
index ca138dd..51c4e54 100644
--- a/util/elf/grub-mkimage.c
+++ b/util/elf/grub-mkimage.c
@@ -166,8 +166,8 @@ add_segment
Hi,
The problem with initrd is that it can't allocate enough memory.
Please try the following patch, it will show some info that could be
be useful in debugging.
diff --git a/loader/i386/efi/linux.c b/loader/i386/efi/linux.c
index ee3fb99..327fcaf 100644
--- a/loader/i386/efi/linux.c
+++ b/loader