From: Loys Ollivier <lollivier@baylibre.com>
To: 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: Tue, 28 May 2019 17:10:42 +0200 [thread overview]
Message-ID: <86o93mpqbx.fsf@baylibre.com> (raw)
In-Reply-To: <alpine.DEB.2.21.9999.1905280105110.20842@viisi.sifive.com>
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. This new riscv-pk version
> should be easier to use than the previous version for those testing
> upstream-bound kernel DT data on SiFive hardware:
>
> https://github.com/sifive/riscv-pk/tree/dev/paulw/configurable-machine-data-methods-v1
>
> To build a BBL that doesn't touch the DT data, use the
> "--with-config-method=hifive_unleashed" switch for the "configure" script.
> As before, this version of riscv-pk can take a DTB that can be passed
> along to the kernel. But this time the path to the DTB can be specified
> on the "configure" script command line.
>
> Below is an example of how to configure it. (The directory structure
> should be familiar to those using the v1_0 tag of freedom-u-sdk, with the
> kernel source in ./linux, riscv-pk source in ./riscv-pk, and build trees
> in work/{linux,riscv-pk}.)
>
> cd work/riscv-pk
> CC=/opt/rv64gc-mmu-linux-8.2.0/bin/riscv64-unknown-linux-gnu-gcc ../../riscv-pk/configure \
> --host=riscv64-unknown-linux-gnu \
> --with-payload=../../work/linux/vmlinux-stripped \
> --with-config-method=hifive_unleashed \
> --enable-dtb \
> --with-dtb-path=../../work/linux/arch/riscv/boot/dts/sifive/hifive-unleashed-a00.dtb
>
>
> 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.
Thanks,
Loys
next prev parent reply other threads:[~2019-05-28 15:10 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 [this message]
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
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=86o93mpqbx.fsf@baylibre.com \
--to=lollivier@baylibre.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).