For anyone that is looking at using the arm 4.14 ipipe and xenomai
3.0.x stable with raspberry pi 2b, there's an issue with the gpio
driver that I'm currently looking into the issue. I don't think
anyone is using this kernel but in case anyone is, I thought I would
send out an FYI.
-Greg
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 core:
int fd, fdm;
void *p;
fd = open("/dev/foocard", O_RDWR);
If rtnet is something you require for beaglebone then it's definitely
worth trying. I don't think this will work right out of the box, so
expect that there will be some additional work to get it running.
On Tue, Apr 10, 2018 at 10:11 AM, Pintu Kumar wrote:
> On Tue, Apr 10,
On Tue, Apr 10, 2018 at 07:41:38PM +0530, Pintu Kumar wrote:
> So, this means there is no rtnet driver available for beagle bone ?
> Then it looks like we have to drop Xenomai for beagle bone... :-(
I don't know if one exists, but certainly it wasn't in the list you had.
> However, I found that
On Tue, Apr 10, 2018 at 7:20 PM, Lennart Sorensen
wrote:
> On Tue, Apr 10, 2018 at 06:52:11PM +0530, Pintu Kumar wrote:
>> Hi,
>>
>> I am using:
>> Beagle Bone Kernel: 4.9.51
>> Xenomai: 3.0.6
>> Board: Beagle Bone White
>>
>> When I enable RTNET, the following
On Tue, Apr 10, 2018 at 06:52:11PM +0530, Pintu Kumar wrote:
> Hi,
>
> I am using:
> Beagle Bone Kernel: 4.9.51
> Xenomai: 3.0.6
> Board: Beagle Bone White
>
> When I enable RTNET, the following ethernet drivers are build.
> $ ls drivers/xenomai/net/drivers/*.ko
>
Hi,
I am using:
Beagle Bone Kernel: 4.9.51
Xenomai: 3.0.6
Board: Beagle Bone White
When I enable RTNET, the following ethernet drivers are build.
$ ls drivers/xenomai/net/drivers/*.ko
drivers/xenomai/net/drivers/rt_8139too.ko
drivers/xenomai/net/drivers/rt_eepro100.ko
Quoting Rodrigo Amaducci :
Ok, I manually loaded the module and it works. I just thought that
the driver was already loaded from boot (as Analogy drivers are, for
example).
Thank you very much for the help, I'll see now if using XDDP fixes
the context switching
Quoting Greg Gallagher :
I was able to reproduce the issue, but it only happened if I didn't
have the driver loaded. I would try building it as a loadable module
then load it and confirm it's running using lsmod. Then run your test
application.
-Greg
Ok, I manually