On Thu, 24 Oct 2019 at 19:10, Mark Cave-Ayland
wrote:
>
> On 24/10/2019 13:19, Peter Maydell wrote:
> > I'm going to apply these to target-arm.next; I know they haven't
> > been on list long but the change since v1 is only minor and
> > they've all been reviewed.
>
> Thanks Peter! Not sure if you
On 10/24/19 8:04 PM, Mark Cave-Ayland wrote:
On 24/10/2019 13:19, Peter Maydell wrote:
On Mon, 21 Oct 2019 at 14:43, Peter Maydell wrote:
This patchset converts the devices used by sparc machines to the new
ptimer API.
Currently the ptimer design uses a QEMU bottom-half as its mechanism
for
On 24/10/2019 13:19, Peter Maydell wrote:
> On Mon, 21 Oct 2019 at 14:43, Peter Maydell wrote:
>>
>> This patchset converts the devices used by sparc machines to the new
>> ptimer API.
>>
>> Currently the ptimer design uses a QEMU bottom-half as its mechanism
>> for calling back into the device m
On Mon, 21 Oct 2019 at 14:43, Peter Maydell wrote:
>
> This patchset converts the devices used by sparc machines to the new
> ptimer API.
>
> Currently the ptimer design uses a QEMU bottom-half as its mechanism
> for calling back into the device model using the ptimer when the
> timer has expired.
On 10/21/19 3:43 PM, Peter Maydell wrote:
This patchset converts the devices used by sparc machines to the new
ptimer API.
Currently the ptimer design uses a QEMU bottom-half as its mechanism
for calling back into the device model using the ptimer when the
timer has expired. Unfortunately this
This patchset converts the devices used by sparc machines to the new
ptimer API.
Currently the ptimer design uses a QEMU bottom-half as its mechanism
for calling back into the device model using the ptimer when the
timer has expired. Unfortunately this design is fatally flawed,
because it means t
