On 14 March 2012 16:01, Andreas Färber <afaer...@suse.de> wrote: > Based on qom-cpu v4 and object_class_get_list() v2, this series converts > the SuperH CPU to QOM. > > The SH7750 SoC code invited to do some cleanups, making use of the SuperHCPU, > so I've QOM'ified the SoC and added the CPU as a link<SuperHCPU> for now. > > I'm not so happy about the link construct, so it may need to be redone > as a SysBus device with qdev properties
Shouldn't the CPU be a child of the SoC, not a link? >- long-term I'd like to have a > "system-on-chip" type derived from TYPE_DEVICE. Deriving it from > TYPE_SYS_BUS_DEVICE might make for a better v2. I think TYPE_SYS_BUS_DEVICE should go away in favour of everything being a TYPE_DEVICE. What do you think a "system-on-chip" type would be needed for? I would have expected that SoCs would basically just be "containers" of devices and directly be TYPE_DEVICEs... -- PMM
