Am Sat, 19 Oct 2019 13:10:27 +0200
schrieb Thomas Huth :
> Am Sat, 19 Oct 2019 12:48:59 +0200
> schrieb Thomas Huth :
>
> > Am Thu, 17 Oct 2019 14:29:04 +0100
> > schrieb Peter Maydell :
> >
> > > Switch the mcf5206 code away from bottom-half based ptimers to
> > > the new transaction-based ptim
Am Sat, 19 Oct 2019 12:48:59 +0200
schrieb Thomas Huth :
> Am Thu, 17 Oct 2019 14:29:04 +0100
> schrieb Peter Maydell :
>
> > Switch the mcf5206 code away from bottom-half based ptimers to
> > the new transaction-based ptimer API. This just requires adding
> > begin/commit calls around the vario
Am Thu, 17 Oct 2019 14:29:04 +0100
schrieb Peter Maydell :
> Switch the mcf5206 code away from bottom-half based ptimers to
> the new transaction-based ptimer API. This just requires adding
> begin/commit calls around the various places that modify the ptimer
> state, and using the new ptimer_ini
On 10/17/19 3:29 PM, Peter Maydell wrote:
Switch the mcf5206 code away from bottom-half based ptimers to
the new transaction-based ptimer API. This just requires adding
begin/commit calls around the various places that modify the ptimer
state, and using the new ptimer_init() function to create t
On 10/17/19 6:29 AM, Peter Maydell wrote:
> Switch the mcf5206 code away from bottom-half based ptimers to
> the new transaction-based ptimer API. This just requires adding
> begin/commit calls around the various places that modify the ptimer
> state, and using the new ptimer_init() function to cr
Switch the mcf5206 code away from bottom-half based ptimers to
the new transaction-based ptimer API. This just requires adding
begin/commit calls around the various places that modify the ptimer
state, and using the new ptimer_init() function to create the timer.
Signed-off-by: Peter Maydell
---
