From: Peter Maydell <peter.maydell@linaro.org>
To: John Snow <jsnow@redhat.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
qemu-devel <qemu-devel@nongnu.org>,
Andrew Baumann <Andrew.Baumann@microsoft.com>
Subject: Re: [Qemu-devel] Call for GSoC 2017 mentors & project ideas
Date: Thu, 9 Feb 2017 22:01:38 +0000 [thread overview]
Message-ID: <CAFEAcA8zSZ8S09APwV8SGy3oHeiutY1j+LSSP327hyZLFfDURw@mail.gmail.com> (raw)
In-Reply-To: <e5673883-cd68-7d4a-01fc-394c506b18a9@redhat.com>
On 9 February 2017 at 20:46, John Snow <jsnow@redhat.com> wrote:
> On 02/09/2017 07:46 AM, Peter Maydell wrote:
>> Slightly late, but I had an idea last night: would "get
>> Raspbian booting on our raspi2 board model" be a good
>> project? Would involve some mix of bug fixing, cleaning
>> up and adding device models from the raspi2 tree on github,
>> and implementing missing devices. Bit of a "how long is a
>> piece of string" project, but on the other hand breaks
>> down easily into small parts that can all go upstream
>> individually. Would suit student who likes debugging :-)
> Who was working on this most recently? There was someone submitting
> patches pretty frequently for the raspi2 board within the last year,
> wasn't there?
That was Andrew Baumann, but I think his use case was
getting Windows 10 to boot on it, which exercises
different bits of the hardware.
thanks
-- PMM
next prev parent reply other threads:[~2017-02-09 22:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 10:52 [Qemu-devel] Call for GSoC 2017 mentors & project ideas Stefan Hajnoczi
2017-01-18 11:12 ` Alex Bennée
2017-01-19 16:27 ` Stefan Hajnoczi
2017-02-09 12:46 ` Peter Maydell
2017-02-09 20:46 ` John Snow
2017-02-09 22:01 ` Peter Maydell [this message]
2017-02-09 22:12 ` Andrew Baumann
2017-02-09 22:17 ` Peter Maydell
2017-02-13 13:46 ` Stefan Hajnoczi
2017-02-13 14:29 ` Alex Bennée
2017-02-13 14:36 ` Peter Maydell
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=CAFEAcA8zSZ8S09APwV8SGy3oHeiutY1j+LSSP327hyZLFfDURw@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=Andrew.Baumann@microsoft.com \
--cc=jsnow@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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 NNTP newsgroup(s).