From: Antony Pavlov <antonynpavlov@gmail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH v3 00/10] Add initial RISC-V architecture support
Date: Fri, 4 Jan 2019 11:47:37 +0300 [thread overview]
Message-ID: <20190104114737.7070d48ba7a2b486d6ee46e0@gmail.com> (raw)
In-Reply-To: <20190103111809.ctogjrhe4d2eyxg7@pengutronix.de>
On Thu, 3 Jan 2019 12:18:09 +0100
Sascha Hauer <s.hauer@pengutronix.de> wrote:
> On Tue, Dec 18, 2018 at 10:19:33AM +0300, Antony Pavlov wrote:
> > This patchseries adds initial RISC-V architecture support for barebox.
>
> It's very nice to get RISC-V support for barebox.
>
> The code looks fine from a first glance. I would prefer using multi
> image support from the start of course, but I think I can live without
> it.
> I do not have the bandwidth to look at the code so closely to give any
> valuable input though. I am fine to apply it if you want to, or you
> could continue to develop it out of tree if that's more convenient for
> you. Your choice.
Hi Sascha!
Please apply RISC-V patchseries.
It's looks like people need a good bootloader for RISC-V ;)
E.g.:
https://www.mail-archive.com/coreboot@coreboot.org/msg52977.html
https://forums.sifive.com/t/coreboot-or-u-boot/1186
I'm planning to add linux-capable 64-bit SiFive Unleashed board support in the next RISC-V patchseries.
See https://www.sifive.com/boards/hifive-unleashed for details.
At least current qemu supports Unleashed-class boards.
--
Best regards,
Antony Pavlov
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2019-01-04 8:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-18 7:19 Antony Pavlov
2018-12-18 7:19 ` [PATCH v3 01/10] " Antony Pavlov
2018-12-18 7:19 ` [PATCH v3 02/10] RISC-V: add Erizo SoC support Antony Pavlov
2018-12-18 7:19 ` [PATCH v3 03/10] RISC-V: add low-level debug macros for ns16550 Antony Pavlov
2018-12-18 8:33 ` Oleksij Rempel
2018-12-18 7:19 ` [PATCH v3 04/10] RISC-V: add nmon nano-monitor Antony Pavlov
2018-12-18 7:19 ` [PATCH v3 05/10] RISC-V: erizo: add DEBUG_LL support Antony Pavlov
2018-12-18 7:19 ` [PATCH v3 06/10] RISC-V: erizo: enable nmon Antony Pavlov
2018-12-18 7:19 ` [PATCH v3 07/10] RISC-V: erizo: add nmon image creation Antony Pavlov
2018-12-18 7:19 ` [PATCH v3 08/10] RISC-V: add erizo_generic_defconfig Antony Pavlov
2018-12-18 7:19 ` [PATCH v3 09/10] scripts: add nmon-loader Antony Pavlov
2019-08-11 9:59 ` Antony Pavlov
2019-08-12 7:41 ` Sascha Hauer
2019-08-12 9:01 ` Antony Pavlov
2018-12-18 7:19 ` [PATCH v3 10/10] Documentation: add RISC-V docs Antony Pavlov
2019-01-03 11:18 ` [PATCH v3 00/10] Add initial RISC-V architecture support Sascha Hauer
2019-01-04 8:47 ` Antony Pavlov [this message]
2019-01-07 7:54 ` Sascha Hauer
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=20190104114737.7070d48ba7a2b486d6ee46e0@gmail.com \
--to=antonynpavlov@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
/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