On 05/17/2018 06:26 AM, Lucky Luo wrote:
Dear xenomai team,
I am an user of xenomai which help me a lot in PTP application, we really
appreciate your contribution on xenomai.
It seems that xenomai 3.0 cannot work on arm64 in Cobalt (dual kernel mode)
currently, will xenomai 3.0 support arm64 i
: image/png
Size: 16729 bytes
Desc: image001.png
URL:
<http://xenomai.org/pipermail/xenomai/attachments/20180517/c086829d/attachment.png>
-- next part --
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 12365 bytes
Desc: image002.png
URL:
ttp://xenomai.org/pipermail/xenomai/attachments/20180517/c086829d/attachment.png>
-- next part --
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 12365 bytes
Desc: image002.png
URL:
<http://xenomai.org/pipermail/xenomai/attachments
On Wed, May 16, 2018 at 07:13:01PM -0700, Dmitriy Cherkasov wrote:
> On Wed, May 16, 2018, at 11:13 AM, Auel, Kendall wrote:
> > I'm trying to build a xenomai-enabled kernel for an arm64 (quad A53
> > cores). Something is not configured correctly, but I haven't been able
> > to get past a stall d
https://github.com/ggallagher31/xenomai-3-alpha-images/blob/master/README.md
Here is the first attempt of Xenomai-3 reference images, this is based
on 4.14 ipipe kernel and the rootfs is a Ubuntu based. Xenomai was
built off the stable-3.0.x branch. The images are currently hosted on
google dri
Hi,
Currently, a user space driver write() API does not clear the number of
interrupts occurred since the last read() API. Instead it disable interrupt
unless a UDD_RTIOC_IRQEN request comes in to enable interrupt. The fact that
ioctl() does support these requests makes write(UDD_RTIOC_IRQEN
