Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
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
In-Reply-To: <20190528153542.jfkkwycyc3vu6hld@excalibur.cnev.de>
References: <alpine.DEB.2.21.9999.1904221705170.18377@viisi.sifive.com> <alpine.DEB.2.21.9999.1905280105110.20842@viisi.sifive.com> <86o93mpqbx.fsf@baylibre.com> <20190528153542.jfkkwycyc3vu6hld@excalibur.cnev.de>
Date:   Wed, 29 May 2019 11:41:11 +0200
Message-ID: <86zhn54myw.fsf@baylibre.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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> wr=
ote:
>>=20
>> > An update for those testing RISC-V patches: here's a new branch of=20
>> > riscv-pk/bbl that doesn't try to read or modify the DT data at all, wh=
ich=20
>> > should be useful until U-Boot settles down.
> [...]
>> > Here is an Linux kernel branch with updated DT data that can be booted=
=20
>> > with the above bootloader:
>> >
>> >    https://github.com/sifive/riscv-linux/tree/dev/paulw/dts-v5.2-rc1-e=
xperimental
>> >
>> > A sample boot log follows, using a 'defconfig' build from that branch.=
=20=20
>>=20
>> Thanks Paul, I can confirm that it works.
>>=20
>> 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.
>>=20
>> Using FSBL + OpenSBI + U-Boot the same kernel + device tree hangs on
>> running /init.
>>=20
>> Would you have any pointer on what riscv-pk does that OpenSBI/U-boot doe=
sn'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/4e2cd478208531c47343290f15b577d=
40c82649c
>
> 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
> --=20
> Ich widerspreche hiermit ausdr=C3=BCcklich der Nutzung sowie der
> Weitergabe meiner personenbezogenen Daten f=C3=BCr Zwecke der Werbung
> sowie der Markt- oder Meinungsforschung.