This is the mail archive of the
newlib@sourceware.org
mailing list for the newlib project.
Re: Procedure for submitting RISC-V based BSP to Newlib
- From: "Prof. Michael Taylor" <prof dot taylor at gmail dot com>
- To: newlib at sourceware dot org
- Cc: Bandhav Veluri <bandhav dot veluri00 at gmail dot com>, Bandhav Veluri <bandhav at uw dot edu>
- Date: Wed, 24 Jul 2019 06:10:11 -0700
- Subject: Re: Procedure for submitting RISC-V based BSP to Newlib
- References: <CALPOZ+cJDu48F=G6wH9f8VZVuNk===sshEnkw+JNMc7AEtajAg@mail.gmail.com>
A little more on this —
1. It does this by supporting a miniature DRAM-based file system.
2. We have targeted RISC-V, but it is not necessarily RISC-V specific. It
could work with any architecture.
3. It seems to me that there are two separate issues; one is upstreaming to
newlib, and the other is updating RISC-V infrastructure to be able to
select this BSP.
Michael Taylor
Professor
University of Washington
On Wed, Jul 24, 2019 at 12:22 AM Bandhav Veluri <bandhav@uw.edu> wrote:
> Hi,
>
> In our research group at University of Washington, we developed a generic
> riscv BSP with integrated file-system that can support file i/o without the
> need for any i/o proxying mechanism. What would be the appropriate place to
> submit a pull request for our BSP? I'm uncertain because the
> riscv-gnu-toolchain seem to use a forked copy of newlib called riscv-newlib.
>
> Is there a way to upstream our work in a way that riscv-gnu-toolchain
> could provide an option to install the toolchain with our BSP?
>
> Thanks,
> Bandhav
>
--
Apologies for all typos. Message sent by combination of an approximate
neural network and a smartphone.