From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: MIME-Version: 1.0 In-Reply-To: <201501280944.38868.jbe@pengutronix.de> References: <201501280944.38868.jbe@pengutronix.de> Date: Wed, 28 Jan 2015 10:21:44 +0100 Message-ID: From: Guillermo Rodriguez Garcia Subject: Re: [ptxdist] ptxdist: Adding custom kernel headers Reply-To: ptxdist@pengutronix.de List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1744503391==" Sender: ptxdist-bounces@pengutronix.de Errors-To: ptxdist-bounces@pengutronix.de To: Juergen Borleis Cc: Markus Niebel , "ptxdist@pengutronix.de" --===============1744503391== Content-Type: multipart/alternative; boundary=001a1137fb786357bf050db2e6e5 --001a1137fb786357bf050db2e6e5 Content-Type: text/plain; charset=UTF-8 Hi Juergen, 2015-01-28 9:44 GMT+01:00 Juergen Borleis : > Hi Guillermo, > > On Tuesday 27 January 2015 21:45:08 Guillermo Rodriguez Garcia wrote: > > 2015-01-27 21:28 GMT+01:00 Guillermo Rodriguez Garcia > > guille.rodriguez@gmail.com>: > > > 2015-01-27 8:31 GMT+01:00 Markus Niebel : > > > > Am 26.01.2015 um 20:16 schrieb Guillermo Rodriguez Garcia: > > > > > I wrote a custom driver for my BSP, and I initially made it an > > > > > out-of-tree driver (ptxdist newpackage src-linux-driver and so on) > > > > > > > > > > This driver needs to export a header file (defining some ioctl > values) > > > > > for use by other (custom) ptxdist packages. I am currently > exporting > > > > > this header file in the "install" stage of the out-of-tree driver: > > > > > > > > > > cp $(MY_DRIVER_DIR)/someheader.h > $(PTXDIST_SYSROOT_TARGET)/usr/include > > > > > > > > > > So far so good. > > > > > > > > > > Now I would like to transform this out-of-tree driver into an > in-tree > > > > > driver and for that I am generating a set of patches against the > > > > > kernel tree. My question is: How can I export the custom header in > > > > > this case? I assume that modifying the generic kernel.make is not > the > > > > > way to go. > > > > > > > > > > Any hints? > > > > > > > > split the internal from the external part and place the header to > export > > > > under > > > > /include/uapi/ > > > > modify the Kbuild script in this subdir to add your header to the > > > > headers to export > > > > Generate patch series for your kernel and use this kernel version for > > > > the kernel header package in ptxdist > > > > > > Thank you, I think this is exactly what I needed! > > > > Just playing with this now, is it normal that after selecting the kernel > > headers package in ptxdist it wants to rebuild all other packages? > > Yes. Changes on the kernel-header package settings have a deep impact. > > > Is there any way to use the "modified" kernel headers only for a specific > > package (the custom driver mentioned above) without affecting the rest of > > the packages? > > If you create your own kernel-header package you can depend on it without > affecting the remaining packages depending on the generic kernel-header > package. > > A few weeks ago I had a similar issue and solved it (at least for the time > of > development) by adding the include path to the new ioctl file in my > development kernel source tree into the package rule file. After finishing > development the new ioctl file is now part of the kernel patch stack and > the > additional include path is now gone as well. > Thank you for the feedback. I'm not sure to understand this, can you elaborate on how you did this exactly? Did you create your own kernel-header package ? Guillermo --001a1137fb786357bf050db2e6e5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Juergen,

2015-01-28 9:44 GMT+01:00 Juergen Borleis <= jbe@pengutronix.de<= /a>>:
Hi Guillermo,

On Tuesday 27 January 2015 21:45:08 Guillermo Rodriguez Garcia wrote:
> 2015-01-27 21:28 GMT+01:00 Guillermo Rodriguez Garcia
> guille.rodriguez@gmail.c= om>:
> > 2015-01-27 8:31 GMT+01:00 Markus Niebel &= lt;list-09_ptxdist@tqsc.de&g= t;:
> > > Am 26.01.2015 um 20:16 schrieb Guill= ermo Rodriguez Garcia:
> > > > I wrote a custom driver for my = BSP, and I initially made it an
> > > > out-of-tree driver (ptxdist newpackage src-linux-driver= and so on)
> > > >
> > > > This driver needs to export a header file (defining som= e ioctl values)
> > > > for use by other (custom) ptxdist packages. I am curren= tly exporting
> > > > this header file in the "install" stage of th= e out-of-tree driver:
> > > >
> > > > cp $(MY_DRIVER_DIR)/someheader.h $(PTXDIST_SYSROOT_TARG= ET)/usr/include
> > > >
> > > > So far so good.
> > > >
> > > > Now I would like to transform this out-of-tree driver i= nto an in-tree
> > > > driver and for that I am generating a set of patches ag= ainst the
> > > > kernel tree. My question is: How can I export the custo= m header in
> > > > this case? I assume that modifying the generic kernel.m= ake is not the
> > > > way to go.
> > > >
> > > > Any hints?
> > >
> > > split the internal from the external part and place the head= er to export
> > > under
> > > <kernel>/include/uapi/<correct subdir>
> > > modify the Kbuild script in this subdir to add your header t= o the
> > > headers to export
> > > Generate patch series for your kernel and use this kernel ve= rsion for
> > > the kernel header package in ptxdist
> >
> > Thank you, I think this is exactly what I needed!
>
> Just playing with this now, is it normal that after selecting the kern= el
> headers package in ptxdist it wants to rebuild all other packages?

Yes. Changes on the kernel-header package settings have a deep impac= t.

> Is there any way to use the "modified" kernel headers only f= or a specific
> package (the custom driver mentioned above) without affecting the rest= of
> the packages?

If you create your own kernel-header package you can depend on it wi= thout
affecting the remaining packages depending on the generic kernel-header
package.

A few weeks ago I had a similar issue and solved it (at least for the time = of
development) by adding the include path to the new ioctl file in my
development kernel source tree into the package rule file. After finishing<= br> development the new ioctl file is now part of the kernel patch stack and th= e
additional include path is now gone as well.

Thank you for the feedback.
I'm not sure to under= stand this, can you elaborate on how you did this exactly?
=
Did you create your own kernel-header package ?
<= div style>
Guillermo
--001a1137fb786357bf050db2e6e5-- --===============1744503391== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline -- ptxdist mailing list ptxdist@pengutronix.de --===============1744503391==--