:devel-boun...@rtems.org] On Behalf Of Chris Johns
> Sent: Friday, July 11, 2014 6:08 PM
> To: devel@rtems.org
> Subject: Re: [PATCH 3/4] capture: Remove nested
> rtems_interrupt_lock_acquire calls.
>
> On 11/07/2014 4:59 pm, Sebastian Huber wrote:
> > On 2014-07-11 04:08, Chris Jo
On 11/07/2014 4:59 pm, Sebastian Huber wrote:
On 2014-07-11 04:08, Chris Johns wrote:
On 10/07/2014 11:44 pm, Jennifer Averett wrote:
Use of the cenable command was resulting in a lock in
rtems_interrupt_lock_acquire due to nesting.
I am rejecting this change. RTEMS as an RTOS should provide
On 2014-07-11 04:08, Chris Johns wrote:
On 10/07/2014 11:44 pm, Jennifer Averett wrote:
Use of the cenable command was resulting in a lock in
rtems_interrupt_lock_acquire due to nesting.
I am rejecting this change. RTEMS as an RTOS should provide support to handle
this case in a consistent man
On 10/07/2014 11:44 pm, Jennifer Averett wrote:
Use of the cenable command was resulting in a lock in
rtems_interrupt_lock_acquire due to nesting.
I am rejecting this change. RTEMS as an RTOS should provide support to
handle this case in a consistent manner in SMP and non-SMP builds of the
co
