From: Paolo Bonzini <pbonzini@redhat.com>
To: Laine Stump <laine@redhat.com>, qemu list <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] which machinetypes have an integrated/implied IDE controller?
Date: Fri, 13 Nov 2015 11:24:02 +0100 [thread overview]
Message-ID: <5645BA42.1010809@redhat.com> (raw)
In-Reply-To: <5644F016.6060206@redhat.com>
A quick "git grep -l ahci" says that in addition to q35, three ARM
boards have an AHCI controller: highbank, cubieboard (also known as
allwinner-a10) and xilinx-zynq-a9 (also known as xlnx-zynqmp).
Everything else that has IDE really means parallel ATA.
In practice the only difference between the two is that parallel ATA
distinguishes master/slave, while serial ATA has only one unit per bus
(in addition, PATA has two buses while SATA/AHCI has six).
On 12/11/2015 21:01, Laine Stump wrote:
> But I just received an email from someone who informed me that the
> "ppc-beigeg3" machine type also has an IDE controller, and that
> additionally this is the *only* method of connecting a disk on this
> particular machine.
That's not exactly true since g3beige has a PCI controller. It may well
be that IDE is the only one supported by the firmware.
> So now I'm wondering how I can determine what other
> machinetypes have an integrated IDE controller, so that I can add them
> to this check. (I would also like to find out which qemu binary supports
> the "ppc-beigeg3" machinetype - I tried running "qemu-blah -M ?" for
> every qemu binary on my Fedora 22 system, and didn't see anything like
> that).
It's actually called g3beige. :)
Paolo
next prev parent reply other threads:[~2015-11-13 10:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 20:01 [Qemu-devel] which machinetypes have an integrated/implied IDE controller? Laine Stump
2015-11-13 10:24 ` Paolo Bonzini [this message]
2015-11-13 13:03 ` Markus Armbruster
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=5645BA42.1010809@redhat.com \
--to=pbonzini@redhat.com \
--cc=laine@redhat.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.