public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Bandhav Veluri <bandhav@uw.edu>
To: newlib@sourceware.org
Cc: Bandhav Veluri <bandhav.veluri00@gmail.com>,
	Michael <prof.taylor@gmail.com>
Subject: Procedure for submitting RISC-V based BSP to Newlib
Date: Wed, 24 Jul 2019 07:24:00 -0000	[thread overview]
Message-ID: <CALPOZ+cJDu48F=G6wH9f8VZVuNk===sshEnkw+JNMc7AEtajAg@mail.gmail.com> (raw)

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

             reply	other threads:[~2019-07-24  7:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-24  7:24 Bandhav Veluri [this message]
2019-07-24 13:10 ` Prof. Michael Taylor
2019-07-24 16:20   ` Kito Cheng
2019-07-24 21:40     ` Jim Wilson

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='CALPOZ+cJDu48F=G6wH9f8VZVuNk===sshEnkw+JNMc7AEtajAg@mail.gmail.com' \
    --to=bandhav@uw.edu \
    --cc=bandhav.veluri00@gmail.com \
    --cc=newlib@sourceware.org \
    --cc=prof.taylor@gmail.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).