On 04/12/2018 07:56 PM, Steve Freyder wrote:
> On 4/12/2018 11:05 AM, Philippe Gerum wrote:
>> On 04/12/2018 05:44 PM, Steve Freyder wrote:
>>> On 4/12/2018 5:23 AM, Philippe Gerum wrote:
On 04/12/2018 11:31 AM, Philippe Gerum wrote:
> On 04/09/2018 01:01 AM, Steve Freyder wrote:
>> On
Hi, everyone
I am trying the posix skin under xenomai 2.6.4 with the Linux kernel 3.14.17.
I created a thread and try to make it periodic, but the
pthread_make_periodic_np failed with ESRCH which indicates that the thread is
invalid. This is impossible since the print work of thread cont
On 4/12/2018 11:05 AM, Philippe Gerum wrote:
On 04/12/2018 05:44 PM, Steve Freyder wrote:
On 4/12/2018 5:23 AM, Philippe Gerum wrote:
On 04/12/2018 11:31 AM, Philippe Gerum wrote:
On 04/09/2018 01:01 AM, Steve Freyder wrote:
On 4/2/2018 11:51 AM, Philippe Gerum wrote:
On 04/02/2018 06:11 PM,
On 04/12/2018 05:44 PM, Steve Freyder wrote:
> On 4/12/2018 5:23 AM, Philippe Gerum wrote:
>> On 04/12/2018 11:31 AM, Philippe Gerum wrote:
>>> On 04/09/2018 01:01 AM, Steve Freyder wrote:
On 4/2/2018 11:51 AM, Philippe Gerum wrote:
> On 04/02/2018 06:11 PM, Steve Freyder wrote:
>> On
On 4/12/2018 5:23 AM, Philippe Gerum wrote:
On 04/12/2018 11:31 AM, Philippe Gerum wrote:
On 04/09/2018 01:01 AM, Steve Freyder wrote:
On 4/2/2018 11:51 AM, Philippe Gerum wrote:
On 04/02/2018 06:11 PM, Steve Freyder wrote:
On 4/2/2018 10:20 AM, Philippe Gerum wrote:
On 04/02/2018 04:54 PM,
Hi,
I have created my own latency tests program to measure latency using
Xenomai API for some use cases.
Now, I have a requirement to plot the latency difference in the form of graph.
I tried cyclictest and gluplot, with my sample program running in back
ground to capture latency information.
But
On Thu, Apr 12, 2018 at 11:56:20AM +0530, Pintu Kumar wrote:
> In BeagleBone there is no direct serial interface available.
> However, we use Serial over USB (ttyUSB0) to connect to minicom.
> In this case it is possible to use this interface over Xenomai and
> check latency improvement?
I thought
Ports UART1, UART2, UART4, UART5 are available on the BeagleBone's P8 and P9,
and UART0 is on the debugging header. UART3 is also available, but only the TX
line I think.
These can be accessed through the linux driver at `/dev/ttyS0`...`/dev/ttyS5`
Additionally, you have uart0 from the PRUSS.
S
I thought the header contained outputs for the UART? The driver will control
interfaces for the serial chip, ttyUSB0 probably won't be included in that.
What type of device are you sending data to over serial?
Greg
Original Message
From: pintu.p...@gmail.com
Sent: April 12, 2018 2:26 AM
To
On 04/12/2018 11:31 AM, Philippe Gerum wrote:
> On 04/09/2018 01:01 AM, Steve Freyder wrote:
>> On 4/2/2018 11:51 AM, Philippe Gerum wrote:
>>> On 04/02/2018 06:11 PM, Steve Freyder wrote:
On 4/2/2018 10:20 AM, Philippe Gerum wrote:
> On 04/02/2018 04:54 PM, Steve Freyder wrote:
>> On
On 04/09/2018 01:01 AM, Steve Freyder wrote:
> On 4/2/2018 11:51 AM, Philippe Gerum wrote:
>> On 04/02/2018 06:11 PM, Steve Freyder wrote:
>>> On 4/2/2018 10:20 AM, Philippe Gerum wrote:
On 04/02/2018 04:54 PM, Steve Freyder wrote:
> On 4/2/2018 8:41 AM, Philippe Gerum wrote:
>> On 04/
On 2018-04-12 11:03, Philippe Gerum wrote:
> On 04/11/2018 01:11 PM, Jan Kiszka wrote:
>> Hi Philippe,
>>
>> many users of the hash functions prefer (and actually have to) call
>> those services under an external lock to close race windows, e.g.
>> between lookup and entry usage. Still, those servi
On 04/11/2018 01:11 PM, Jan Kiszka wrote:
> Hi Philippe,
>
> many users of the hash functions prefer (and actually have to) call
> those services under an external lock to close race windows, e.g.
> between lookup and entry usage. Still, those services come with their
> own, internal lock. That se
It's not really safe to allow a potentially modifying operation to be
canceled in the middle, just dropping the lock during rollback. Better
defer cancellation until the lock is dropped.
Signed-off-by: Jan Kiszka
---
lib/boilerplate/hash.c | 10 ++
1 file changed, 6 insertions(+), 4 dele
On 04/10/2018 09:03 PM, Pham, Phong wrote:
>
> Hi,
>
> According to page 651
> https://xenomai.org/documentation/xenomai-3/pdf/xeno3prm.pdf
>
>
> This will make such region accessible via the mapper device using the
> following sequence of code, via
> the default ->mmap() handler from the UDD
This reverts commit 0f19393b3702705c8470147b6a3fd03a08b42642.
No reason was given back then, and we there is the risk that this code
is used by prio-sensitive threads. Moreover, pvhash still used PI -
unless it is mapped on plain hash in case of !CONFIG_XENO_PSHARED.
Signed-off-by: Jan Kiszka
--
16 matches
Mail list logo