From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:37809) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gf4zx-0003lq-62 for qemu-devel@nongnu.org; Thu, 03 Jan 2019 10:33:30 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gf4zt-0007Rh-Hj for qemu-devel@nongnu.org; Thu, 03 Jan 2019 10:33:29 -0500 Received: from mx1.redhat.com ([209.132.183.28]:57706) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gf4zs-0007Qr-2b for qemu-devel@nongnu.org; Thu, 03 Jan 2019 10:33:24 -0500 From: Stefan Hajnoczi Date: Thu, 3 Jan 2019 15:33:20 +0000 Message-Id: <20190103153320.21687-1-stefanha@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: [Qemu-devel] [qemu-web RFC] Add GSoC/Outreachy 2018 retrospective blog post List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: jim@groklearning.com, marcandre.lureau@redhat.com, Paolo Bonzini , Thomas Huth , Fam Zheng , joel@jms.id.au, kraxel@redhat.com, airlied@redhat.com, Stefan Hajnoczi Signed-off-by: Stefan Hajnoczi --- Dear mentors, Let's post an overview of what was achieved in GSoC/Outreachy 2018. I have populated a blog post with information available to me, but I'm sure it can be improved to explain how the project went and the current status. Please let me know what should be changed, thanks! --- _posts/2019-01-03-internships-wrapup.md | 61 +++++++++++++++++++++++++ 1 file changed, 61 insertions(+) create mode 100644 _posts/2019-01-03-internships-wrapup.md diff --git a/_posts/2019-01-03-internships-wrapup.md b/_posts/2019-01-03-= internships-wrapup.md new file mode 100644 index 0000000..ec245e6 --- /dev/null +++ b/_posts/2019-01-03-internships-wrapup.md @@ -0,0 +1,61 @@ +--- +layout: post +title: "GSoC and Outreachy 2018 retrospective" +date: 2019-01-03 07:50:00 +0100 +categories: [gsoc, outreachy, internships] +--- +QEMU participates in open source internship programs including Google Su= mmer of +Code (GSoC) and Outreachy. These full-time remote work opportunities al= low +talented new developers to get involved in our community. This post hig= hlights +what our interns achieved in 2018. + +## micro:bit board emulation + +Julia Suvorova (Outreachy) and Steffen G=C3=B6rtz (GSoC) tackled adding = emulation +support for the [micro:bit ARM board](https://microbit.org/). Although = QEMU +already has plenty of ARM emulation code, the Cortex-M0 CPU used in the +micro:bit was not yet implemented and the nRF51 system-on-chip was also +missing. + +The goal of this project was to run micro:bit programs (usually created = with +the [MicroPython](https://python.microbit.org/v/1.1) or +[Javascript/Blocks](https://makecode.microbit.org/) IDEs) with a core se= t of +emulated devices, including the serial port, pushbuttons, and LEDs. + +QEMU 3.1 already shipped the groundwork for the new `qemu-system-arm -M +microbit` machine type. Enough functionality to run basic micro:bit pro= grams +is expected in the next QEMU release. + +## Patchew REST API improvements + +Shubham Jain (GSoC) created a REST API for the Patchew continuous integr= ation +system that is at the heart of QEMU's development process. The previous= API +was not RESTful and exposed database schema internals. + +## Qtest Driver Framework + +Emanuele Esposito (GSoC) enhanced QEMU's test infrastructure with an eng= ine +that starts tests with all variants of devices that they are capable of +driving. + +This is a complicated task in QEMU since certain devices and busses are +available in an architecture-specific way on each emulation target, maki= ng it +hard to write test cases without lots of hardcoded dependencies - and to= keep +them up-to-date! + +The qgraph framework that Emanuele created eliminates the need to hardco= de each +variant into the test. + +## Vulkan-izing VirGL + +Nathan Gau=C3=ABr (GSoC) improved VirGL, which provides an OpenGL path w= ell +supported on Linux guests. On the host, QEMU offers several console back= -ends, +from EGL to SDL. Adding a Vulkan path will require to change the current= VirGL +API, write new guest drivers, and also offer a way to display the output= . This +is a huge task, which can be split in several sub-projects. Expending th= e +current VirGL API to support Vulkan is the first step. + +## Stay tuned for 2019 internships! + +QEMU will apply to Google Summer of Code and Outreachy again in 2019. W= e hope +to offer more great open source internship opportunities for new develop= ers. --=20 2.20.1