Am 12.12.2016 um 16:55 schrieb Jorge Ramirez:
> On 12/07/2016 01:39 PM, Jan Leupold wrote:
>> All a4l_sbinfo_t are handled in __a4l_fill_desc() as a contiguous array
>> and is stored as data in a4l_root_t. The old code allocated enough
>> memory when the device had at least two subdevices, but miss
On 05/20/2015 11:53 AM, Marco Baracchi wrote:
> We are using kernel *linux 3.0.35*, branch *imx_3.0.35_4.1.0* with
> patches *adeos-xenomai
> 2.6.4* for *mxc* on a freescale imx6 single core and we have a problem
> with hrtimer: sometimes after a couple of hour our periodic task inside
> Xenomai b
On 12/07/2016 01:39 PM, Jan Leupold wrote:
All a4l_sbinfo_t are handled in __a4l_fill_desc() as a contiguous array
and is stored as data in a4l_root_t. The old code allocated enough
memory when the device had at least two subdevices, but missed 8 bytes
(on ARM32), which is the difference between
Am 12.12.2016 um 15:35 schrieb Marco Baracchi:
Sorry I hope this format is more readable
12.12.2016, 15:31, "Marco Baracchi" :
Sorry I hope this is the correct way to add a mail to this thread inside
mailing list:
What you mean with "lost wakeup problem" ?
Ask google, you get many results.
Sorry I hope this format is more readable
12.12.2016, 15:31, "Marco Baracchi" :
> Sorry I hope this is the correct way to add a mail to this thread inside
> mailing list:
>
> What you mean with "lost wakeup problem" ?
>
> What we are checking is a timer tick missing:
>
> root@deimo-staubli ~$ cat
Sorry I hope this is the correct way to add a mail to this thread
inside mailing list:
Â
What you mean with "lost wakeup problem" ?
Â
What we are checking is a timer tick missing:
Â
root@deimo-staubli ~$ cat /proc/timer_list
Timer List Version: v0.6
HRTIMER_MAX
In the pSOS interface region 0 can be used by applications to allocate
memory from. It contains 'system' memory and is created by default during
system init. Region 0 is currently not supported by the xenomai psos skin.
This patch adds functionality to configure the total size and the unit
size by
This patch introduces a tunable in the mercury copperplate code that allows
to put an upper limit on the priority used by the created thread objects.
Before this patch the complete OS scheduler's FIFO range was used and it was
not possible to restrict it. Restricting it can be useful in case other
Am 09.12.2016 um 23:42 schrieb Marco:
We are notice a very strange problem on a imx6 with kernel
Linux3.0.35-4.1.0 + xenomai_2.6.4. After machine runs for 8 - 10 hours
we found the system blocked in may different ways (user interface
tcp/ip interface ecc..)
Â
We check in
