Peter Maydell writes:
> On Fri, 24 Sept 2021 at 15:43, Daniel P. Berrangé wrote:
>>
>> On Fri, Sep 24, 2021 at 03:35:52PM +0200, Markus Armbruster wrote:
>> > Peter Maydell writes:
>> > > Side side note: the JSON event doesn't seem to contemplate
>> > > the possibility that a machine might
On Fri, 24 Sept 2021 at 15:43, Daniel P. Berrangé wrote:
>
> On Fri, Sep 24, 2021 at 03:35:52PM +0200, Markus Armbruster wrote:
> > Peter Maydell writes:
> > > Side side note: the JSON event doesn't seem to contemplate
> > > the possibility that a machine might have more than one RTC...
> >
> >
On Fri, Sep 24, 2021 at 03:35:52PM +0200, Markus Armbruster wrote:
> Peter Maydell writes:
>
> > On Fri, 24 Sept 2021 at 13:21, Markus Armbruster wrote:
> >> ... this isn't really *target*-specific, it's *device*-specific: some
> >> devices implement the event, some don't.
> >>
> >> Ideally,
Peter Maydell writes:
> On Fri, 24 Sept 2021 at 13:21, Markus Armbruster wrote:
>> ... this isn't really *target*-specific, it's *device*-specific: some
>> devices implement the event, some don't.
>>
>> Ideally, we'd just fix that.
>
> Would you want to tell the far end "this machine simply
On Fri, 24 Sept 2021 at 13:29, Marc-André Lureau
wrote:
> On Fri, Sep 24, 2021 at 4:21 PM Markus Armbruster wrote:
>>
>> Peter Maydell writes:
>> > Could we reconsider this change? It seems to me to be adding
>> > complexity and build time and I don't really see the advantage
>> > that
On Fri, 24 Sept 2021 at 13:21, Markus Armbruster wrote:
> ... this isn't really *target*-specific, it's *device*-specific: some
> devices implement the event, some don't.
>
> Ideally, we'd just fix that.
Would you want to tell the far end "this machine simply does
not have an RTC device at all
Hi
On Fri, Sep 24, 2021 at 4:21 PM Markus Armbruster wrote:
> Peter Maydell writes:
>
> > On Mon, 18 Feb 2019 at 14:19, Markus Armbruster
> wrote:
> >>
> >> From: Marc-André Lureau
> >>
> >> A few targets don't emit RTC_CHANGE, we could restrict the event to
> >> the tagets that do emit it.
Peter Maydell writes:
> On Mon, 18 Feb 2019 at 14:19, Markus Armbruster wrote:
>>
>> From: Marc-André Lureau
>>
>> A few targets don't emit RTC_CHANGE, we could restrict the event to
>> the tagets that do emit it.
>>
>> Note: There is a lot more of events & commands that we could restrict
>>
On 23/09/21 15:14, Peter Maydell wrote:
It also means that now rtc devices that emit this event need to
change in meson.build from softmmu_ss to specific_ss, because the
qapi_event_send_rtc_change() prototype is in the generated
qapi/qapi-events-misc-target.h header, and that header uses
On Mon, 18 Feb 2019 at 14:19, Markus Armbruster wrote:
>
> From: Marc-André Lureau
>
> A few targets don't emit RTC_CHANGE, we could restrict the event to
> the tagets that do emit it.
>
> Note: There is a lot more of events & commands that we could restrict
> to capable targets, with the cost
10 matches
Mail list logo
