From: Loys Ollivier <lollivier@baylibre.com>
To: Karsten Merker <merker@debian.org>
Cc: Paul Walmsley <paul.walmsley@sifive.com>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: Testing the recent RISC-V DT patchsets
Date: Wed, 29 May 2019 11:41:11 +0200 [thread overview]
Message-ID: <86zhn54myw.fsf@baylibre.com> (raw)
In-Reply-To: <20190528153542.jfkkwycyc3vu6hld@excalibur.cnev.de>
On Tue 28 May 2019 at 17:35, Karsten Merker <merker@debian.org> wrote:
> 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.
>
Hello Karsten,
That was it ! This fixes the issue I had on init execution.
Good catch, thanks a lot for the help !
Regards,
Loys
> 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.
next prev parent reply other threads:[~2019-05-29 9:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-23 0:17 Testing the recent RISC-V DT patchsets Paul Walmsley
2019-05-28 8:32 ` Paul Walmsley
2019-05-28 15:10 ` Loys Ollivier
2019-05-28 15:35 ` Karsten Merker
2019-05-29 7:50 ` Atish Patra
2019-05-29 10:04 ` Loys Ollivier
2019-05-29 17:09 ` Atish Patra
2019-05-29 17:25 ` Troy Benjegerdes
2019-06-03 9:49 ` Loys Ollivier
2019-06-03 15:40 ` Troy Benjegerdes
2019-06-03 20:17 ` Troy Benjegerdes
2019-06-04 6:12 ` Anup Patel
2019-05-29 9:41 ` Loys Ollivier [this message]
2019-05-28 19:38 ` Atish Patra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86zhn54myw.fsf@baylibre.com \
--to=lollivier@baylibre.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=merker@debian.org \
--cc=paul.walmsley@sifive.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox