qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	John Snow <jsnow@redhat.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: Mon, 13 Feb 2017 14:29:42 +0000	[thread overview]
Message-ID: <87k28uupt5.fsf@linaro.org> (raw)
In-Reply-To: <20170213134637.GC10361@stefanha-x1.localdomain>


Stefan Hajnoczi <stefanha@gmail.com> writes:

> On Thu, Feb 09, 2017 at 10:17:45PM +0000, Peter Maydell wrote:
>> On 9 February 2017 at 22:12, Andrew Baumann
>> <Andrew.Baumann@microsoft.com> wrote:
>> >> From: Peter Maydell [mailto:peter.maydell@linaro.org]
>> >> Sent: Thursday, 9 February 2017 14:02
>> >> 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.
>> >
>> > That's right, but I thought we also had Raspbian working after
>> > Peter C's implementation of SETEND. (I wouldn't be surprised if
>> > it had regressed, however.)
>>
>> For the raspbian kernel image I had it never worked -- I
>> think the kernel gained some new functionality that means
>> it now touches some device we don't yet implement (vague
>> recollection it was somethnig message-box related?).

There are RNG related patches on the list at the moment.

>>
>> > I've dropped the ball on this, and don't forsee finding time
>> > for it in the immediate future, but if anyone wants to work
>> > on it there are still some outstanding bits of emulation
>> > lurking in my github tree (github.com/0xabu/qemu)
>>
>> Yeah, I figured that was probably the situation, and I
>> don't personally have the time to do it either; but
>> it seemed like maybe it would make a GSoC project.
>
> It sounds like this can be broken down into tasks by a mentor willing to
> participate and knowledgable (or willing to do the homework) on device
> support status.
>
> Are there any volunteers?

I'd be happy to help mentor if needed. I guess it will depend of anyone
picks the project up?

>
> This would be a great project to have on board.
>
> Stefan


--
Alex Bennée

  reply	other threads:[~2017-02-13 14:29 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
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 [this message]
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=87k28uupt5.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=Andrew.Baumann@microsoft.com \
    --cc=jsnow@redhat.com \
    --cc=peter.maydell@linaro.org \
    --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).