On Mon, 22 Apr 2013 15:22:30 +0200
Andreas Färber wrote:
> Am 16.04.2013 00:12, schrieb Igor Mammedov:
> > ... to provide hotplug-able bus.
> >
> > * icc-bridge will serve as a parent for icc-bus and provide
> > mmio mapping services to child icc-devices.
> > * icc-device will replace SysBusDe
Am 16.04.2013 00:12, schrieb Igor Mammedov:
> ... to provide hotplug-able bus.
>
> * icc-bridge will serve as a parent for icc-bus and provide
> mmio mapping services to child icc-devices.
> * icc-device will replace SysBusDevice as a parent of APIC
> and IOAPIC devices.
>
> Signed-off-by: Ig
Il 22/04/2013 13:39, Peter Maydell ha scritto:
>> > ... to provide hotplug-able bus.
>> >
>> > * icc-bridge will serve as a parent for icc-bus and provide
>> > mmio mapping services to child icc-devices.
>> > * icc-device will replace SysBusDevice as a parent of APIC
>> > and IOAPIC devices.
>>
On 15 April 2013 23:12, Igor Mammedov wrote:
> ... to provide hotplug-able bus.
>
> * icc-bridge will serve as a parent for icc-bus and provide
> mmio mapping services to child icc-devices.
> * icc-device will replace SysBusDevice as a parent of APIC
> and IOAPIC devices.
>
> Signed-off-by: Ig
... to provide hotplug-able bus.
* icc-bridge will serve as a parent for icc-bus and provide
mmio mapping services to child icc-devices.
* icc-device will replace SysBusDevice as a parent of APIC
and IOAPIC devices.
Signed-off-by: Igor Mammedov
---
v2:
* Rebase on top the last HW reorganiz
