Messages in this thread | | | Date | Tue, 28 May 2019 17:35:42 +0200 | From | Karsten Merker <> | Subject | Re: Testing the recent RISC-V DT patchsets |
| |
On Tue, May 28, 2019 at 05:10:42PM +0200, Loys Ollivier wrote: > On Tue 28 May 2019 at 01:32, Paul Walmsley <paul.walmsley@sifive.com> wrote: > > > An update for those testing RISC-V patches: here's a new branch of > > riscv-pk/bbl that doesn't try to read or modify the DT data at all, which > > should be useful until U-Boot settles down. [...] > > Here is an Linux kernel branch with updated DT data that can be booted > > with the above bootloader: > > > > https://github.com/sifive/riscv-linux/tree/dev/paulw/dts-v5.2-rc1-experimental > > > > A sample boot log follows, using a 'defconfig' build from that branch. > > Thanks Paul, I can confirm that it works. > > Something is still unclear to myself. > Using FSBL + riscv-pk/bbl the linux kernel + device tree boots. > Neither FSBL nor riscv-pk/bbl are modifying the DT. > > Using FSBL + OpenSBI + U-Boot the same kernel + device tree hangs on > running /init. > > Would you have any pointer on what riscv-pk does that OpenSBI/U-boot doesn't ? > Or maybe it is the other way around - OpenSBI/U-boot does something that > extra that should not happen.
Hello,
I don't know which version of OpenSBI you are using, but there is a problem with the combination of kernel 5.2-rc1 and OpenSBI versions before commit
https://github.com/riscv/opensbi/commit/4e2cd478208531c47343290f15b577d40c82649c
that can result in a hang on executing init, so in case you should be using an older OpenSBI build that might be the source of the problem that you are experiencing.
Regards, Karsten -- Ich widerspreche hiermit ausdrücklich der Nutzung sowie der Weitergabe meiner personenbezogenen Daten für Zwecke der Werbung sowie der Markt- oder Meinungsforschung.
| |