[Xenomai] rtdm/driver.h location - Xenomai 3.0

[Xenomai] rtdm/driver.h location - Xenomai 3.0

[Michael Smith]

Hi.
I am busy porting device drivers over to Xenomai 3.0.
At the moment I'm having trouble figuring out the location of
rtdm/driver.h.
I would assume it should be installed under /usr/include/xenomai, because
in my previous Xenomai 2.x build the rtdm/rtdm_driver.h was located there.
I can see the file in the Xenomai source code but its not installed under
/usr/include/xenomai after Xenomai 3.0 the build and install.
I'm using cobalt with an x86_64 architecture.

Am I missing something? Is there something that I should have setup in the
configuration file with the install? I went back and had a look in the
Linux kernel
build setup under the Xenomai heading, but I could not see any obvious
options that I missed.

Thanks
Michael Smith

Re: [Xenomai] rtdm/driver.h location - Xenomai 3.0

[Philippe Gerum]

On 03/13/2015 09:17 AM, Michael Smith wrote:
> Hi.
> I am busy porting device drivers over to Xenomai 3.0.
> At the moment I'm having trouble figuring out the location of
> rtdm/driver.h.
> I would assume it should be installed under /usr/include/xenomai, because
> in my previous Xenomai 2.x build the rtdm/rtdm_driver.h was located there.
> I can see the file in the Xenomai source code but its not installed under
> /usr/include/xenomai after Xenomai 3.0 the build and install.
> I'm using cobalt with an x86_64 architecture.
> 
> Am I missing something? Is there something that I should have setup in the
> configuration file with the install? I went back and had a look in the
> Linux kernel
> build setup under the Xenomai heading, but I could not see any obvious
> options that I missed.
> 

In short, Xenomai 3 introduces a split between kernel and userland
headers, with only a few of them shared in order to expose the ABI. So
you need to build against a kernel prepared with the Xenomai sources,
adding the proper extra CFLAGS to your kernel Makefile for building the
module with the proper -I directives to find them.

Everything under /usr/include/xenomai now belongs to userland
exclusively, barring the ABI bits (uapi/).

See http://www.xenomai.org/pipermail/xenomai/2015-March/033558.html

-- 
Philippe.

Re: [Xenomai] rtdm/driver.h location - Xenomai 3.0

[Michael Smith]

On Fri, Mar 13, 2015 at 11:32 AM, Philippe Gerum <rpm@xenomai.org> wrote:
> On 03/13/2015 09:17 AM, Michael Smith wrote:
>> Hi.
>> I am busy porting device drivers over to Xenomai 3.0.
>> At the moment I'm having trouble figuring out the location of
>> rtdm/driver.h.
>> I would assume it should be installed under /usr/include/xenomai, because
>> in my previous Xenomai 2.x build the rtdm/rtdm_driver.h was located there.
>> I can see the file in the Xenomai source code but its not installed under
>> /usr/include/xenomai after Xenomai 3.0 the build and install.
>> I'm using cobalt with an x86_64 architecture.
>>
>> Am I missing something? Is there something that I should have setup in the
>> configuration file with the install? I went back and had a look in the
>> Linux kernel
>> build setup under the Xenomai heading, but I could not see any obvious
>> options that I missed.
>>
>
> In short, Xenomai 3 introduces a split between kernel and userland
> headers, with only a few of them shared in order to expose the ABI. So
> you need to build against a kernel prepared with the Xenomai sources,
> adding the proper extra CFLAGS to your kernel Makefile for building the
> module with the proper -I directives to find them.
>
> Everything under /usr/include/xenomai now belongs to userland
> exclusively, barring the ABI bits (uapi/).
>
> See http://www.xenomai.org/pipermail/xenomai/2015-March/033558.html
>
> --
> Philippe.

I understand.
Thanks Phillipe.
Will implement it like that.
If I can suggest, maybe to have a note of this somewhere in the
documentation, or
a RTDM example will clarify similar questions in the future.

Regards
Michael

Re: [Xenomai] rtdm/driver.h location - Xenomai 3.0

[Michael Smith]

On Fri, Mar 13, 2015 at 1:42 PM, Michael Smith <2michael.smith@gmail.com> wrote:
> On Fri, Mar 13, 2015 at 11:32 AM, Philippe Gerum <rpm@xenomai.org> wrote:
>> On 03/13/2015 09:17 AM, Michael Smith wrote:
>>> Hi.
>>> I am busy porting device drivers over to Xenomai 3.0.
>>> At the moment I'm having trouble figuring out the location of
>>> rtdm/driver.h.
>>> I would assume it should be installed under /usr/include/xenomai, because
>>> in my previous Xenomai 2.x build the rtdm/rtdm_driver.h was located there.
>>> I can see the file in the Xenomai source code but its not installed under
>>> /usr/include/xenomai after Xenomai 3.0 the build and install.
>>> I'm using cobalt with an x86_64 architecture.
>>>
>>> Am I missing something? Is there something that I should have setup in the
>>> configuration file with the install? I went back and had a look in the
>>> Linux kernel
>>> build setup under the Xenomai heading, but I could not see any obvious
>>> options that I missed.
>>>
>>
>> In short, Xenomai 3 introduces a split between kernel and userland
>> headers, with only a few of them shared in order to expose the ABI. So
>> you need to build against a kernel prepared with the Xenomai sources,
>> adding the proper extra CFLAGS to your kernel Makefile for building the
>> module with the proper -I directives to find them.
>>
>> Everything under /usr/include/xenomai now belongs to userland
>> exclusively, barring the ABI bits (uapi/).
>>
>> See http://www.xenomai.org/pipermail/xenomai/2015-March/033558.html
>>
>> --
>> Philippe.
>
> I understand.
> Thanks Phillipe.
> Will implement it like that.
> If I can suggest, maybe to have a note of this somewhere in the
> documentation, or
> a RTDM example will clarify similar questions in the future.
>
> Regards
> Michael

I am trying to do a out of tree compile for my RTDM driver.
As I include the line $(shell xeno-config --kcflags)) in my make file,
it expands to the line -Iarch/$(SRCARCH)/xenomai/include -Iinclude/xenomai.

My problem is my compiler is not finding the $(SRCARCH) variable in
the make process.
I had a look and its not defined in my environmental variables either.
I see the only place it is defined is in linux/Makefile on the top
level of the Linux tree.

But does this mean I can only compile a Xenomai driver as part of the
full Linux tree?
And do I need to re-make the whole kernel tree when I want to compile a custom
Xenomai driver?
Where would I need to place the RTDM source code if I want to compile
it, linux/drivers perhaps?
Or can I still do a out of tree compile for a Xenomai driver?

Thanks
Michael

Re: [Xenomai] rtdm/driver.h location - Xenomai 3.0

[Gilles Chanteperdrix]

On Fri, Mar 13, 2015 at 06:39:03PM +0200, Michael Smith wrote:
> On Fri, Mar 13, 2015 at 1:42 PM, Michael Smith <2michael.smith@gmail.com> wrote:
> > On Fri, Mar 13, 2015 at 11:32 AM, Philippe Gerum <rpm@xenomai.org> wrote:
> >> On 03/13/2015 09:17 AM, Michael Smith wrote:
> >>> Hi.
> >>> I am busy porting device drivers over to Xenomai 3.0.
> >>> At the moment I'm having trouble figuring out the location of
> >>> rtdm/driver.h.
> >>> I would assume it should be installed under /usr/include/xenomai, because
> >>> in my previous Xenomai 2.x build the rtdm/rtdm_driver.h was located there.
> >>> I can see the file in the Xenomai source code but its not installed under
> >>> /usr/include/xenomai after Xenomai 3.0 the build and install.
> >>> I'm using cobalt with an x86_64 architecture.
> >>>
> >>> Am I missing something? Is there something that I should have setup in the
> >>> configuration file with the install? I went back and had a look in the
> >>> Linux kernel
> >>> build setup under the Xenomai heading, but I could not see any obvious
> >>> options that I missed.
> >>>
> >>
> >> In short, Xenomai 3 introduces a split between kernel and userland
> >> headers, with only a few of them shared in order to expose the ABI. So
> >> you need to build against a kernel prepared with the Xenomai sources,
> >> adding the proper extra CFLAGS to your kernel Makefile for building the
> >> module with the proper -I directives to find them.
> >>
> >> Everything under /usr/include/xenomai now belongs to userland
> >> exclusively, barring the ABI bits (uapi/).
> >>
> >> See http://www.xenomai.org/pipermail/xenomai/2015-March/033558.html
> >>
> >> --
> >> Philippe.
> >
> > I understand.
> > Thanks Phillipe.
> > Will implement it like that.
> > If I can suggest, maybe to have a note of this somewhere in the
> > documentation, or
> > a RTDM example will clarify similar questions in the future.
> >
> > Regards
> > Michael
> 
> I am trying to do a out of tree compile for my RTDM driver.
> As I include the line $(shell xeno-config --kcflags)) in my make file,
> it expands to the line -Iarch/$(SRCARCH)/xenomai/include -Iinclude/xenomai.
> 
> My problem is my compiler is not finding the $(SRCARCH) variable in
> the make process.
> I had a look and its not defined in my environmental variables either.
> I see the only place it is defined is in linux/Makefile on the top
> level of the Linux tree.
> 
> But does this mean I can only compile a Xenomai driver as part of the
> full Linux tree?
> And do I need to re-make the whole kernel tree when I want to compile a custom
> Xenomai driver?
> Where would I need to place the RTDM source code if I want to compile
> it, linux/drivers perhaps?
> Or can I still do a out of tree compile for a Xenomai driver?

Compilation of kernel modules outside of the kernel sources is
documented in Documentation/kbuild/modules.txt in kernel sources.
Since RTDM modules are ordinary kernel modules, these instructions
apply. 

-- 
					    Gilles.

Re: [Xenomai] rtdm/driver.h location - Xenomai 3.0

[Helder Daniel]

I was having the same problem.
What I did was (for a one source code file module only to keep it simple):

In the source code: #include <rtdm/driver.h>

The makefile that I use is:

obj-m += modulesource.o

$(eval EXTRA_CFLAGS := $(shell xeno-config --kcflags))
#or:
#$(eval ccflags-y = $(shell xeno-config --kcflags))

all:
make -C /lib/modules/$(shell uname -r)/build M=$(PWD) modules
clean:
make -C /lib/modules/$(shell uname -r)/build M=$(PWD) clean

It assumes that:

/lib/modules/3.16.0-ipipe/build -> /usr/src/linux-3.16.0-ipipe/

points the full source tree (not just a headers tree like the one created
by the debian kbuild)




On 13 March 2015 at 16:39, Michael Smith <2michael.smith@gmail.com> wrote:

> On Fri, Mar 13, 2015 at 1:42 PM, Michael Smith <2michael.smith@gmail.com>
> wrote:
> > On Fri, Mar 13, 2015 at 11:32 AM, Philippe Gerum <rpm@xenomai.org>
> wrote:
> >> On 03/13/2015 09:17 AM, Michael Smith wrote:
> >>> Hi.
> >>> I am busy porting device drivers over to Xenomai 3.0.
> >>> At the moment I'm having trouble figuring out the location of
> >>> rtdm/driver.h.
> >>> I would assume it should be installed under /usr/include/xenomai,
> because
> >>> in my previous Xenomai 2.x build the rtdm/rtdm_driver.h was located
> there.
> >>> I can see the file in the Xenomai source code but its not installed
> under
> >>> /usr/include/xenomai after Xenomai 3.0 the build and install.
> >>> I'm using cobalt with an x86_64 architecture.
> >>>
> >>> Am I missing something? Is there something that I should have setup in
> the
> >>> configuration file with the install? I went back and had a look in the
> >>> Linux kernel
> >>> build setup under the Xenomai heading, but I could not see any obvious
> >>> options that I missed.
> >>>
> >>
> >> In short, Xenomai 3 introduces a split between kernel and userland
> >> headers, with only a few of them shared in order to expose the ABI. So
> >> you need to build against a kernel prepared with the Xenomai sources,
> >> adding the proper extra CFLAGS to your kernel Makefile for building the
> >> module with the proper -I directives to find them.
> >>
> >> Everything under /usr/include/xenomai now belongs to userland
> >> exclusively, barring the ABI bits (uapi/).
> >>
> >> See http://www.xenomai.org/pipermail/xenomai/2015-March/033558.html
> >>
> >> --
> >> Philippe.
> >
> > I understand.
> > Thanks Phillipe.
> > Will implement it like that.
> > If I can suggest, maybe to have a note of this somewhere in the
> > documentation, or
> > a RTDM example will clarify similar questions in the future.
> >
> > Regards
> > Michael
>
> I am trying to do a out of tree compile for my RTDM driver.
> As I include the line $(shell xeno-config --kcflags)) in my make file,
> it expands to the line -Iarch/$(SRCARCH)/xenomai/include -Iinclude/xenomai.
>
> My problem is my compiler is not finding the $(SRCARCH) variable in
> the make process.
> I had a look and its not defined in my environmental variables either.
> I see the only place it is defined is in linux/Makefile on the top
> level of the Linux tree.
>
> But does this mean I can only compile a Xenomai driver as part of the
> full Linux tree?
> And do I need to re-make the whole kernel tree when I want to compile a
> custom
> Xenomai driver?
> Where would I need to place the RTDM source code if I want to compile
> it, linux/drivers perhaps?
> Or can I still do a out of tree compile for a Xenomai driver?
>
> Thanks
> Michael
>
> _______________________________________________
> Xenomai mailing list
> Xenomai@xenomai.org
> http://www.xenomai.org/mailman/listinfo/xenomai
>



-- 
Helder Daniel
UALG - FCT
DEEI

http://w3.ualg.pt/~hdaniel

Re: [Xenomai] rtdm/driver.h location - Xenomai 3.0

[Gilles Chanteperdrix]

On Fri, Mar 13, 2015 at 05:06:06PM +0000, Helder Daniel wrote:
> I was having the same problem.
> What I did was (for a one source code file module only to keep it simple):
> 
> In the source code: #include <rtdm/driver.h>
> 
> The makefile that I use is:
> 
> obj-m += modulesource.o
> 
> $(eval EXTRA_CFLAGS := $(shell xeno-config --kcflags))
> #or:
> #$(eval ccflags-y = $(shell xeno-config --kcflags))
> 
> all:
> make -C /lib/modules/$(shell uname -r)/build M=$(PWD) modules
> clean:
> make -C /lib/modules/$(shell uname -r)/build M=$(PWD) clean
> 
> It assumes that:
> 
> /lib/modules/3.16.0-ipipe/build -> /usr/src/linux-3.16.0-ipipe/
> 
> points the full source tree (not just a headers tree like the one created
> by the debian kbuild)

Once again, typing:

make -C /usr/src/linux-3.16.0-ipipe/ M=$(PWD) modules

is shorter and avoids the need for a symbolic link which requires
root privileges.

-- 
					    Gilles.

Re: [Xenomai] rtdm/driver.h location - Xenomai 3.0

[Helder Daniel]

>
>
> Once again, typing:
>
> make -C /usr/src/linux-3.16.0-ipipe/ M=$(PWD) modules
>
> is shorter and avoids the need for a symbolic link which requires
> root privileges.
>
>
ok. thanks Gilles

Re: [Xenomai] rtdm/driver.h location - Xenomai 3.0

[Michael Smith]

On Fri, Mar 13, 2015 at 7:10 PM, Gilles Chanteperdrix
<gilles.chanteperdrix@xenomai.org> wrote:
> On Fri, Mar 13, 2015 at 05:06:06PM +0000, Helder Daniel wrote:
>> I was having the same problem.
>> What I did was (for a one source code file module only to keep it simple):
>>
>> In the source code: #include <rtdm/driver.h>
>>
>> The makefile that I use is:
>>
>> obj-m += modulesource.o
>>
>> $(eval EXTRA_CFLAGS := $(shell xeno-config --kcflags))
>> #or:
>> #$(eval ccflags-y = $(shell xeno-config --kcflags))
>>
>> all:
>> make -C /lib/modules/$(shell uname -r)/build M=$(PWD) modules
>> clean:
>> make -C /lib/modules/$(shell uname -r)/build M=$(PWD) clean
>>
>> It assumes that:
>>
>> /lib/modules/3.16.0-ipipe/build -> /usr/src/linux-3.16.0-ipipe/
>>
>> points the full source tree (not just a headers tree like the one created
>> by the debian kbuild)
>
> Once again, typing:
>
> make -C /usr/src/linux-3.16.0-ipipe/ M=$(PWD) modules
>
> is shorter and avoids the need for a symbolic link which requires
> root privileges.
>
> --
>                                             Gilles.

Thanks Gilles.
Its a great help.

Regards
Michael

Re: [Xenomai] rtdm/driver.h location - Xenomai 3.0

[Philippe Gerum]

On 03/13/2015 12:42 PM, Michael Smith wrote:
> On Fri, Mar 13, 2015 at 11:32 AM, Philippe Gerum <rpm@xenomai.org> wrote:
>> On 03/13/2015 09:17 AM, Michael Smith wrote:
>>> Hi.
>>> I am busy porting device drivers over to Xenomai 3.0.
>>> At the moment I'm having trouble figuring out the location of
>>> rtdm/driver.h.
>>> I would assume it should be installed under /usr/include/xenomai, because
>>> in my previous Xenomai 2.x build the rtdm/rtdm_driver.h was located there.
>>> I can see the file in the Xenomai source code but its not installed under
>>> /usr/include/xenomai after Xenomai 3.0 the build and install.
>>> I'm using cobalt with an x86_64 architecture.
>>>
>>> Am I missing something? Is there something that I should have setup in the
>>> configuration file with the install? I went back and had a look in the
>>> Linux kernel
>>> build setup under the Xenomai heading, but I could not see any obvious
>>> options that I missed.
>>>
>>
>> In short, Xenomai 3 introduces a split between kernel and userland
>> headers, with only a few of them shared in order to expose the ABI. So
>> you need to build against a kernel prepared with the Xenomai sources,
>> adding the proper extra CFLAGS to your kernel Makefile for building the
>> module with the proper -I directives to find them.
>>
>> Everything under /usr/include/xenomai now belongs to userland
>> exclusively, barring the ABI bits (uapi/).
>>
>> See http://www.xenomai.org/pipermail/xenomai/2015-March/033558.html
>>
>> --
>> Philippe.
> 
> I understand.
> Thanks Phillipe.
> Will implement it like that.
> If I can suggest, maybe to have a note of this somewhere in the
> documentation, or
> a RTDM example will clarify similar questions in the future.
> 

This newly added documentation may help:

http://xenomai.org/building-applications-with-xenomai-3-x/#compiling_a_rtdm-based_module

-- 
Philippe.

Re: [Xenomai] rtdm/driver.h location - Xenomai 3.0

[Michael Smith]

On Mon, Mar 16, 2015 at 11:59 AM, Philippe Gerum <rpm@xenomai.org> wrote:
> On 03/13/2015 12:42 PM, Michael Smith wrote:
>> On Fri, Mar 13, 2015 at 11:32 AM, Philippe Gerum <rpm@xenomai.org> wrote:
>>> On 03/13/2015 09:17 AM, Michael Smith wrote:
>>>> Hi.
>>>> I am busy porting device drivers over to Xenomai 3.0.
>>>> At the moment I'm having trouble figuring out the location of
>>>> rtdm/driver.h.
>>>> I would assume it should be installed under /usr/include/xenomai, because
>>>> in my previous Xenomai 2.x build the rtdm/rtdm_driver.h was located there.
>>>> I can see the file in the Xenomai source code but its not installed under
>>>> /usr/include/xenomai after Xenomai 3.0 the build and install.
>>>> I'm using cobalt with an x86_64 architecture.
>>>>
>>>> Am I missing something? Is there something that I should have setup in the
>>>> configuration file with the install? I went back and had a look in the
>>>> Linux kernel
>>>> build setup under the Xenomai heading, but I could not see any obvious
>>>> options that I missed.
>>>>
>>>
>>> In short, Xenomai 3 introduces a split between kernel and userland
>>> headers, with only a few of them shared in order to expose the ABI. So
>>> you need to build against a kernel prepared with the Xenomai sources,
>>> adding the proper extra CFLAGS to your kernel Makefile for building the
>>> module with the proper -I directives to find them.
>>>
>>> Everything under /usr/include/xenomai now belongs to userland
>>> exclusively, barring the ABI bits (uapi/).
>>>
>>> See http://www.xenomai.org/pipermail/xenomai/2015-March/033558.html
>>>
>>> --
>>> Philippe.
>>
>> I understand.
>> Thanks Phillipe.
>> Will implement it like that.
>> If I can suggest, maybe to have a note of this somewhere in the
>> documentation, or
>> a RTDM example will clarify similar questions in the future.
>>
>
> This newly added documentation may help:
>
> http://xenomai.org/building-applications-with-xenomai-3-x/#compiling_a_rtdm-based_module
>
> --
> Philippe.

Thanks, yes that's perfect.

Regards
Micheal