Apologies for long silence, I've been off prototyping runtime services
for UEFI on ARMv7 (in order to make EFI grub-install actually _do_
anything), and am really bad at multi-tasking.
I am now focusing 100% on this for the rest of the week.
On Mon, Apr 08, 2013 at 09:58:12PM +0200, Vladimir '??-c
> Then I need to add a configure test for this, causing a failure if the
> option is missing. A toolchain that does not support this option cannot
> be used to build a reliable bare-metal image for ARM.
>
> FSF GCC 4.7 onwards (and some distribution-patched 4.6) support this flag.
>
Why? Accord
On Mon, Apr 08, 2013 at 02:59:59PM +0200, Vladimir '??-coder/phcoder'
Serbinenko wrote:
> > Is this because you're feeding it a uImage?
> > It is entirely possible to runtime detect the U-Boot signature, and simply
> > skip the header.
>
> The kernel shipped with raspbian aren't uImages. they are
On 08.04.2013 13:44, Leif Lindholm wrote:
> On Sun, Apr 07, 2013 at 07:20:35PM +0200, Vladimir '??-coder/phcoder'
> Serbinenko wrote:
>> Based on Leif Lindholm's patches I could go to GRUB console on raspberry pi.
>> The biggest problem is that cache flushing is simply skipped. Another
>> problem
On Sun, Apr 07, 2013 at 07:20:35PM +0200, Vladimir '??-coder/phcoder'
Serbinenko wrote:
> Based on Leif Lindholm's patches I could go to GRUB console on raspberry pi.
> The biggest problem is that cache flushing is simply skipped. Another
> problem is that due to different linux image format linux
Based on Leif Lindholm's patches I could go to GRUB console on raspberry pi.
The biggest problem is that cache flushing is simply skipped. Another problem
is that due to different linux image format linux loader doesn't work. I didn't
test grub-install but fed GRUB to uboot using kermit.
Is there a
