Bug#1028343: u-boot-qemu 2023.01~rc4+dfsg-2: riscv64: FDT creation failed

2023-01-16 Thread Vagrant Cascadian
Control: tags 1028343 pending On 2023-01-11, Karsten Merker wrote: > On Wed, Jan 11, 2023 at 09:21:42AM -0800 Vagrant Cascadian wrote: >> Definitely would be good to mention to upstream. Please Cc me if you do! > > I've sent the bugreport upstream: >

Bug#1028343: u-boot-qemu 2023.01~rc4+dfsg-2: riscv64: FDT creation failed

2023-01-11 Thread Karsten Merker
Control: tags -1 upstream X-Debbugs-CC: debian-ri...@lists.debian.org On Wed, Jan 11, 2023 at 09:21:42AM -0800 Vagrant Cascadian wrote: > Definitely would be good to mention to upstream. Please Cc me if you do! I've sent the bugreport upstream:

Bug#1028343: u-boot-qemu 2023.01~rc4+dfsg-2: riscv64: FDT creation failed

2023-01-11 Thread Vagrant Cascadian
On 2023-01-11, Karsten Merker wrote: > On Tue, Jan 10, 2023 at 09:22:02PM +0100 Karsten Merker wrote: > >> I've also taken a look at the u-boot changelogs and there have >> been quite a few changes concerning u-boot's handling of >> device-trees between the working and the non-working versions.

Bug#1028343: u-boot-qemu 2023.01~rc4+dfsg-2: riscv64: FDT creation failed

2023-01-11 Thread Karsten Merker
X-Debbugs-CC: debian-ri...@lists.debian.org On Tue, Jan 10, 2023 at 09:22:02PM +0100 Karsten Merker wrote: > I've also taken a look at the u-boot changelogs and there have > been quite a few changes concerning u-boot's handling of > device-trees between the working and the non-working versions.

Bug#1028343: u-boot-qemu 2023.01~rc4+dfsg-2: riscv64: FDT creation failed

2023-01-10 Thread Karsten Merker
Control: found -1 2023.01+dfsg-1 X-Debbugs-CC: debian-ri...@lists.debian.org On Tue, Jan 10, 2023 at 09:23:04AM -0800 Vagrant Cascadian wrote: > On 2023-01-10, Cheng Li wrote: [...] > > Moving Image from 0x8400 to 0x8020, end=815d8000 > > ## Flattened Device Tree blob at ff733ef0 > >   

Bug#1028343: u-boot-qemu 2023.01~rc4+dfsg-2: riscv64: FDT creation failed

2023-01-10 Thread Vagrant Cascadian
On 2023-01-10, Cheng Li wrote: > qemu-system-riscv64 \ > -nographic \ > -machine virt \ > -smp 8 -m 8G  \ > -bios /usr/lib/riscv64-linux-gnu/opensbi/generic/fw_jump.elf  \ > -kernel /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf  \ > -object rng-random,filename=/dev/urandom,id=rng0 \ > -device

Bug#1028343: u-boot-qemu 2023.01~rc4+dfsg-2: riscv64: FDT creation failed

2023-01-10 Thread Cheng Li
Hello, I have the same issue with Karsten: Here is my command line: qemu-system-riscv64 \ -nographic \ -machine virt \ -smp 8 -m 8G  \ -bios /usr/lib/riscv64-linux-gnu/opensbi/generic/fw_jump.elf  \ -kernel /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf  \ -object

Bug#1028343: u-boot-qemu 2023.01~rc4+dfsg-2: riscv64: FDT creation failed

2023-01-09 Thread Karsten Merker
Source: u-boot Version: 2023.01~rc4+dfsg-2 Severity: important User: debian-ri...@lists.debian.org Usertags: riscv64 X-Debbugs-CC: debian-ri...@lists.debian.org Hello, when booting a riscv64 VM in qemu 1:7.0+dfsg-1 with OpenSBI 1.1-2 and u-boot-qemu 2023.01~rc4+dfsg-2 with the following