From: "Michael S. Tsirkin" <mst@redhat.com>
To: Sebastian Herbszt <herbszt@gmx.de>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] piix: use pci_config_set_prog_interface()
Date: Mon, 27 Dec 2010 16:01:38 +0200 [thread overview]
Message-ID: <20101227140136.GA27055@redhat.com> (raw)
In-Reply-To: <1292879881$2997@local>
On Mon, Dec 20, 2010 at 10:18:01PM +0100, Sebastian Herbszt wrote:
> Use pci_config_set_prog_interface().
>
> Signed-off-by: Sebastian Herbszt <herbszt@gmx.de>
Since I was asked explicitly - I don't have a problem
with these changes: both class and prog interface.
However, they aren't all that useful in themselves.
For class, what I would like to see is a system where
the device class is put in the qdev info table,
and where -device ?
(and hopefully the legacy -help, -nic etc as well)
use this information.
pci_config_set_prog_interface can then have an assert to
verify that value.
Maybe we can even make e.g. -device nic work.
In a similar way, pci_config_set_prog_interface
would really become useful if we put the handling
for the legacy classes in a central place
(e.g. pci_class.c)
Any chance of doing something like the above?
I'd be happy to apply such patches.
> diff --git a/hw/ide/piix.c b/hw/ide/piix.c
> index 1cad906..2772e08 100644
> --- a/hw/ide/piix.c
> +++ b/hw/ide/piix.c
> @@ -135,7 +135,7 @@ static int pci_piix_ide_initfn(PCIIDEState *d)
> {
> uint8_t *pci_conf = d->dev.config;
>
> - pci_conf[PCI_CLASS_PROG] = 0x80; // legacy ATA mode
> + pci_config_set_prog_interface(pci_conf, 0x80); // legacy ATA mode
> pci_config_set_class(pci_conf, PCI_CLASS_STORAGE_IDE);
>
> qemu_register_reset(piix3_reset, d);
>
next prev parent reply other threads:[~2010-12-27 14:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-20 21:18 [Qemu-devel] [PATCH] piix: use pci_config_set_prog_interface() Sebastian Herbszt
2010-12-27 14:01 ` Michael S. Tsirkin [this message]
2010-12-28 16:24 ` [Qemu-devel] " Sebastian Herbszt
2010-12-28 17:19 ` Michael S. Tsirkin
2010-12-28 18:48 ` Sebastian Herbszt
2010-12-28 21:08 ` Michael S. Tsirkin
2010-12-29 10:26 ` Sebastian Herbszt
2010-12-29 11:21 ` Michael S. Tsirkin
2010-12-29 14:55 ` Michael S. Tsirkin
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=20101227140136.GA27055@redhat.com \
--to=mst@redhat.com \
--cc=herbszt@gmx.de \
--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 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).