linux-riscv.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Damien Le Moal <Damien.LeMoal@wdc.com>
To: Drew Fustini <drew@beagleboard.org>,
	"linux-riscv@lists.infradead.org"
	<linux-riscv@lists.infradead.org>
Subject: Re: Current options for Linux on RISC-V?
Date: Wed, 25 Dec 2019 04:44:38 +0000	[thread overview]
Message-ID: <BYAPR04MB5816D2323D68B6BA4B02B9EFE7280@BYAPR04MB5816.namprd04.prod.outlook.com> (raw)
In-Reply-To: CAPgEAj6edQiTtXkau+E5hSb=RcQ7vjv=kTN0yAmgbOYXEx0+Dw@mail.gmail.com

On 2019/12/24 22:28, Drew Fustini wrote:
> Hello, I'm giving a talk about Linux, Open Source Hardware and RISC-V
> this Sunday at the Chaos Communication Congress (36c3) in Germany [1].
> 
> I want to make sure I am up-to-date about the current ways that people
> could run Linux on RISC-V:
> 
> - QEMU on x86 (Fedora / Debian)
> - SiFive Freedom Unleashed board (unfortunately expensive)
> - Kendryte K210 (NOMMU, limited SRAM, I am not sure how to reproduce
> the LPC demo) [2]

The K210 specific code is still missing upstream. I have not yet posted
anything, lack of time being the prime reason. We still need a proper
device tree, a defconfig and additional code for enabling the last 2MB
of SRAM which are not automatically enabled by the HW on power up.

Flatbin format for userland would work, but proper FDPIC support would
be nicer. gcc and uclibc will need work for that to happen. We are
currently looking at that.


> - RISC-V soft core on Xilinix or Altera FPGA with proprietary toolchain
> - LiteX-On-Linux with VexRIscV on Lattice ECP5 FPGA with and open
> source tools (trellis, yosys, nextpnr)
> - Microchip/MicroSemi PolarFire SoC (stil coming soon?)
> - Future: OpenHW Group and NXP making RISC-V iMX-style SoC?
> 
> Any other options that I missed?
> 
> Thank you,
> Drew
> 
> [1] https://fahrplan.events.ccc.de/congress/2019/Fahrplan/events/10549.html
> [2] https://youtu.be/ycG592N9EMA?t=10394
> 
> 


-- 
Damien Le Moal
Western Digital Research


      parent reply	other threads:[~2019-12-25  4:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-24 13:27 Current options for Linux on RISC-V? Drew Fustini
2019-12-24 14:54 ` Charles Papon
2019-12-25  4:44 ` Damien Le Moal [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=BYAPR04MB5816D2323D68B6BA4B02B9EFE7280@BYAPR04MB5816.namprd04.prod.outlook.com \
    --to=damien.lemoal@wdc.com \
    --cc=drew@beagleboard.org \
    --cc=linux-riscv@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;
as well as URLs for NNTP newsgroup(s).