From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Julien Olivain <ju.o@free.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] board/spike/riscv64/readme.txt: remove obsolete comment
Date: Fri, 12 Jul 2024 22:43:40 +0200 [thread overview]
Message-ID: <20240712224340.383674fa@windsurf> (raw)
In-Reply-To: <20240712183318.243890-1-ju.o@free.fr>
On Fri, 12 Jul 2024 20:33:18 +0200
Julien Olivain <ju.o@free.fr> wrote:
> At the time the spike_riscv64_defconfig was introduced in commit [1], it
> was not possible to have a console input using Spike and OpenSBI for
> RISC-V 32 bits. This limitation no longer applies, as upstream
> components now implements support for this.
>
> Buildroot commit [2] updated riscv-isa-sim (Spike), which now includes a
> NS16550 uart emulation. This can be used by RV32 Linux Kernel. Finally,
> a spike_riscv32_defconfig was added in [3].
>
> This commit removes the comment about this limitation, since it no
> longer applies.
>
> [1] https://gitlab.com/buildroot.org/buildroot/-/commit/24d07fdc1404901fb1872ac55f875fe1d555cbb3
> [2] https://gitlab.com/buildroot.org/buildroot/-/commit/853b7661bf5ddca5d4b81964ef1a19a133beac85
> [3] https://gitlab.com/buildroot.org/buildroot/-/commit/a83ab3f4c8621dec58dc78a8dcb48e519377ac3d
>
> Signed-off-by: Julien Olivain <ju.o@free.fr>
> ---
> board/spike/riscv64/readme.txt | 8 --------
> 1 file changed, 8 deletions(-)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-07-12 20:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-12 18:33 [Buildroot] [PATCH 1/1] board/spike/riscv64/readme.txt: remove obsolete comment Julien Olivain
2024-07-12 20:43 ` Thomas Petazzoni via buildroot [this message]
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=20240712224340.383674fa@windsurf \
--to=buildroot@buildroot.org \
--cc=ju.o@free.fr \
--cc=thomas.petazzoni@bootlin.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