On Mon, Sep 28, 2020 at 12:45:15PM +0200, Damien Hedde wrote:
>
>
> On 9/28/20 9:53 AM, Luc Michel wrote:
> > On 11:08 Sun 27 Sep , Philippe Mathieu-Daudé wrote:
> >> Instead of directly aborting, display a hint to help the developer
> >> figure out the problem (likely trying to connect a clo
On 9/28/20 9:53 AM, Luc Michel wrote:
> On 11:08 Sun 27 Sep , Philippe Mathieu-Daudé wrote:
>> Instead of directly aborting, display a hint to help the developer
>> figure out the problem (likely trying to connect a clock to a device
>> pre-dating the Clock API, thus not expecting clocks).
>
On 11:08 Sun 27 Sep , Philippe Mathieu-Daudé wrote:
> Instead of directly aborting, display a hint to help the developer
> figure out the problem (likely trying to connect a clock to a device
> pre-dating the Clock API, thus not expecting clocks).
>
> Signed-off-by: Philippe Mathieu-Daudé
Re
Instead of directly aborting, display a hint to help the developer
figure out the problem (likely trying to connect a clock to a device
pre-dating the Clock API, thus not expecting clocks).
Signed-off-by: Philippe Mathieu-Daudé
---
hw/core/qdev-clock.c | 11 +++
1 file changed, 11 insert