Re: booti usage offset requirements for compressed kernel and initrd with dtb

On Sat, Jan 06, 2024 at 02:45:47PM -0800, E Shattow wrote: > Hi Simon, > > "If this [fdt_high environment variable] is set to the special value > 0x (32-bit machines) or 0x (64-bit machines) then > the fdt will not be copied at all on boot. For this to work it must reside >

Re: booti usage offset requirements for compressed kernel and initrd with dtb

Hi Simon, "If this [fdt_high environment variable] is set to the special value 0x (32-bit machines) or 0x (64-bit machines) then the fdt will not be copied at all on boot. For this to work it must reside in writable memory, have sufficient padding on the end of it for U-Boo

Re: booti usage offset requirements for compressed kernel and initrd with dtb

Hi, On Thu, Jan 4, 2024 at 5:19 AM E Shattow wrote: > > Hello, > > There is data corruption when using booti on a JH7110 (riscv64) board to > load (over tftp or ymodem) a compressed kernel, compressed initrd, and > device tree blob, when the data are too close together (even though not > overlapp

booti usage offset requirements for compressed kernel and initrd with dtb

Hello, There is data corruption when using booti on a JH7110 (riscv64) board to load (over tftp or ymodem) a compressed kernel, compressed initrd, and device tree blob, when the data are too close together (even though not overlapping). In the adjustments I have tried it seems to be consistent but