[Xenomai] Gpio-core question

Hi, I'm finishing up my work on a patch to add a RTDM gpio driver for the zynq-7000 platform. I ran into a situation where I needed to call gpio_request in gpio-core because the zynq gpio driver uses the gpio_request function to enable the gpio pins on the board. A side effect that I found

Re: [Xenomai] [RFC] RTnet, Analogy and the elephant in the room

I really like the idea of having some TODO files, this would given new comers to the project a place to start. Improving the documentation and adding a quick start guide might help get more people interested in using Xenomai. With more users hopefully that would lead to more contributors and

Re: [Xenomai] matching patch version to kernel version

Hi, In my experience I usually try to get the patch that is the closest match to my kernel version. So I would try ipipe-core-4.9.51-x86-4.patch, you will probably have to do some hand fixes to resolve any conflicts if the patch doesn't apply cleanly. That's usually how I approach it. There

Re: [Xenomai] Gpio-core question

Sure sounds good, I'll start tonight.   Original Message   From: r...@xenomai.org Sent: November 30, 2017 3:50 AM To: g...@embeddedgreg.com; xenomai@xenomai.org Subject: Re: [Xenomai] Gpio-core question On 11/29/2017 09:40 PM, Greg Gallagher wrote: > Hi, >   Sorry for the formatting in th

Re: [Xenomai] Gpio-core question

ght. If this is what is happening should the fd be removed from the tree in cleanup_instance? I can play around with xnid_remove and see if working it into cleanup_instance will solve the issue. -Greg On Wed, Nov 29, 2017 at 2:10 AM, Greg Gallagher <g...@embeddedgreg.com> wrote: > Hi, > I was

Re: [Xenomai] Xenomai on Arm64

What kernel are you using L4T or mainline? Sent from my BlackBerry - the most secure mobile device - via the Rogers Network   Original Message   From: yuboch...@live.cn Sent: December 17, 2017 9:44 AM To: xenomai@xenomai.org Subject: [Xenomai] Xenomai on Arm64 Hi, I'm trying to patch Xenomai

Re: [Xenomai] Xenomai on Arm64

I believe Arm64 is only in the next branch, but i'll leave that to someone else to confirm or correct. Greg   Original Message   From: g...@embeddedgreg.com Sent: December 17, 2017 10:24 AM To: yuboch...@live.cn; xenomai@xenomai.org Subject: Re: [Xenomai] Xenomai on Arm64 What kernel are you

Re: [Xenomai] (no subject)

How did you install it in the first place? What platform are you using? X86, arm, ppc??   Original Message   From: samiraelmada...@gmail.com Sent: December 17, 2017 11:49 AM To: xenomai@xenomai.org Subject: [Xenomai] (no subject) please to uninstall xenomai or reconfigure it ,because it sounds

Re: [Xenomai] Xenomai on Arm64

__ From: Greg Gallagher <[1]g...@embeddedgreg.com> Sent: Sunday, December 17, 2017 10:24 To: ?? ?; [2]xenomai@xenomai.org Subject: Re: [Xenomai] Xenomai on Arm64 What kernel are you using L4T or mainline? Sent from my BlackBerry - the most secure mobile device

[Xenomai] rt_imx_uart

Hi, I looked into why this driver isn't compiling, basically it needs to be brought up to match the newer imx serial driver. It's relying on files and structures that existed in earlier versions of the kernel before a reorganization happened (around 3.18 I think). I have access to a i.mx6

Re: [Xenomai] rt-fprintf problem

You'll have to be more specific then "it didn't work", is it possible to post some code so we can see what you are trying to do? -Greg On Mon, Dec 18, 2017 at 7:12 PM, rajae rajae wrote: > Hello everyone please I have a question about rt-fprontf it didn't work >

Re: [Xenomai] Cobalt core and Yocto

Others might be able to give a more concrete answer, but usually I check for the existence of /proc/xenomai as a very quick test. You can also run the autotune script and check that there are no errors in the output. If this is meant to be a smoke test it may worth while to run the autotune

[Xenomai] Contributing to Xenomai

Hi, I'm preparing a patch to enable RTDM gpio for the Xilinx Zynq 7000 platform. First, is this something that would be of value to add to mainline Xenomai? I noticed there is a rtdm gpio driver for the bcm2835 (raspberry pi) and figured it may be nice for Zynq users to have a rtdm gpio driver

Re: [Xenomai] [RFC] RTnet, Analogy and the elephant in the room

Hi, I've been using Xenomai for a couple of years now and having been preparing my first patch. I'd love to help any way that is needed. Documentation may be a good place for me to start. I'd also be more than happy to help maintain some of the I/O frameworks. I would probably need a mentor

[Xenomai] [PATCH] Add How To Contribute Guide

--- How_To_Contribute.adoc | 57 ++ 1 file changed, 57 insertions(+) create mode 100644 How_To_Contribute.adoc diff --git a/How_To_Contribute.adoc b/How_To_Contribute.adoc new file mode 100644 index 000..60c366f --- /dev/null +++

[Xenomai] [PATCH] Split rtdm_fd_enter up, move the functionality where we store the fd until after the open() call succeeds. Calls where open() fail a fd is left in the tree even after the cleanup cod

--- include/cobalt/kernel/rtdm/fd.h | 2 ++ kernel/cobalt/posix/mqueue.c| 7 ++- kernel/cobalt/posix/timerfd.c | 4 kernel/cobalt/rtdm/core.c | 12 +--- kernel/cobalt/rtdm/fd.c | 24 5 files changed, 37 insertions(+), 12

[Xenomai] [PATCH] Add zynq-7000 rtdm gpio driver.

From: Greg Gallagher <ggallaghe...@gmail.com> --- For the zynq platform (and possibly others in the future) we need to modify gpio-core to request gpio pins before using them. The open() function will now request a gpio and fail if it's already reserved. This should make the pin r

[Xenomai] [PATCH] Split rtdm_fd_enter up

--- split rtdm_fd_enter, move the functionality where we store the fd until after the open() call succeeds. Calls where open() fail a fd is left in the tree even after the cleanup code is executed. If this fd number is used again we will fail the call to open until a different fd is used.

[Xenomai] Contributing Doc

Hi, I'm putting together a doc on how to contribute. I've pasted it below, if anyone has some time to review and let me know what I've missed that would be great. I wasn't sure if all development should take place against the next branch or not. I'm also not sure if I linked the documents

[Xenomai] [PATCH] Fix up name collision, debug is already defined

--- When compiling for x86 and enabling experimental intel net drivers I ran into a compilation error where debug was defined previously. Rename the debug variable to avoid the collision. --- kernel/drivers/net/drivers/experimental/e1000/e1000_main.c | 8 1 file changed, 4

Re: [Xenomai] Xenomai porting for proprietary drivers

It's possible to port proprietary drivers, but the license is the same as the Linux kernel. Which means you must comply with the GPL license. Greg   Original Message   From: pintu.p...@gmail.com Sent: May 7, 2018 6:16 AM To: xenomai@xenomai.org Subject: [Xenomai] Xenomai porting for

Re: [Xenomai] RPi zero: high resolution clock not working

Hi, To the best of my knowledge for raspberry pi zero you should be using the bcm2835_defconfig for mainline. I was working on this last month when I had a little more time. There are a couple things missing right now for Xenomai-3 (Cobalt) to work on the bcm2835 based pis. Most of it has to

Re: [Xenomai] RPI, pinctrl-bcm2835 now working

pinctrl-bcm2835 driver on your RPi2? Regards Gustav From: Greg Gallagher <g...@embeddedgreg.com> Sent: 24 April 2018 15:34 To: Gustav Johansson Cc: Xenomai@xenomai.org Subject: Re: [Xenomai] Illegal instruction/bad syscall Have you considered using ma

Re: [Xenomai] [SPAM] Re: Issue with Xenomai 3.0.6, I-Pipe 4.9.51 and Linux 4.9.51 on Xilinx Zynq 7000 MPSOC

I'll update my how-to this weekend and post my prebuilt images. I just need to make time to look into the 4.9.51 lock up. I'll post here with links once things are ready. Greg   Original Message   From: jeff.w...@nta-inc.net Sent: April 27, 2018 10:21 AM To: xenomai@xenomai.org Subject: Re:

Re: [Xenomai] RTDM serial illicit call from head domain 'Xenomai'

n running > kernels with this debug capability enabled, so I've never seen this before > and we have never had any issues with it at all so that tends to suggest > this > is truly benign for these specific code paths. > > Thanks Greg, > Steve > > > > > On 5/12/2018

Re: [Xenomai] RTDM serial illicit call from head domain 'Xenomai'

I'll try to answer part of this. The detection of a cross domain call would come form the ipipe code in the kernel. This is being called because the ipipe debug flags are on and it's detecting the switch from the root domain and then causing a panic so we can see the stack trace. I'm not sure why

Re: [Xenomai] RTDM serial illicit call from head domain 'Xenomai'

Subject: Re: [Xenomai] RTDM serial illicit call from head domain 'Xenomai' On 05/13/2018 07:02 AM, Greg Gallagher wrote: > I won't say the driver is improperly written, this ioctl call may not > be expected to be used in a low latency situation.  Some code maybe > expected to

Re: [Xenomai] Xddp and socket: Address family not supported by protocol

Do you have the module loaded or enabled in the kernel?   Original Message   From: libin.z...@envisioncn.com Sent: May 17, 2018 9:13 AM To: xenomai@xenomai.org Subject: Re: [Xenomai] Xddp and socket: Address family not supported by protocol Hi, Now,I install Xenomai-3.3 In Ubuntu

Re: [Xenomai] Boot failed on arm64 - xenomai_init --> ipipe_send_ipi

HI, What ipipe and kernel version are you using and what Xenomai branch are you using? -Greg On Wed, May 16, 2018 at 2:13 PM, Auel, Kendall wrote: > I'm trying to build a xenomai-enabled kernel for an arm64 (quad A53 cores). > Something is not configured

Re: [Xenomai] RPi zero: high resolution clock not working

I have the ipipe support for the bcm2835 done, I'll submit the patch shortly. Once that's in the ipipe-arm tree we can start building xenomai for the rpi zero. On Wed, May 9, 2018 at 8:50 AM, Gustav Johansson wrote: > Hi! > > > I have managed to boot RPI zero with Cobalt on

[Xenomai] Reference Images Alpha Release

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

Re: [Xenomai] Boot failed on arm64 - xenomai_init --> ipipe_send_ipi

I know Philippe put a change into the arm 32-bit ipipe for the new gic in the imx7d which was causing a lock up. I'm not sure if this is a similar thing. -Greg On Wed, May 16, 2018 at 4:00 PM, Auel, Kendall wrote: > Greg, > > The kernel is 4.9.51, modified by NXP

Re: [Xenomai] Only 2 serial ports at a time with xeno_16550A driver

This is highly likely, I'm not sure when this driver was last tested. Are you able to put a patch together? Has anyone else sense similar behaviour? -Greg On Tue, May 22, 2018 at 2:31 PM, C Smith wrote: > I think I may have found a bug in the rtl_16550A driver when

Re: [Xenomai] INTR-REMAP issue while enabling GPIO interrupt as RTDM interrupt

I'm probably not much help but something similar was on the list a while ago: https://xenomai.org/pipermail/xenomai/2017-November/038014.html On Thu, Jun 7, 2018 at 11:55 AM, Yan, Hongliang wrote: > Hi All, > I am trying to enable pinctrl-intel.c GPIO interrupt as RTDM interrupt. I > use

Re: [Xenomai] ipipe-4.4.y LTS

Are there still plans to have a ipipe patch for the CIP kernel? I think this was brought up at the last meet up? Maybe the bigger question (which is a lot more work) is do we plan on maintaining ipipe for 4.4, 4.9 and older? -Greg On Mon, Jun 18, 2018 at 8:52 AM, Radu Rendec wrote: > Hi all,

Re: [Xenomai] rpi3 - very high negative latency for simple xeno task

Hi Pintu, I just started doing some work recently with the RPI3 to see how Xenomai performs, but I haven't made it too far at the moment. How did you tune the system? -Greg On Sun, Jun 17, 2018 at 10:07 AM, Pintu Kumar wrote: > Dear Greg, > > Do you have any comment about this? > On Wed,

Re: [Xenomai] xenomai modules - xeno_rtdm, xeno_hal, xeno_nucleus. not getting installed

Did you turn them on in menuconfig when you built your kernel? -Greg On Mon, Jun 18, 2018 at 1:40 AM, Ashok kumar wrote: > Hi, > > I have patched xenomai -2.6.4 with linux 3.18.20 . > and installed the patched kernel, and compiled the xenomai library using > below > commands > > cd /usr/src >

Re: [Xenomai] how to install the following modules xeno_rtdm xeno_hal xeno_nucleus to use RTnet

Do you have the modules enabled in the CONFIG? How are you configuring your kernel? -Greg On Wed, Jun 13, 2018 at 1:06 AM, Ashok kumar wrote: > Hi, > > I am using xenomai -2.6.2.1 and I have patched the xenomai -2.6.2.1 > with linux kernel 3.4.6 > and I installed using the following commands >

Re: [Xenomai] How to print to dmesg buffer from an RT task

You can try to write to /dev/kmsg, but this is a Linux resource so it will impact which domain your thread is running on. AFAIK user space tasks shouldn't be logging to the kernel log for the most part. One solution I've seen is to create a driver (in your case RTDM driver) to take in log

Re: [Xenomai] xenomai modules - xeno_rtdm, xeno_hal, xeno_nucleus. not getting installed

architecture. > > Thank you > > > On Tue, Jun 19, 2018 at 11:11 PM, Greg Gallagher > wrote: >> You won't need them for Xenomai-3 if you aren't using things like >> rtnet, ipc or any driver that can be found in the Xenomai tree. Are >> you using a Debian system? Th

Re: [Xenomai] xenomai modules - xeno_rtdm, xeno_hal, xeno_nucleus. not getting installed

ve turned modules ON, I have attached the enable modules section > in the kernel configuration > > thank you > R.Ashokkumar > > > > On Mon, Jun 18, 2018 at 7:30 PM, Greg Gallagher wrote: >> Did you turn them on in menuconfig when you built your kernel? >> >>

Re: [Xenomai] xenomai modules - xeno_rtdm, xeno_hal, xeno_nucleus. not getting installed

nagement and ACPI options -- turn off CPU idle PM support. >>> # 5. Kernel hacking turn off KGDB: kernel debugger. >>> # 6. Turn off Virtualization. >>> # 7. Make appropriate changes to Real-time sub-system. >>> # 8. Device Drivers -> IOMMU Hardware Support -- t

Re: [Xenomai] xenomai modules - xeno_rtdm, xeno_hal, xeno_nucleus. not getting installed

, 2018 at 11:29 AM, Ashok kumar wrote: > Hi, > > I am getting xeno_rtdm.o,xeno_hal.o,xeno_nucleus.o. file but I am not > getting xeno_rtdm.ko, xeno_hal.ko, xeno_nucleus.ko > > I should get .ko file to load it in kernel module . > > Thank you > > > On Tue, Jun 19

Re: [Xenomai] xenomai modules - xeno_rtdm, xeno_hal, xeno_nucleus. not getting installed

turns 6, set as Generic otherwise) > * Power management and ACPI options > --> Memory power savings > --> Intel chipset idle memory power saving driver (Disable) > and in nucleus I have seleted RTDM drivers, in interfaces,drivers etc > > and I am using x86_64 proce

Re: [Xenomai] xenomai modules - xeno_rtdm, xeno_hal, xeno_nucleus. not getting installed

mai-2.6.4 , > in this folder I am able to get xeno_rtdm.o,xeno_hal.o,xeno_nucleus.o. > some where in arch , drivers, kernel directory , but I am not able to get > xeno_rtdm.ko,xeno_hal.ko,xeno_nucleus.ko, > > > > > On Tue, Jun 19, 2018 at 9:56 PM, Greg Gallagher wrote: >> When y

Re: [Xenomai] xenomai modules - xeno_rtdm, xeno_hal, xeno_nucleus. not getting installed

mand can you please provide me >> to how to build xenomai -3 in x86_64 architecture. >> >> to get the modules xeno_rtdm.ko,xeno_hal.ko,xeno_nucleus.ko. >> >> >> >> On Tue, Jun 19, 2018 at 10:24 PM, Greg Gallagher >> wrote: >>> Look at

Re: [Xenomai] xenomai modules - xeno_rtdm, xeno_hal, xeno_nucleus. not getting installed

k kumar >> wrote: >>> in my lib/module/ >>> >>> I am able to get this folder 3.14.17-xenomai-2.6.4 , >>> in this folder I am able to get xeno_rtdm.o,xeno_hal.o,xeno_nucleus.o. >>> some where in arch , drivers, kernel directory , but I am not able to

Re: [Xenomai] Reference Images Alpha Release

:46, Greg Gallagher wrote: >> I agree, after the first run of building the images myself I think >> having the user generate the images would make more sense. I'm >> looking into doing that with an existing tool I think yocto may be a >> good choice. I've been generating

Re: [Xenomai] Reference Images Alpha Release

the work to bring the bcm2835 to the 4.14 ipipe so it looks like we should be able to try more raspberry pi builds. -Greg On Wed, May 30, 2018 at 10:03 AM, Jan Kiszka wrote: > On 2018-05-18 04:00, Greg Gallagher wrote: >> https://github.com/ggallagher31/xenomai-3-alpha-images/blob/master/

Re: [Xenomai] xenomai 3.0.6 on RPi3 overheating when idle

I haven't tested Xenomai on RPI3 in 32-bit mode, I think someone else tried it a while ago with out using Yocto and may be able to share his experiences (Gustav?). I haven't seen this issue on Raspberry pi 2b. You can take a look at the output of ps and see if anything is using a lot of the CPU.

Re: [Xenomai] ipipe 4.14 for ARM and X86

I think there's still some ongoing work in both ARM and x86, Philippe and Jan may be able to comment more on the timeline. You can directly clone the ipipe-arm tree and evaluate if it would work on your platform. There are still some issues with beaglebone/beagleboard in 4.14 that I'm looking

Re: [Xenomai] beaglebone: arm: xeno-test gives segmentation fault - test dlopen failed

Hi, I'll take a look at this tonight. I'll confirm if this test is crashing on all platforms or just BB. To disable I believe you'll have to recompile the tests. -Greg On Tue, Jun 26, 2018 at 10:43 AM, Pintu Kumar wrote: > Dear Greg, > > Please let me know how to disable "dlopen" test in

Re: [Xenomai] beaglebone: arm: xeno-test gives segmentation fault - test dlopen failed

> > > So, please let us know how to disable dlopen test to pass the >> > > > xeno-test report. >> > > > >> > > > >> > > > Thanks, >> > > > Pintu >> > > > >> > > > >> > > >

Re: [Xenomai] KERNEL OOPS : hikey620: arm64 - while xecuting xeno-test

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

Re: [Xenomai] Kernel oops during rtnet loopback usage on x86_64 (e1000e)

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

Re: [Xenomai] ipipe-4.4.y LTS

I can run some tests on ARM boards I have. -Greg On Tue, Jun 19, 2018 at 3:09 AM, Jan Kiszka wrote: > On 2018-06-18 15:59, Greg Gallagher wrote: >> Are there still plans to have a ipipe patch for the CIP kernel? I >> think this was brought up at the last meet up? Maybe the big

Re: [Xenomai] how to bring gpio to user space

It looks like you are calling rtdm_dev_register twice, so the second one complains that it already exists. Take out the second call and see what happens. // rtdm_sem_init(, 0);// init the global semaphore rtdm_printk("gpio TRY register Driver \n"); err=rtdm_dev_register(); if

Re: [Xenomai] how to bring gpio to user space

сотрудничество, > Шевченко Т.Г. > > - Исходное сообщение ----- > От: "Greg Gallagher" <g...@embeddedgreg.com> > Кому: "Шевченко Тарас Григорьевич" <shevchenko.ta...@triolcorp.com.ua> > Копия: "xenomai" <xenomai@xenomai.org>, "Olej

Re: [Xenomai] Issue with Xenomai 3.0.6, I-Pipe 4.9.51 and Linux 4.9.51 on Xilinx Zynq 7000 MPSOC

git clone git://git.xenomai.org/xenomai-3.git git checkout stable-3.0.x When was the last time you sync'd with the Linux stable tree? On Thu, Apr 26, 2018 at 12:39 PM, Salvatore Barone <salvator.bar...@gmail.com> wrote: > Which repo sould I use? > > > 2018-04-26 18:35 GMT+02:00

Re: [Xenomai] Issue with Xenomai 3.0.6, I-Pipe 4.9.51 and Linux 4.9.51 on Xilinx Zynq 7000 MPSOC

g...@embeddedgreg.com >> *Cc:* xenomai@xenomai.org >> *Subject:* Re: [Xenomai] Issue with Xenomai 3.0.6, I-Pipe 4.9.51 and >> Linux 4.9.51 on Xilinx Zynq 7000 MPSOC >> >> Hi Greg! I've read all your blog post on this argument! With the xilinz >> li

Re: [Xenomai] Issue with Xenomai 3.0.6, I-Pipe 4.9.51 and Linux 4.9.51 on Xilinx Zynq 7000 MPSOC

.9.51 I-Pipe patch and get > Xenomai working on it? > > 2018-04-26 18:56 GMT+02:00 Greg Gallagher <g...@embeddedgreg.com>: >> >> okay, I will try to reproduce tonight. If you need to be up and >> running i can send you a 4.14 image, (4.14 kernel with Ubuntu 16.04 >>

Re: [Xenomai] Issue with Xenomai 3.0.6, I-Pipe 4.9.51 and Linux 4.9.51 on Xilinx Zynq 7000 MPSOC

Sounds good, and I will test out the 4.9.51 patch tonight and see what happens. On Thu, Apr 26, 2018 at 1:05 PM, Salvatore Barone <salvator.bar...@gmail.com> wrote: > Ok, I'll try. > > I keep you updated > Thanks a lot! > > 2018-04-26 19:02 GMT+02:00 Greg Gallaghe

Re: [Xenomai] Issue with Xenomai 3.0.6, I-Pipe 4.9.51 and Linux 4.9.51 on Xilinx Zynq 7000 MPSOC

and Linux 4.9.51 on Xilinx Zynq 7000 MPSOC Hi Greg! I've read all your blog post on this argument! With the xilinz linux kernel i have no problem! Saluti, Salvatore Barone. Il Gio 26 Apr 2018, 16:25 Greg Gallagher <[1]g...@embeddedgreg.com> ha scritto: If you load

Re: [Xenomai] Issue with Xenomai 3.0.6, I-Pipe 4.9.51 and Linux 4.9.51 on Xilinx Zynq 7000 MPSOC

hours ago... > > 2018-04-26 18:43 GMT+02:00 Greg Gallagher <g...@embeddedgreg.com>: >> >> git clone git://git.xenomai.org/xenomai-3.git >> git checkout stable-3.0.x >> >> When was the last time you sync'd with the Linux stable tree? >> >> On T

Re: [Xenomai] Shared memory between RT and NRT tasks (Posix Skin)

Have you considered using xddp sockets instead? How large is the memory you are sharing? -Greg On Thu, May 3, 2018 at 1:49 PM, Virendra Kate wrote: > Hello, > > I am trying to create a shared memory between a RT (Cobalt) and a NRT > (Linux) task. I went through the " A

Re: [Xenomai] Shared memory between RT and NRT tasks (Posix Skin)

ory is 16MB big. > > -Virendra > > On Thu, May 3, 2018 at 10:51 AM, Greg Gallagher <g...@embeddedgreg.com> wrote: >> Have you considered using xddp sockets instead? How large is the >> memory you are sharing? >> >> -Greg >> >> On Thu, May 3, 201

[Xenomai] [PATCH] Fix up the imx uart driver so it now compiles with new kernels.

bruary/035924.html Fixed up kernel style errors and I added a couple small changes and tested on a imx7d board. One quick note, the IMX7D define may not really be needed since most imx7 uarts look to be compatible with imx6. Signed-off-by: Greg Gallagher <g...@embeddedgreg.com> --- ke

[Xenomai] [PATCH] Fix up the imx uart driver so it now compiles with new kernels.

--- kernel/drivers/serial/rt_imx_uart.c | 299 1 file changed, 204 insertions(+), 95 deletions(-) diff --git a/kernel/drivers/serial/rt_imx_uart.c b/kernel/drivers/serial/rt_imx_uart.c index 092cecc..db63df6 100644 --- a/kernel/drivers/serial/rt_imx_uart.c

[Xenomai] [PATCH] Fix up the imx uart driver so it now compiles with new kernels.

035924.html Fixed up kernel style errors and I added a couple small changes and tested on a imx7d board. One quick note, the IMX7D define may not really be needed since most imx7 uarts look to be compatible with imx6. Signed-off-by: Greg Gallagher <g...@embeddedgreg.com> --- kernel/dr

Re: [Xenomai] [PATCH] Fix up the imx uart driver so it now compiles with new kernels.

at 3:09 PM, Greg Gallagher <g...@embeddedgreg.com> wrote: > > From: Michael Welling <mwell...@ieee.org> > > This patch is based on one that was submitted by Michael Welling back in Feb > 2016 but a formal patch was never submitted.  The original thread that this > pat

Re: [Xenomai] [PATCH] Fix up the imx uart driver so it now compiles with new kernels.

at the bottom. Let me know if I missed anything. Thanks Greg On Mon, Jan 8, 2018 at 1:03 PM, Jan Kiszka <jan.kis...@siemens.com> wrote: > On 2018-01-08 18:52, Greg Gallagher wrote: >> Hi, >> The patch I submitted was based on one that was submitted by Wolfgang >>

Re: [Xenomai] [PATCH] Fix up the imx uart driver so it now compiles with new kernels.

put this info in the patch as well. -Greg On Mon, Jan 8, 2018 at 12:49 PM, Greg Gallagher <g...@embeddedgreg.com> wrote: > --- > kernel/drivers/serial/rt_imx_uart.c | 299 > > 1 file changed, 204 insertions(+), 95 deletions(-) > > dif

Re: [Xenomai] heap allocation working for some memory sizes but not others

ces "OK" for some memory size, same > values as when using H_SHARE) > - I compiled the tests, and heap-1 / heap-2 run ok > > Best > > Vincent > > > > On 10.01.2018 23:38, Greg Gallagher wrote: >> >> Hi, >> >> You may want to look at this

Re: [Xenomai] Xenomai 3.0.6 - ipipe-3.18.20 - kernel build error

Hi, Can you post more information on how you are building the patched kernel? I'm assuming you are building for x86_64? Thanks Greg On Wed, Jan 10, 2018 at 11:16 AM, Fazio Maurizio wrote: > Hello, > I have some problems in building the 3.18.20 stable

Re: [Xenomai] heap allocation working for some memory sizes but not others

Hi, You may want to look at this test for help: https://git.xenomai.org/xenomai-3.git/tree/lib/alchemy/testsuite/heap-1.c I think you should have rt_heap_bind after your call to rt_heap_create, if you switch the timeout flag in rt_heap_bind to TM_INFINITE I think you should see your program

Re: [Xenomai] Xenomai community meeting 02.02.18

I'll definitely attend via TelCo.   Original Message   From: henning.sch...@siemens.com Sent: January 9, 2018 6:22 AM To: r...@xenomai.org; jan.kis...@siemens.com; sance...@numalliance.com; j...@xenomai.org; s...@hilscher.com; g.m...@qmul.ac.uk; steven.see...@nasa.gov; l...@alaxarxa.net;

Re: [Xenomai] [RFC] FOSDEM meeting agenda

We can add an ELC meeting ;) On Fri, Jan 26, 2018 at 1:49 PM, Jan Kiszka wrote: > On 2018-01-25 18:40, Philippe Gerum wrote: >> >> Here are some points I would like to discuss during this meeting. Please >> feel free to comment: >> >> 1. Release management >> >> *

Re: [Xenomai] [RFC] FOSDEM meeting agenda

it will be interesting. I'm up for anything Xenomai, I'll be getting there late Sunday and leaving around 6pm Wednesday. -Greg On Fri, Jan 26, 2018 at 1:57 PM, Jan Kiszka <jan.kis...@siemens.com> wrote: > On 2018-01-26 19:51, Greg Gallagher wrote: >> We can add an ELC meeting ;) >&g

Re: [Xenomai] [RFC] FOSDEM meeting agenda

Sounds good to me, I can send out a reminder to the list the week before the conference. On Fri, Jan 26, 2018 at 2:34 PM, Jan Kiszka <jan.kis...@siemens.com> wrote: > On 2018-01-26 20:02, Greg Gallagher wrote: >> That would be great, I booked my flights and hotel this morning

[Xenomai] meeting agenda suggestions

Adding some points that I think need some attention at the meeting. Drivers: Currently we have support for certain boards, SOC families and devices. Do we want to expand on that? Are there commonly used pieces of hardware that we want to add support for? For most devices it may be a port

Re: [Xenomai] ipipe: kernel updates in the light of recent fixes (meltdown...)

I think using the CIP kernel would be a great idea. I can see this being popular with product developers. -Greg On Tue, Jan 23, 2018 at 12:52 PM, Jan Kiszka wrote: > Hi Philippe, > > as the number of question increase here, but I bet elsewhere as well, > and I'm

Re: [Xenomai] Writing to UDD driver through mapped memory cause secondary mode switch

Sorry to bring back an old thread but I just noticed this. Did you solve your issue? Did you use the documentation in this file for help? https://git.xenomai.org/xenomai-3.git/tree/include/cobalt/kernel/rtdm/udd.h?id=f4a54b173db71a182d9826852a94b20f6095b411 -Greg On Thu, Dec 14, 2017 at 6:23

Re: [Xenomai] R: R: Xenomai 3.0.6 high latency

Hi, I configured a xenomai 3 system on a x86 i7 not too long ago, I got really got latency results. Here is what I did when I configured my system: Menu config options: * Power management and ACPI options --> CPU Frequency scaling --> CPU Frequency scaling (Disable) --> ACPI (Advanced

[Xenomai] [PATCH] Fix up the imx uart driver so it now compiles with new kernels.

to be compatible with imx6. The original thread that this patch was derived from is located here: https://xenomai.org/pipermail/xenomai/2016-February/035924.html Signed-off-by: Greg Gallagher <g...@embeddedgreg.com> --- kernel/drivers/serial/rt_imx_uart.c

[Xenomai] [PATCH 1/3] Add Xilinx AXI gpio driver

new file mode 100644 index 000..72d4364 --- /dev/null +++ b/kernel/drivers/gpio/gpio-xilinx.c @@ -0,0 +1,40 @@ +/** + * @note Copyright (C) 2017 Greg Gallagher <g...@embeddedgreg.com> + * + * This driver controls the gpio that can be located on the PL + * of the Zynq SOC + * + * This pro

[Xenomai] [PATCH 3/3] Allow for more then one rt gpio driver to be built and loaded at the same build

Some SOCs will have two GPIO chips that require two independent drivers. In my case I was working with the Zynq SOC and needed a driver for the gpios on the FPGA and a driver for the gpios available on the ARM core. This change allows for two rt gpio drivers to be built and loaded at the same

[Xenomai] [PATCH 2/3] Handle device paths from the device tree that start with a forward slash

If the device name from the device tree starts with a forward slash (/) the rtdm device stores it in the registry including the forward slash. When we go to use that device and do the registry lookup we use a relative path from /dev/rtdm which doesn't contain the forward slash and fails to find a

Re: [Xenomai] Uninstall xenomai

How did you install it?   Original Message   From: samiraelmada...@gmail.com Sent: February 2, 2018 4:08 PM To: xenomai@xenomai.org Subject: [Xenomai] Uninstall xenomai Please How to uninstall xenomai-2.4.6 (remove all the partition) from the computer

[Xenomai] ipipe 4.14 arm 32-bit

Hi, Which ipipe branch should I be using to test out 4.14 ipipe? I tried rebase/4.14-arm, which worked after a couple of very small fix ups. If this is the branch we should be testing against I'll submit the patches to fix the raspberry pi build. -Greg

Re: [Xenomai] [PATCH 2/3] Handle device paths from the device tree that start with a forward slash

Yep, sorry I thought I removed that. Will update On Thu, Feb 1, 2018 at 5:29 AM, Philippe Gerum <r...@xenomai.org> wrote: > On 01/31/2018 03:36 AM, Greg Gallagher wrote: >> If the device name from the device tree starts with a forward slash (/) the >> rtdm device stor

Re: [Xenomai] [PATCH 3/3] Allow for more then one rt gpio driver to be built and loaded at the same build

Yes, will fix that On Thu, Feb 1, 2018 at 5:30 AM, Philippe Gerum <r...@xenomai.org> wrote: > On 01/31/2018 03:36 AM, Greg Gallagher wrote: >> Some SOCs will have two GPIO chips that require two independent drivers. In >> my >> case I was working with the Z

Re: [Xenomai] [PATCH] Fix up the imx uart driver so it now compiles with new kernels.

Makes sense, after the fact I realized this would diverge from the mainline structs. Will fix up and update. On Thu, Feb 1, 2018 at 5:02 AM, Philippe Gerum <r...@xenomai.org> wrote: > On 01/31/2018 03:28 AM, Greg Gallagher wrote: >> This patch is based on one that was submit

[Xenomai] [PATCH 3/3] Allow for more then one rt gpio driver to be built and loaded at the same build

Some SOCs will have two GPIO chips that require two independent drivers. In my case I was working with the Zynq SOC and needed a driver for the gpios on the FPGA and a driver for the gpios available on the ARM core. This change allows for two rt gpio drivers to be built and loaded at the same

[Xenomai] [PATCH 1/3] Add Xilinx AXI gpio driver

new file mode 100644 index 000..e982f5f --- /dev/null +++ b/kernel/drivers/gpio/gpio-xilinx.c @@ -0,0 +1,40 @@ +/** + * @note Copyright (C) 2017 Greg Gallagher <g...@embeddedgreg.com> + * + * This driver controls the gpio that can be located on the PL + * of the Zynq SOC + * + * This pro

[Xenomai] [PATCH 2/3] Handle device paths from the device tree that start with a forward slash

If the device name from the device tree starts with a forward slash (/) the rtdm device stores it in the registry including the forward slash. When we go to use that device and do the registry lookup we use a relative path from /dev/rtdm which doesn't contain the forward slash and fails to find a

[Xenomai] [PATCH] Fix up the imx uart driver so it now compiles with new kernels.

to be compatible with imx6. The original thread that this patch was derived from is located here: https://xenomai.org/pipermail/xenomai/2016-February/035924.html Signed-off-by: Greg Gallagher <g...@embeddedgreg.com> --- kernel/drivers/serial/rt_imx_uart.c

[Xenomai] Reference Board

Hi, After the recent meet up we had, I had an idea to help with a couple of issues that we identified. One issue that was brought up is new users don't know how to get started with Xenomai, this impacts the community of users and downstream feedback we get. To help this problem I'm proposing

Re: [Xenomai] Reference Board

at 11:52 AM, Lennart Sorensen <lsore...@csclub.uwaterloo.ca> wrote: > On Mon, Feb 05, 2018 at 11:22:46AM -0500, Greg Gallagher wrote: >> Hi, >>After the recent meet up we had, I had an idea to help with a >> couple of issues that we identified. One issue that was broug

Re: [Xenomai] [RTnet] 3.0.6 xenomai/net/drivers 'debug' symbol redeclared

This is fixed in stable-3.0.x On Mon, Jan 29, 2018 at 1:15 PM, Philippe Gerum wrote: > On 01/29/2018 07:01 PM, alessio margan wrote: >> Hi all, >> >> I was installing xenomai 3.0.6 ( >> https://xenomai.org/downloads/xenomai/stable/ ) on a 4.9.51 kernel, I >> get the following

[Xenomai] [PATCH] fixes for rpi 2b build

Small fix ups to enable building multi_v7_defconfig --- drivers/gpio/gpio-mvebu.c | 1 + drivers/gpio/gpio-pl061.c | 1 + drivers/gpio/gpio-zynq.c | 2 +- drivers/irqchip/irq-atmel-aic5.c | 6 -- drivers/irqchip/irq-bcm7120-l2.c | 15 +--

  1   2   3   4   5   >