Markus Armbruster arm...@redhat.com writes:
Alex Williamson alex.william...@redhat.com writes:
On Tue, 2010-06-15 at 10:53 +0200, Markus Armbruster wrote:
Alex Williamson alex.william...@redhat.com writes:
[...]
virtio-serial doesn't seem to make a DeviceState per port, so I think it
can
Alex Williamson alex.william...@redhat.com writes:
On Tue, 2010-06-15 at 10:53 +0200, Markus Armbruster wrote:
Alex Williamson alex.william...@redhat.com writes:
On Mon, 2010-06-14 at 09:02 +0200, Gerd Hoffmann wrote:
Hi,
My premise with this attempt is that we walk the hierarchy
Alex Williamson alex.william...@redhat.com writes:
On Mon, 2010-06-14 at 09:02 +0200, Gerd Hoffmann wrote:
Hi,
My premise with this attempt is that we walk the hierarchy and use the
names to create the base of the path. As we get to the device,
particularly to the parent bus of the
ISA: serial/parallel = iobase, others??
ne2k_isa has iobase too.
I think all remaining isa devices (timer, kbd, vga, ...) have a fixed
i/o base and can be only once in the system.
ide-drive: unit
I2C: address
virtio-serial doesn't seem to make a DeviceState per port, so I think it
can be
On Tue, 2010-06-15 at 10:53 +0200, Markus Armbruster wrote:
Alex Williamson alex.william...@redhat.com writes:
On Mon, 2010-06-14 at 09:02 +0200, Gerd Hoffmann wrote:
Hi,
My premise with this attempt is that we walk the hierarchy and use the
names to create the base of the path.
On Tue, 2010-06-15 at 11:12 +0200, Gerd Hoffmann wrote:
ISA: serial/parallel = iobase, others??
ne2k_isa has iobase too.
Added
I think all remaining isa devices (timer, kbd, vga, ...) have a fixed
i/o base and can be only once in the system.
Yep, isa doesn't support hotplug either, so
Hi,
My premise with this attempt is that we walk the hierarchy and use the
names to create the base of the path. As we get to the device,
particularly to the parent bus of the device, we need to start looking at
properties to ensure uniqueness.
You'll need that for every bus along the way
On Mon, 2010-06-14 at 09:02 +0200, Gerd Hoffmann wrote:
Hi,
My premise with this attempt is that we walk the hierarchy and use the
names to create the base of the path. As we get to the device,
particularly to the parent bus of the device, we need to start looking at
properties to
