On Wed, Apr 03, 2013 at 04:08:45PM +0200, Paolo Bonzini wrote: > Il 03/04/2013 16:06, Michael S. Tsirkin ha scritto: > > > Ok, I'll add hw/pci/bridge, and remove the "host-" prefix for host PCI > > > devices. > > > > That's too much nesting I think. hw/bridge/ and we can put isa bridges there > > as well then. > > You need to group similar devices for the nesting to be useful. For > example, it should be easy to check if something is true of all ISA > bridges, or to do the same change in all of them. ISA and PCI bridges > have too little in common for that (and why not put I2C and SPI in > hw/bridge too :)). > > Paolo At some level it might make sense to have pci/ and isa/ with core code at the top level. Specific devices would go into hw/pci/ hw/isa/ ... But will this conflict with how libhw works at the moment? We don't want to rebuild pci for each target ... -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
