On Fri, Jan 25, 2013, at 08:06 PM, Michael Haberler wrote:
> In the current code, the only components which start RT threads are motion
> (motmod) and threads
> the only components which stop threads are hal_lib and motmod
>
> they differ as follows:
>
> - unloading 'motmod' stops all threads
Am 26.01.2013 um 02:21 schrieb andy pugh:
> On 26 January 2013 01:06, Michael Haberler wrote:
>
>> I know barely anybody uses the threads module so that's likely safe but I'm
>> raising it more to clarify semantics than to cry wolf.
>
> I use it very often (dozens of invocations a day), howev
On 26 January 2013 01:06, Michael Haberler wrote:
> I know barely anybody uses the threads module so that's likely safe but I'm
> raising it more to clarify semantics than to cry wolf.
I use it very often (dozens of invocations a day), however I would
expect the threads to stop if I unloaded it
In the current code, the only components which start RT threads are motion
(motmod) and threads
the only components which stop threads are hal_lib and motmod
they differ as follows:
- unloading 'motmod' stops all threads
- unloading 'hal_lib' stops all threads
- unloading 'threads' does _not_ st
Gentle persons:
I won't repeat here Bas's analysis of the problem we're having with the
BeagleBone/Ubuntu system.
Here is my minimalist solution which requires no new programming, just a
change in several configuration parameters. Please bear with the longish
message. Because of an abrupt turn
