./prepare-kernel.sh --arch=arm
--adeos=/usr/src/linux/ipipe-core-4.14.36-arm-1.patch
--linux=/usr/src/linux/linux-4.14.36
make menuconfig and I load file in
/usr/src/linux/linux-4.14.36/arch/arm/configs/sama5_defconfig --and save in
/usr/src/linux/linux-4.14.36/.config
make ARCH=arm
On 06/27/2018 08:54 PM, Jeff Melvile wrote:
> Philippe,
>
> Thanks again for all your work on this release.
>
> On Mon, 25 Jun 2018, Philippe Gerum wrote:
>
>>
>> Xenomai 3.0.7 is out [1]. The GIT repository can be cloned from [2].
>>
>> Some GPIO driver updates, several bug fixes in the Cobalt
Philippe,
Thanks again for all your work on this release.
On Mon, 25 Jun 2018, Philippe Gerum wrote:
>
> Xenomai 3.0.7 is out [1]. The GIT repository can be cloned from [2].
>
> Some GPIO driver updates, several bug fixes in the Cobalt core, and a
> critical bug removed from the pshared heap
On 06/27/2018 07:29 PM, Pintu Kumar wrote:
> On Wed, Jun 27, 2018 at 10:47 PM Greg Gallagher wrote:
>>
>> I don't think Beaglebone is supported currently in RTNet.
>>
>
> But I am just checking loopback interface with 127.0.0.1
> I hope that should work on all boards and arch, even without
>
On 06/27/2018 06:17 PM, Jan Kiszka wrote:
> On 2018-06-27 16:12, Pintu Kumar wrote:
>>> With nosmap, that particular issue should no longer occur (at least as
>>> long as we can ask the kernel for this relaxation), so I suspect the
>>> other effect you see now is something else.
>>
>> Just for the
Hi,
I am also planning to submit a talk at ELC-E about Xenomai and my
pratical experience.
However it should be approved first and funded by my company.
If everything goes well, then I will be also interested in this meetup at ELC-E.
Thanks,
Pintu
On Wed, Jun 27, 2018 at 3:39 PM Jan Kiszka
On Wed, Jun 27, 2018 at 10:47 PM Greg Gallagher wrote:
>
> I don't think Beaglebone is supported currently in RTNet.
>
But I am just checking loopback interface with 127.0.0.1
I hope that should work on all boards and arch, even without
installing the net driver.
> On Wed, Jun 27, 2018 at 1:13
This is hikey620 board from hisilicon with 8 cores.
Currently we have resolved this issue by disabling: ACPI, CPU_IDLE,
but enabling CPU_FREQ and changing default CPU governor to userspace.
On Wed, Jun 27, 2018 at 10:31 PM Greg Gallagher wrote:
>
> This is an ipipe issue. CPU4 seems to be
I don't think Beaglebone is supported currently in RTNet.
On Wed, Jun 27, 2018 at 1:13 PM, Pintu Kumar wrote:
> On Wed, Jun 27, 2018 at 9:47 PM Jan Kiszka wrote:
>>
>> On 2018-06-27 16:12, Pintu Kumar wrote:
>> >> With nosmap, that particular issue should no longer occur (at least as
>> >> long
On Wed, Jun 27, 2018 at 9:47 PM Jan Kiszka wrote:
>
> On 2018-06-27 16:12, Pintu Kumar wrote:
> >> With nosmap, that particular issue should no longer occur (at least as
> >> long as we can ask the kernel for this relaxation), so I suspect the
> >> other effect you see now is something else.
> >
This is an ipipe issue. CPU4 seems to be stalled or starved. I'm
doing some RPI3 testing and I haven't seen this yet. Which board is
this? Is it from 96boards with the octacore A53?
-Greg
On Tue, Jun 26, 2018 at 7:56 AM, Pintu Kumar wrote:
> Dear Greg/Philippe,
>
> I am running xeno-test on
On 2018-06-27 16:12, Pintu Kumar wrote:
>> With nosmap, that particular issue should no longer occur (at least as
>> long as we can ask the kernel for this relaxation), so I suspect the
>> other effect you see now is something else.
>
> Just for the information, that issue occurred even on Beagle
On 2018-06-27 17:32, gengdongjiu wrote:
> Hi,
>
> Sorry to disturb you, I want to consult with you two questions:
>
> 1. For the RTnet, do you usually using the witout-RTmac mode or
> with-RTmac mode? From the spec and code, it seems the RTmac is very
> complex and reduce the real-time.
On 06/27/2018 05:30 PM, Radu Rendec wrote:
> On Wed, Jun 27, 2018 at 10:55 AM Philippe Gerum wrote:
>> The only API available from kernel space is RTDM. Since you already have
>> a RTDM driver in place, all you need to do is to expose a read() or
>> ioctl() service to userland, which would wait
Hi,
Sorry to disturb you, I want to consult with you two questions:
1. For the RTnet, do you usually using the witout-RTmac mode or
with-RTmac mode? From the spec and code, it seems the RTmac is very complex
and reduce the real-time.
2. Does the default Xenomai driver supports
On Wed, Jun 27, 2018 at 10:55 AM Philippe Gerum wrote:
> The only API available from kernel space is RTDM. Since you already have
> a RTDM driver in place, all you need to do is to expose a read() or
> ioctl() service to userland, which would wait on rtdm_sem_down to be
> posted by your IRQ
On 06/27/2018 03:52 PM, Radu Rendec wrote:
> Hi all,
>
> I need to port some kernel and application code from Xenomai 2.6 to
> Xenomai 3.0.
>
> The existing code creates a semaphore with sem_open() from the *kernel*
> module init function and posts it with sem_post() from a rtdm interrupt
>
I'm not that familiar with autotools (still learning), but I removed
this from configure.ac :
diff --git a/configure.ac b/configure.ac
index 4f9b1f9..a84dd14 100644
--- a/configure.ac
+++ b/configure.ac
@@ -881,7 +881,6 @@ AC_CONFIG_FILES([ \
testsuite/spitest/Makefile \
> With nosmap, that particular issue should no longer occur (at least as
> long as we can ask the kernel for this relaxation), so I suspect the
> other effect you see now is something else.
Just for the information, that issue occurred even on Beagle bone, and
there is no smap on arm.
However, it
Hi all,
I need to port some kernel and application code from Xenomai 2.6 to
Xenomai 3.0.
The existing code creates a semaphore with sem_open() from the *kernel*
module init function and posts it with sem_post() from a rtdm interrupt
handler (which is also part of the kernel module). The
Hi,
Sorry, but both the below patches are already applied to my xenomai-next repo:
build: link dlopen libs with "nodelete"
smokey/dlopen: fix testcase
Still I am facing dlopen issue.
Is there any other patches I am missing?
Thanks,
Pintu
On Wed, Jun 27, 2018 at 6:47 PM Pintu Kumar wrote:
>
>
Hi,
One doubt, how do we clone 3.0.7 ?
Is it part of the following branches?
remotes/origin/next
remotes/origin/stable/v3.0.x
I could not find any branch with the name 3.0.7.
Is all 3 patches important, or only this is fine:
build: link dlopen libs with "nodelete"
smokey/dlopen: fix
Dear Henning,
Thanks so much for your reply.
I am actually using xenomai-next branch.
With last commit as:
commit ffb68112e2342a62a1f70916a35a3d68e875b12c
Author: Philippe Gerum
Date: Mon May 21 12:54:59 2018 +0200
scripts/prepare-kernel.sh: drop left overs from obsolete ports
Anyways, I
Hi Pintu,
i guess you might be using v3.0.6. There are a couple of commits on top
of that
https://gitlab.denx.de/Xenomai/xenomai/commit/aa008686091484c88cbb809bc190133a98769a30
and 2 parents
All three are in v3.0.7, which hopefully solves your problem.
regards,
Henning
Am Wed, 27 Jun 2018
On 2018-06-27 12:56, Pintu Kumar wrote:
> Dear Jan,
>
>> What means "now"? Did it work before? What was the setup then?
> rtnet loopback test is working (even with older kernel) on my Virtual
> Box with Ubuntu 32-bit.
>
> But it never worked for me on x86_64 machine.
> So, at first I wonder what
The NULL-test is currently performed also in case we assign a
pre-checked value from the master to base_addr. This is harmless, but
the compiler correctly complains about the misaligned code block - or
the missing braces.
Signed-off-by: Jan Kiszka
---
kernel/drivers/can/sja1000/rtcan_adv_pci.c
Dear Jan,
> What means "now"? Did it work before? What was the setup then?
rtnet loopback test is working (even with older kernel) on my Virtual
Box with Ubuntu 32-bit.
But it never worked for me on x86_64 machine.
So, at first I wonder what is the minimum criteria to make rtnet work
on any
Dear Henning,
I saw your commit regarding dlopen here:
https://xenomai.org/pipermail/xenomai/2018-February/038351.html
We are facing dlopen error with xeno-test on arm (beagle bone) and
arm64 (hikey) boards.
Segmentation fault
/usr/xenomai/bin/smokey: test dlopen failed: Unknown error -1
Do you
Hi all,
ELC-E is coming, October 22-24 in Edinburgh, and I've received some
indications that there is interest in having another meetup of the
community. The question is now how broad that interest is and what form
we should head for.
Options:
- BoF at ELC-E (1h, evening session):
- brief
Hi,
With xenomai 3 (but i think the behaviour was the same with xenomai 2),
with loopback enabled, when there is no physical device on the bus, the
following happens :
* the messages fill the internal socket buffers. this result in any
blocking send call actually blocking the caller
* when this
30 matches
Mail list logo
