Cédric Le Goater <[email protected]> writes: > On 1/15/26 20:47, Philippe Mathieu-Daudé wrote: >> Hi, >> Cc'ing Markus. >> On 12/1/26 09:30, Kane Chen via qemu development wrote: >>> From: Kane-Chen-AS <[email protected]> >>> >>> Currently, the Aspeed I2C controller uses a static naming convention >>> for its buses (e.g., "aspeed.i2c.bus.0"). This approach leads to >>> object name conflicts in machine models that incorporate multiple I2C >>> controllers, such as an Aspeed SoC paired with an external IO expander >>> or a co-processor like the AST1700. >>> >> Is this a side-effect of Problem 4: 'The /machine/unattached/ orphanage' >> described here? >> https://lore.kernel.org/qemu-devel/[email protected]/ >> This problem isn't specific to I2C nor Aspeed. > > > See the discussion here : > > > https://lore.kernel.org/qemu-devel/[email protected]/ > > The Aspeed SoC has 3*16 I2C buses attached on 3 different I2C > controllers plus the I2C/I3C buses. We need to find a way to > distinguish these groups at the QEMU machine level to be able > to add devices on the right bus when using the command line. > > Suggestions welcome !
Please show me how to start a QEMU with the 48 I2C mentioned above, complete with output of "info qtree".
