On 03/01/2019 17:27, Peter Maydell wrote:
On Thu, 3 Jan 2019 at 16:50, Nick Hudson wrote:
On 03/01/2019 16:20, Peter Maydell wrote:
On Tue, 11 Dec 2018 at 12:27, Nick Hudson wrote:
--- a/hw/arm/boot.c
+++ b/hw/arm/boot.c
@@ -30,8 +30,9 @@
* Documentation/arm/Booting and
On Thu, 3 Jan 2019 at 16:50, Nick Hudson wrote:
> On 03/01/2019 16:20, Peter Maydell wrote:
> > On Tue, 11 Dec 2018 at 12:27, Nick Hudson
> > wrote:
> >> --- a/hw/arm/boot.c
> >> +++ b/hw/arm/boot.c
> >> @@ -30,8 +30,9 @@
> >> * Documentation/arm/Booting and Documentation/arm64/booting.txt
On 03/01/2019 16:20, Peter Maydell wrote:
> On Tue, 11 Dec 2018 at 12:27, Nick Hudson wrote:
>>
>>
>> noload kernels are loaded with the u-boot image header and as a result
>> the header size needs adding to the entry point. Fake up a hdr so the
>> kernel image is loaded at the right address
On Tue, 11 Dec 2018 at 12:27, Nick Hudson wrote:
>
>
> noload kernels are loaded with the u-boot image header and as a result
> the header size needs adding to the entry point. Fake up a hdr so the
> kernel image is loaded at the right address and the entry point is
> adjusted appropriately.
>
>
On Fri, 21 Dec 2018 at 16:13, Nick Hudson wrote:
>
> ping
Thanks for the ping. This is on my to-review list but I'm
not going to be doing any code review until after I get
back to work in January now...
thanks
-- PMM
ping
On 11/12/2018 12:27, Nick Hudson wrote:
noload kernels are loaded with the u-boot image header and as a result
the header size needs adding to the entry point. Fake up a hdr so the
kernel image is loaded at the right address and the entry point is
adjusted appropriately.
The bootloader
noload kernels are loaded with the u-boot image header and as a result
the header size needs adding to the entry point. Fake up a hdr so the
kernel image is loaded at the right address and the entry point is
adjusted appropriately.
The bootloader fits in the space that the uboot header would
