From: Anthony Liguori <anthony@codemonkey.ws>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC PATCH 0/9] Configurable PCI device addresses
Date: Fri, 23 Jan 2009 13:28:59 -0600 [thread overview]
Message-ID: <497A1A7B.8030300@codemonkey.ws> (raw)
In-Reply-To: <200901231906.08178.paul@codesourcery.com>
Paul Brook wrote:
>> I think we're starting to get to the tipping point where we really just
>> need to introduce a machine config file.
>>
>> Paul, you mentioned you were working on something before? Care to
>> update us on the status?
>>
>> I know there was a fair bit of support before for a FDT based machine
>> config.
>>
>
> I have a FDT based machine descriptions working locally.
>
Can you post what you have?
> Currently it's only capable of generating a small subset ARM embedded boards.
> There are a few issues that need to be resolved before it can replace most of
> the current qemu machines:
>
> - How to handle "plug-n-play" busses like PCI. The FDT provided to the kernel
> generally just describes the host bridge, and the kernel/bios figures
> everything else out using the normal PCI config mechanisms.
> - How it will interact with commandline options like -nic that modify which
> hardware is present. One possibility is to remove these options (remove -net
> nic, but leave -net tap, etc.). If users want different numbers/types of NICs
> they should use a different machine config.
> - How to handle GPIO pins, and other interconnects like I2S, SSI and I2C. I
> guess this is mainly coming up with suitable FDT representations.
>
> I have not implemented a user level config file. My work effectively just
> replaces integratorcp_init and friends.
>
A user level config file can come later.
Regards,
Anthony Liguori
> Paul
>
next prev parent reply other threads:[~2009-01-23 19:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-22 19:23 [Qemu-devel] [RFC PATCH 0/9] Configurable PCI device addresses Markus Armbruster
2009-01-22 19:30 ` [Qemu-devel] [PATCH 1/9] PCI device registration helpers Markus Armbruster
2009-01-22 19:30 ` [Qemu-devel] [PATCH 2/9] Clean up handling of name=value, ... part of -vga option argument Markus Armbruster
2009-01-22 19:30 ` [Qemu-devel] [PATCH 3/9] Support pci=... in option argument of -vga Markus Armbruster
2009-01-22 19:31 ` [Qemu-devel] [PATCH 4/9] Convert virtio_init_pci() to pci_register_device_2() Markus Armbruster
2009-01-22 19:31 ` [Qemu-devel] [PATCH 5/9] Support pci=... in option argument of -net nic Markus Armbruster
2009-01-22 19:31 ` [Qemu-devel] [PATCH 6/9] Make drives_opt[] accessible from device initialization Markus Armbruster
2009-01-22 19:31 ` [Qemu-devel] [PATCH 7/9] Support pci=... in option argument of -drive if=virtio Markus Armbruster
2009-01-22 19:31 ` [Qemu-devel] [PATCH 8/9] New option -audio as a more flexible alternative to -soundhw Markus Armbruster
2009-01-22 22:03 ` malc
2009-01-23 8:32 ` Markus Armbruster
2009-01-23 9:29 ` Kevin Wolf
2009-01-23 10:04 ` Markus Armbruster
2009-01-23 10:24 ` Kevin Wolf
2009-01-23 11:51 ` Markus Armbruster
2009-01-22 19:31 ` [Qemu-devel] [PATCH 9/9] Support pci=... in option argument of -audio Markus Armbruster
2009-01-22 20:06 ` [Qemu-devel] [RFC PATCH 0/9] Configurable PCI device addresses Anthony Liguori
2009-01-23 9:04 ` Markus Armbruster
2009-01-23 10:23 ` Daniel P. Berrange
2009-01-23 19:06 ` Paul Brook
2009-01-23 19:28 ` Anthony Liguori [this message]
2009-01-26 8:55 ` 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=497A1A7B.8030300@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=paul@codesourcery.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.