From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Thu, 03 Mar 2022 11:02:41 +0100 Received: from metis.ext.pengutronix.de ([2001:67c:670:201:290:27ff:fe1d:cc33]) by lore.white.stw.pengutronix.de with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1nPiID-00GOgb-3m for lore@lore.pengutronix.de; Thu, 03 Mar 2022 11:02:41 +0100 Received: from bombadil.infradead.org ([2607:7c80:54:e::133]) by metis.ext.pengutronix.de with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nPiIB-0008U9-HW for lore@pengutronix.de; Thu, 03 Mar 2022 11:02:40 +0100 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=eViWgVXQbayik+ls+aWP2jwvplCuENZgZ0sx68L3hso=; b=0AWF9uW2GZKAQv 23mHy6pbVqebtD+REqqmQEXXIYPdltlNJuXCgi9Kz8RyPmUebuy11ijnFYpwkJ9HPHx/OLr2eEqxO 1L7Vc93vlzbbSff4Cic3quyfkuf3tTaMGIaHcQOYgVAjrV1/wpm8d094knjxKr9D3v7AsCnvLpbqS Yxu+ogSkiw1JqkLraQihV8EmSnQnW/ugidmjk+anWtCkXaqmn7KiD8aQAp7LImBok9YHEGMn5Eoqf QmME4U3J4RFZ3mbujHzekaaRni9kFstjxePN+kqxwgxe7UvYdVathsVpxKxuYvmO1DFC7b/w8IGLs dkqpFWO4KHM3WbP53UPg==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1nPiFr-005ycU-72; Thu, 03 Mar 2022 10:00:15 +0000 Received: from metis.ext.pengutronix.de ([2001:67c:670:201:290:27ff:fe1d:cc33]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1nPiFl-005ybT-Kl for barebox@lists.infradead.org; Thu, 03 Mar 2022 10:00:12 +0000 Received: from ptx.hi.pengutronix.de ([2001:67c:670:100:1d::c0]) by metis.ext.pengutronix.de with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nPiFk-0007pT-CF; Thu, 03 Mar 2022 11:00:08 +0100 Received: from sha by ptx.hi.pengutronix.de with local (Exim 4.92) (envelope-from ) id 1nPiFk-0001GO-1Y; Thu, 03 Mar 2022 11:00:08 +0100 Date: Thu, 3 Mar 2022 11:00:08 +0100 From: Sascha Hauer To: Ahmad Fatoum Cc: barebox@lists.infradead.org, rcz@pengutronix.de Message-ID: <20220303100008.GB19585@pengutronix.de> References: <20220302155846.2990159-1-a.fatoum@pengutronix.de> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20220302155846.2990159-1-a.fatoum@pengutronix.de> X-Sent-From: Pengutronix Hildesheim X-URL: http://www.pengutronix.de/ X-IRC: #ptxdist @freenode X-Accept-Language: de,en X-Accept-Content-Type: text/plain X-Uptime: 10:59:56 up 82 days, 18:45, 83 users, load average: 0.13, 0.19, 0.20 User-Agent: Mutt/1.10.1 (2018-07-13) X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220303_020009_879199_EEB1B943 X-CRM114-Status: GOOD ( 46.27 ) X-BeenThere: barebox@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "barebox" X-SA-Exim-Connect-IP: 2607:7c80:54:e::133 X-SA-Exim-Mail-From: barebox-bounces+lore=pengutronix.de@lists.infradead.org X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on metis.ext.pengutronix.de X-Spam-Level: X-Spam-Status: No, score=-4.8 required=4.0 tests=AWL,BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED,SPF_HELO_NONE,SPF_NONE, T_SCC_BODY_TEXT_LINE autolearn=unavailable autolearn_force=no version=3.4.2 Subject: Re: [PATCH] Documentation: devel: project-ideas: align with GSoC guidelines X-SA-Exim-Version: 4.2.1 (built Wed, 08 May 2019 21:11:16 +0000) X-SA-Exim-Scanned: Yes (on metis.ext.pengutronix.de) On Wed, Mar 02, 2022 at 04:58:46PM +0100, Ahmad Fatoum wrote: > Google informed orgs for GSoC 2022 about required info for ideas list: > > As we state in the Defining a Project Idea List section of the Mentor > guide, please provide the following information for each idea: > > a) a project title/description > b) more detailed description of the project (2-5+ sentences) > c) expected outcomes > d) skills required/preferred > e) possible mentors > f) expected size of project (175 or 350 hour) > g) an easy, medium or hard difficulty rating of each project. > > We are nearly there, add the missing points. > > Signed-off-by: Ahmad Fatoum > --- > Documentation/devel/project-ideas.rst | 44 ++++++++++++++++++++++----- > 1 file changed, 37 insertions(+), 7 deletions(-) Applied, thanks Sascha > > diff --git a/Documentation/devel/project-ideas.rst b/Documentation/devel/project-ideas.rst > index f27e4d5406fc..a3643298ab08 100644 > --- a/Documentation/devel/project-ideas.rst > +++ b/Documentation/devel/project-ideas.rst > @@ -13,16 +13,26 @@ If you find a project interesting and would like to work on it, reach out > to the :ref:`mailing list ` and we can together > try to figure out whether you are a good match for the project. > > +For GSoC, following barebox developers are mentoring: > + > + - Ahmad Fatoum (IRC: ``a3f``) > + - Sascha Hauer (IRC: ``_sha_``) > + - Rouven Czerwinski (IRC: ``Emantor``) > + > This list can be edited and extended by sending patches to the mailing list. > Other interesting ideas: Support for new file systems (EROFS, extfat, btrfs). > Switch device framework (currently scripts write into a ``/dev/switch`` file > to configure passthrough), Improvements for barebox-efi (e.g. as a coreboot > payload), ... etc. > > +Ideas listed below should contain a title, description, expected outcomes, > +skills (and HW if any) required and a difficulty rating. > +Projects are meant to be about 175 hours of effort, unless otherwise noted. > + > Address static analyzer feedback for barebox > ============================================ > > -Skills: C > +Skills: C. Difficulty: Lowest > > barebox is automatically tested using Synopsys' free "Coverity Scan" service. > The static analyzer has so far identified 191 possible defects at > @@ -36,13 +46,15 @@ To make this service more useful, the project would involve categorizing > reported issues and handling them as appropriate: Mark them as not applicable > if false positive or provide patches to fix real issues. > > +Expected outcome is that barebox is coverity-clean. > + > This project does not require dedicated hardware. QEMU or barebox built > to run under Linux (sandbox) may be used. > > Update barebox networking stack for IPv6 support > ================================================ > > -Skills: C, Networking > +Skills: C, Networking. Difficulty: Medium > > The barebox network stack is mainly used for TFTP and NFSv3 (over UDP) boot. > Most embedded systems barebox runs on aren't deployed to IPv6 networks yet, > @@ -55,13 +67,15 @@ makes it possible to integrate an IPv6 stack, e.g. lwIP. > There are also community patches to integrate a TCP stack into barebox. > These can be evaluated as time allows. > > +Expected outcome is that barebox can TFTP/NFS boot over IPv6. > + > This project does not require dedicated hardware. QEMU or barebox built > to run under Linux (sandbox) may be used. > > Improving barebox test coverage > =============================== > > -Skills: C > +Skills: C. Difficulty: Lowest > > barebox is normally tested end-to-end as part of a deployed system. > More selftests/emulated tests would reduce the round trip time for testing > @@ -78,13 +92,16 @@ tests for barebox functionality and by fuzzing the parsers available in > barebox, with special consideration to the FIT parser, which is used in > secure booting setups. > > +Expected outcome is a richer test suite for barebox and an automated > +setup for fuzzing security-critical parsers. > + > This project does not require dedicated hardware. QEMU or barebox built > to run under Linux (sandbox) may be used. > > Porting barebox to new hardware > =============================== > > -Skills: C, low-level affinity > +Skills: C, low-level affinity. Difficulty: Medium > > While Linux and Linux userspace can be quite generic with respect to the > hardware it runs on, the bucket needs to stop somewhere: barebox needs > @@ -102,6 +119,9 @@ If time allows (because most drivers are already available in barebox), > new drivers can be ported to enable not only running Linux on the board, > but bareDOOM as well. > > +Expected outcome is upstreamed barebox drivers and board support to > +enable running on previously unsupported hardware. > + > This project requires embedded hardware with preferably an ARM SoC, as > these have the widest barebox support, but other architectures are ok > as well. > @@ -109,7 +129,7 @@ as well. > Improve barebox RISC-V support > ============================== > > -Skills: C, RISC-V interest, low-level affinity > +Skills: C, RISC-V interest, low-level affinity. Difficulty: Medium > > barebox supports a number of both soft and hardRISC-V targets, > e.g.: BeagleV, HiFive, LiteX and the QEMU/TinyEMU Virt machine. > @@ -121,12 +141,16 @@ stage, so much opportunity in implementing the gritty details: > - MMU support in S-Mode to trap access violations > - Improve barebox support for multiple harts (hardware threads) > > +Expected outcome is better RISC-V support: Access violations are > +trapped in both S- and M-Mode. Virtual memory is implemented and > +Linux can be booted on multiple harts. > + > This project does not require dedicated hardware. QEMU can be used. > > Improve barebox I/O performance > =============================== > > -Skills: C, low-level affinity > +Skills: C, low-level affinity. Difficulty: Medium > > On a normal modern system, booting may involve mounting and traversing > a file system, which employs caching for directory entries and sits > @@ -145,13 +169,15 @@ possible to increase throughput of barebox I/O: > and write performance. This may not be optimal for all devices > and can be revisited. > > +Expected outcome is faster read/write/erasure of MMC block devices. > + > This project requires embedded hardware with SD/eMMC that is supported > by a barebox media card interface (MCI) driver. > > Improve JSBarebox, the barebox web demo > ======================================= > > -Skills: C (Basics), Javascript/Web-assembly, Browser-Profiling > +Skills: C (Basics), Javascript/Web-assembly, Browser-Profiling. Difficulty: Medium > > While Linux and Linux userspace can be quite generic with respect to the > hardware it runs on, the bucket needs to stop somewhere: barebox needs > @@ -170,5 +196,9 @@ provided with modern browsers. The remainder of the project can then > focus on improving the jsbarebox tutorial. e.g. by adding new > peripherals to the virtual machine. > > +Expected outcome is snappier and less CPU-intensive barebox demo. > +TinyEMU is extended, so the RISC-V machine is more like real > +hardware and tutorial is extended to make use of the new pripherals. > + > This project does not require dedicated hardware. The development > machine need only support a recent browser. > -- > 2.30.2 > > -- Pengutronix e.K. | | Steuerwalder Str. 21 | http://www.pengutronix.de/ | 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | _______________________________________________ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox