From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 116699 invoked by alias); 24 Jul 2019 16:20:19 -0000 Mailing-List: contact newlib-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: newlib-owner@sourceware.org Received: (qmail 116691 invoked by uid 89); 24 Jul 2019 16:20:18 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-4.5 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy=H*f:sk:tQjreLi, HX-Spam-Relays-External:209.85.221.68, H*i:CAKoatx3MoX9UB, H*i:sk:pmcA@ma X-HELO: mail-wr1-f68.google.com Received: from mail-wr1-f68.google.com (HELO mail-wr1-f68.google.com) (209.85.221.68) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 24 Jul 2019 16:20:17 +0000 Received: by mail-wr1-f68.google.com with SMTP id x4so47605779wrt.6 for ; Wed, 24 Jul 2019 09:20:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=k65/8QRHu4FmImvxth+A6EkaoUilSxgYdh1llytwRqE=; b=NboiUHIUak9A8y45C4q9JnnXqoLoCKdrhn/hnsbqwssr729Kbeh2pzfsRdahW5yyIi GvIEjW0pV2QkH3bI+zStnknwZGw9z95zQbILTQ/dtiF7+05p8yCPkZrrk2+xDC0q8iuA 9fmMDydzRA8VqcsJlTLQIU1+/oyc0Zp7hOrBiSLkNGpHL4RInW+g8g0W6UdP5jF5dDAz 8TKtZUyXYATjModDJ4z4Me+O41XFWeHXbbumYwk+Gty1/O86gQj6FxyqQBlX8a9i1x95 uEwzRLPeg+SuY0hpP1W0pDoN0YAUJx73dfP0pBeV/Klvgwh6PhtQct0fS2ZvGJMiiybp AJEw== MIME-Version: 1.0 References: In-Reply-To: From: Kito Cheng Date: Wed, 24 Jul 2019 16:20:00 -0000 Message-ID: Subject: Re: Procedure for submitting RISC-V based BSP to Newlib To: "Prof. Michael Taylor" Cc: Newlib , Bandhav Veluri , Bandhav Veluri , Jim Wilson , Palmer Dabbelt Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes X-SW-Source: 2019/txt/msg00341.txt.bz2 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 wrote: > > A little more on this =E2=80=94 > > 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 wrote: > > > Hi, > > > > In our research group at University of Washington, we developed a gener= ic > > 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 plac= e 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-ne= wlib. > > > > 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.