Re: Procedure for submitting RISC-V based BSP to Newlib

Hi Bandhav, Michael:

riscv-newlib in riscv-gnu-toolchain basically won't modify anything if
possible, it just kind of buffer, hold some un-upstreamed patches, and
will going to upstream eventually, it's also a place to report RISC-V
specific bug.

So the newlib part I think you could submit patches to this mailing
list directly or send a pull request on riscv-newlib is fine.
And riscv-gnu-toolchain part you could try to fork it first, and might
send pull request on gitthub to start further discussion about how to
integration.

:)

On Wed, Jul 24, 2019 at 9:10 PM Prof. Michael Taylor
<[email protected]> wrote:
>
> 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 <[email protected]> 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.