From: Elek Roland <elek.roland@gmail.com>
To: Sebastian Herbszt <herbszt@gmx.de>
Cc: 乔崇 <qiaochong@loongson.cn>, "Joerg Roedel" <joro@8bytes.org>,
"qemu-devel Developers" <qemu-devel@nongnu.org>,
"Alexander Graf" <agraf@suse.de>
Subject: [Qemu-devel] Re: [RFC] [PATCH] add ahci support into qemu
Date: Sun, 02 May 2010 17:56:37 +0200 [thread overview]
Message-ID: <1272815797.1611.13.camel@vibrance> (raw)
In-Reply-To: <F9E71DC7256E49C8A7819F0828EA354C@FSCPC>
Hi all,
I am the GSoC student working on the project. I haven't tried the patch
yet, but I've read the code. It could use general cleanup and a lot of
development indeed, but otherwise it looks like a good base to build
complete support on so far. I'm going to try the patch in practice as
soon as I finish my university project. (It's due today.)
Chong, I'd be happy to stay in touch with you. I'm going to work on this
in the summer full time.
Regards,
Roland
On v, 2010-05-02 at 17:36 +0200, Sebastian Herbszt wrote:
> Hi,
>
> 乔崇 wrote:
> > Hi,Alexander Graf.
> >
> > I am very glad you noticed my patch about ahci.I love qemu just like I love linux.I wish I could do much more work on
> > qemu development.
> >
> > I had cloned qemu from master branch,add my patch into it,and tested ahci on i386 softmmu.
> >
> > If anyone is interested on ahci,you can test my patch like this:
> >
> > git-clone -ls git://git.savannah.nongnu.org/qemu
> > patch -p1 -i 0001-add-ahci-support-into-qemu-only-support-sata-disk.patch
> > patch -p1 -i 0002-add-ahci-device-into-i386-pc-just-for-test.patch
>
> The last submission was missing the qemu "glue", but this one looks complete. Nonetheless the old one was working fine
> enough.
>
> > ./configure --target-list=i386-softmmu
> > make
> >
> > dd if=/dev/zero of=/tmp/disk bs=1M count=100
> > ./i386-softmmu/qemu -cdrom KNOPPIX_V6.0.1CD-2009-02-08-EN.iso -boot d -drive if=sd,file=/tmp/disk
> >
> > After linux boot,you will find a ahci device named sda.
> >
> > Now this patch only support sata disk.
> > Most ahci registers and operations which are not necessary on linux are ignored.
> > Now this patch support disk identify,dma read,dma write,ignore other opertions.
>
> Do you intent to work on this and complet the support?
> There are also some minor changes needed like moving PCI_VENDOR_MYDEVICE
> and PCI_PRODUCT_MYDEVICE to pci.h and others.
>
> Did you use the Intel document #301473 for reference?
>
> > By the way how you send patch to mail list?
>
> Try "git send-email".
>
>
> Regards,
> Sebastian
>
next prev parent reply other threads:[~2010-05-02 15:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-30 12:48 [Qemu-devel] add ahci support into qemu 乔崇
2010-05-02 8:05 ` Alexander Graf
2010-05-02 12:52 ` [Qemu-devel] [RFC] [PATCH] " 乔崇
2010-05-02 15:36 ` [Qemu-devel] " Sebastian Herbszt
2010-05-02 15:49 ` Avi Kivity
2010-05-02 15:56 ` Elek Roland [this message]
2010-05-03 21:08 ` Elek Roland
2010-05-04 20:56 ` Sebastian Herbszt
2010-05-02 22:13 ` Sebastian Herbszt
2010-05-04 1:07 ` 乔崇
2010-05-04 20:51 ` Sebastian Herbszt
2010-05-05 19:37 ` Stuart Brady
2010-05-06 19:10 ` [Qemu-devel] " Sebastian Herbszt
2010-05-04 0:01 ` [Qemu-devel] " Alexander Graf
2010-05-04 0:28 ` 乔崇
2010-05-09 19:16 ` Alexander Graf
2010-05-10 11:24 ` 乔崇
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=1272815797.1611.13.camel@vibrance \
--to=elek.roland@gmail.com \
--cc=agraf@suse.de \
--cc=herbszt@gmx.de \
--cc=joro@8bytes.org \
--cc=qemu-devel@nongnu.org \
--cc=qiaochong@loongson.cn \
/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).