From: Robert Millan
Date: Sat, 28 Mar 2009 14:42:34 +0100
> On Sat, Mar 28, 2009 at 02:36:00PM +0800, Bean wrote:
> > Hi,
> >
> > Currently, the grub-emu is in every rmk files, but I don't see the
> > difference between grub-emu in i386-pc, i386-coreboot or i386-efi. In
> > fact, grub-emu runs i
Btw, Vladimir's thread "Move normal.mod to conf/common.rmk" seems related
to this, since normal.mod and grub-emu have almost the same problem.
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening
On Sat, Mar 28, 2009 at 02:36:00PM +0800, Bean wrote:
> Hi,
>
> Currently, the grub-emu is in every rmk files, but I don't see the
> difference between grub-emu in i386-pc, i386-coreboot or i386-efi. In
> fact, grub-emu runs inside the host os, it can't access firmware
> facility anyway. One quick
Bean wrote:
> Hi,
>
> Currently, the grub-emu is in every rmk files, but I don't see the
> difference between grub-emu in i386-pc, i386-coreboot or i386-efi. In
> fact, grub-emu runs inside the host os, it can't access firmware
> facility anyway. One quick fix to move grub-emu to i386.rmk, but we
Hi,
Currently, the grub-emu is in every rmk files, but I don't see the
difference between grub-emu in i386-pc, i386-coreboot or i386-efi. In
fact, grub-emu runs inside the host os, it can't access firmware
facility anyway. One quick fix to move grub-emu to i386.rmk, but we
could also put it in a n
