All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Alexander Graf <agraf@suse.de>, Roland Elek <elek.roland@gmail.com>
Subject: Re: [Qemu-devel] GSoC projects about AHCI and S3 Trio
Date: Tue, 30 Mar 2010 12:14:01 +0000	[thread overview]
Message-ID: <201003301314.03044.paul@codesourcery.com> (raw)
In-Reply-To: <E4D57722-2474-4798-ACCB-382963862D5B@suse.de>

> Hi Roland,
> 
> On 30.03.2010, at 01:52, Roland Elek wrote:
> > Dear Qemu developers,
> >
> > I am a university student from Hungary interested in contributing to Qemu
> > through Google Summer of Code. I am interested in emulation, and two
> > projects from the ideas page in particular. One of them is AHCI
> > emulation. Can I kindly ask you what were the hardest points that made
> > the project get a high difficulty rating, so that I could determine
> > whether to apply for it or not? At a first glance, I think that AHCI code
> > from VirtualBox OSE would be a good place to start. What do you think?
> 
> I looked at the AHCI code from vbox some time ago and deemed it unreadable.
>  It's probably easier to go with the spec and implement it from there.

I agree. IIRC the AHCI documentation is pretty good.
The main reason I implemented the LSI SCSI HBA rather than AHCI was because at 
the time the SCSI HBA had much wider OS support.

Paul

  parent reply	other threads:[~2010-03-30 12:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-29 23:52 [Qemu-devel] GSoC projects about AHCI and S3 Trio Roland Elek
2010-03-30  0:55 ` Alexander Graf
2010-03-30  4:56   ` Natalia Portillo
2010-03-30 12:14   ` Paul Brook [this message]
2010-03-30 18:52     ` Roland Elek
2010-04-01 11:55       ` Paul Brook

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=201003301314.03044.paul@codesourcery.com \
    --to=paul@codesourcery.com \
    --cc=agraf@suse.de \
    --cc=elek.roland@gmail.com \
    --cc=qemu-devel@nongnu.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.