All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>, Alexander Graf <agraf@suse.de>,
	qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v2] ahci: add -drive support
Date: Thu, 12 Jul 2012 13:33:01 +0200	[thread overview]
Message-ID: <4FFEB5ED.20405@redhat.com> (raw)
In-Reply-To: <m3liiptev8.fsf@blackfin.pond.sub.org>

Il 12/07/2012 13:09, Markus Armbruster ha scritto:
>> >
>> > It isn't. AHCI is on the same level as IDE. They both speak ATA, but
>> > the guest os interface is completely different. You can write a
>> > generic IDE driver, but that won't be able to talk to an AHCI
>> > controller in AHCI mode. You can write a generic AHCI driver, but that
>> > won't be able to talk to an IDE controller.
> Yes, but does the naive command line user care?
> 
> -serial configures a serial device.  The kind of device depends on the
> board: 16550A UARTs with -M pc, Exynos 4210 UARTs with -M nuri, ColdFire
> UARTs with -M an5206, ...  You can't write a generic serial device
> driver.

The naive command line user uses -cdrom or just "qemu file.img", they do
not use -drive.

The non-naive command line user who has so far been using -drive with
if=ide, can learn to omit it when they move to q35.

Paolo

  parent reply	other threads:[~2012-07-12 11:33 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1340714974-25489-1-git-send-email-agraf@suse.de>
2012-07-09  8:50 ` [Qemu-devel] [PATCH v2] ahci: add -drive support Markus Armbruster
2012-07-09  9:11   ` Kevin Wolf
2012-07-09  9:13     ` Alexander Graf
2012-07-09  9:27       ` Kevin Wolf
2012-07-09  9:36         ` Alexander Graf
2012-07-09  9:41           ` Gleb Natapov
2012-07-09  9:44             ` Alexander Graf
2012-07-09  9:46               ` Gleb Natapov
2012-07-09  9:52           ` Kevin Wolf
2012-07-09 10:02             ` Gleb Natapov
2012-07-09 10:03               ` Kevin Wolf
2012-07-09 10:05                 ` Gleb Natapov
2012-07-09 10:14             ` Gerd Hoffmann
2012-07-09 11:05               ` Markus Armbruster
2012-07-09 11:06     ` Markus Armbruster
2012-07-09 11:08       ` Alexander Graf
2012-07-09 11:19         ` Markus Armbruster
2012-07-09 11:22           ` Alexander Graf
2012-07-11 22:33   ` Alexander Graf
2012-07-12  8:17     ` Markus Armbruster
2012-07-12  8:23       ` Alexander Graf
2012-07-12 11:09         ` Markus Armbruster
2012-07-12 11:28           ` Alexander Graf
2012-07-12 11:42             ` Markus Armbruster
2012-07-12 11:33           ` Paolo Bonzini [this message]
2012-07-12  8:42       ` Gerd Hoffmann
2012-07-12 10:58         ` Markus Armbruster
2012-07-12 11:50       ` Alexander Graf
2012-07-12 14:39         ` 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=4FFEB5ED.20405@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=agraf@suse.de \
    --cc=armbru@redhat.com \
    --cc=kwolf@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.