BALATON Zoltan writes:
> On Wed, 22 Sep 2021, Markus Armbruster wrote:
>> BALATON Zoltan writes:
>>> To me it looks like device code can't really set a globally unique
>>> name on creating the bus without getting some help from upper
>>> levels. So maybe naming busses should be done by qdev (or
On Wed, 22 Sep 2021, Markus Armbruster wrote:
BALATON Zoltan writes:
On Tue, 21 Sep 2021, Peter Maydell wrote:
On Wed, 15 Sept 2021 at 05:28, Markus Armbruster wrote:
Peter Maydell writes:
I'm not sure how best to sort this tangle out. We could:
* make controller devices pass in NULL
On 9/22/21 09:02, Markus Armbruster wrote:
Peter Maydell writes:
On Wed, 15 Sept 2021 at 05:28, Markus Armbruster wrote:
Peter Maydell writes:
I'm not sure how best to sort this tangle out. We could:
* make controller devices pass in NULL as bus name; this
means that some bus names
Peter Maydell writes:
> On Wed, 15 Sept 2021 at 05:28, Markus Armbruster wrote:
>>
>> Peter Maydell writes:
>> > I'm not sure how best to sort this tangle out. We could:
>> > * make controller devices pass in NULL as bus name; this
>> >means that some bus names will change, which is an
Peter Maydell writes:
[...]
> I'm not sure how best to sort this tangle out. We could:
> * make controller devices pass in NULL as bus name; this
>means that some bus names will change, which is an annoying
>breakage but for these minor bus types we can probably
>get away with it.
BALATON Zoltan writes:
> On Tue, 21 Sep 2021, Peter Maydell wrote:
>> On Wed, 15 Sept 2021 at 05:28, Markus Armbruster wrote:
>>>
>>> Peter Maydell writes:
I'm not sure how best to sort this tangle out. We could:
* make controller devices pass in NULL as bus name; this
means
On Tue, 21 Sep 2021, Peter Maydell wrote:
On Wed, 15 Sept 2021 at 05:28, Markus Armbruster wrote:
Peter Maydell writes:
I'm not sure how best to sort this tangle out. We could:
* make controller devices pass in NULL as bus name; this
means that some bus names will change, which is an
On Wed, 15 Sept 2021 at 05:28, Markus Armbruster wrote:
>
> Peter Maydell writes:
> > I'm not sure how best to sort this tangle out. We could:
> > * make controller devices pass in NULL as bus name; this
> >means that some bus names will change, which is an annoying
> >breakage but for
Peter Maydell writes:
> On Thu, 26 Aug 2021 at 15:08, Markus Armbruster wrote:
>> Peter Maydell writes:
>> > What's the right way to ensure that when a machine has multiple
>> > buses of the same type (eg multiple i2c controllers, multiple
>> > sd card controllers) they all get assigned unique
On Thu, 26 Aug 2021 at 15:08, Markus Armbruster wrote:
> Peter Maydell writes:
> > What's the right way to ensure that when a machine has multiple
> > buses of the same type (eg multiple i2c controllers, multiple
> > sd card controllers) they all get assigned unique names so that
> > the user
Peter Maydell writes:
> What's the right way to ensure that when a machine has multiple
> buses of the same type (eg multiple i2c controllers, multiple
> sd card controllers) they all get assigned unique names so that
> the user can use '-device ...,bus=some-name' to put a device on a
> specific
On Thu, 12 Aug 2021 at 12:05, Peter Maydell wrote:
>
> What's the right way to ensure that when a machine has multiple
> buses of the same type (eg multiple i2c controllers, multiple
> sd card controllers) they all get assigned unique names so that
> the user can use '-device ...,bus=some-name'
What's the right way to ensure that when a machine has multiple
buses of the same type (eg multiple i2c controllers, multiple
sd card controllers) they all get assigned unique names so that
the user can use '-device ...,bus=some-name' to put a device on a
specific bus?
For instance in
13 matches
Mail list logo
