Am 05.02.2013 14:07, schrieb Peter Maydell: > On 5 February 2013 12:58, Paolo Bonzini <pbonz...@redhat.com> wrote: >> Il 05/02/2013 12:06, Andreas Färber ha scritto: >>> Am 04.02.2013 22:23, schrieb Peter Maydell: >>> So where would you like a tegra2.c SoC device/object to live? >>> It depends on ARMCPU and is thus fo me a clear candidate for hw/arm/, >>> among boards such as ac100.c, kaen.c, ... >> >> I think we agree that almost all of it would be in hw/i2c/tegra2_i2c.c, >> hw/sd/tegra2_sd.c, hw/misc/tegra2_whatever.c. If you need a device just >> because you're developing it with QOM composition, then the device could >> go in hw/arm/tegra2.c together with the board description. As they say, >> the exception that confirms the rule. > > We could have a "hw/socks" directory for devices which are pure > containers :-)
I'd surely prefer hw/socs/ over hw/socks/ ;) but my point is why would we want to mix arm and sh4 SoCs (with a clear dependency on $arch) rather than putting them into hw/$arch proper. As Paolo points out, this is (once again) discussing the strictness of your sayings, in this case 'no devices in hw/$arch' (pseudo-quote). Andreas -- SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
