From: Sam Ravnborg <sam@ravnborg.org>
To: Antony Pavlov <antonynpavlov@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: [RFC 0/4] riscv: add initial LiteX SoC support
Date: Sun, 2 Jun 2019 11:08:17 +0200 [thread overview]
Message-ID: <20190602090817.GA14301@ravnborg.org> (raw)
In-Reply-To: <20190602073101.21352-1-antonynpavlov@gmail.com>
Hi Antony
Nice patch series, thanks for sharing.
On Sun, Jun 02, 2019 at 10:30:57AM +0300, Antony Pavlov wrote:
> This RFC patchseries adds initial LiteX RISC-V SoC support for barebox.
>
> You can obtain this patchseries from github:
>
> $ git clone -b 20190602.litex https://github.com/frantony/barebox
>
> LiteX is a Migen-based System on Chip [1], supporting softcore VexRiscv CPU,
> a 32-bits Linux Capable RISC-V CPU [2].
>
> All the components used to create the LiteX SoC are open-source and
> the flexibility of Spinal HDL/Migen allow targeting easily very various
> FPGA devices/boards: Lattice, Altera, Xilinx, Microsemi FPGAs
> with SDRAM/DDR/DDR2/DDR3/DDR4 RAMs, RMII/MII/RGMII/1000BASE-X Ethernet PHYs.
>
> The LiteX SoC with VexRiscv CPU can be deployed on e.g. Digilent ARTY board [3]
> or Terasic DE0-Nano board [4].
>
> You can boot barebox from serial port using flterm [5]:, e.g.:
>
> flterm --port /dev/ttyUSB0 --kernel <path_to_barebox.bin> --kernel-adr 0x40000000
Can you be persuaded to include the above in a .rst file in
Documentation, so others can find this info later?
Sam
>
>
> TODO
> ====
>
> * add pbl support for riscv barebox;
> * add liteeth Ethernet core support [6] (tip: use ARTY board);
> * fix issues (see the WIP commit);
> * use barebox to start linux [2] and zephyr [7].
>
>
> REFERENCES
> ==========
>
> [1] https://github.com/enjoy-digital/litex
> [2] https://github.com/enjoy-digital/linux-on-litex-vexriscv
> [3] https://store.digilentinc.com/arty-a7-artix-7-fpga-development-board-for-makers-and-hobbyists/
> [4] http://www.terasic.com.tw/cgi-bin/page/archive.pl?Language=English&No=593
> [5] https://github.com/timvideos/flterm
> [6] https://github.com/enjoy-digital/liteeth
> [7] https://github.com/zephyrproject-rtos/zephyr/tree/master/boards/riscv32/litex_vexriscv
>
>
> Antony Pavlov (4):
> riscv: add initial LiteX SoC support
> serial: add litex UART driver
> WIP: make it work on litex
> riscv: add litex_defconfig
>
> arch/riscv/Kconfig | 6 +
> arch/riscv/Makefile | 1 +
> arch/riscv/boot/start.S | 2 -
> arch/riscv/configs/litex_defconfig | 45 +++++++
> arch/riscv/dts/litex-generic.dts | 17 +++
> arch/riscv/dts/litex.dtsi | 36 +++++
> arch/riscv/mach-litex/Kconfig | 11 ++
> arch/riscv/mach-litex/Makefile | 3 +
> arch/riscv/mach-litex/include/mach/debug_ll.h | 124 ++++++++++++++++++
> common/bootm.c | 2 +
> drivers/serial/Makefile | 1 +
> drivers/serial/serial_litex.c | 99 ++++++++++++++
> 12 files changed, 345 insertions(+), 2 deletions(-)
> create mode 100644 arch/riscv/configs/litex_defconfig
> create mode 100644 arch/riscv/dts/litex-generic.dts
> create mode 100644 arch/riscv/dts/litex.dtsi
> create mode 100644 arch/riscv/mach-litex/Kconfig
> create mode 100644 arch/riscv/mach-litex/Makefile
> create mode 100644 arch/riscv/mach-litex/include/mach/debug_ll.h
> create mode 100644 drivers/serial/serial_litex.c
>
> --
> 2.20.1
>
>
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2019-06-02 9:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-02 7:30 Antony Pavlov
2019-06-02 7:30 ` [RFC 1/4] " Antony Pavlov
2019-06-02 7:30 ` [RFC 2/4] serial: add litex UART driver Antony Pavlov
2019-06-03 5:10 ` Ahmad Fatoum
2019-06-03 5:13 ` Ahmad Fatoum
2019-06-02 7:31 ` [RFC 3/4] WIP: make it work on litex Antony Pavlov
2019-06-07 7:11 ` Sascha Hauer
2019-06-02 7:31 ` [RFC 4/4] riscv: add litex_defconfig Antony Pavlov
2019-06-02 9:08 ` Sam Ravnborg [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=20190602090817.GA14301@ravnborg.org \
--to=sam@ravnborg.org \
--cc=antonynpavlov@gmail.com \
--cc=barebox@lists.infradead.org \
/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