From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-wg0-x233.google.com ([2a00:1450:400c:c00::233]) by metis.ext.pengutronix.de with esmtp (Exim 4.72) (envelope-from ) id 1YFp8s-0008Mu-D6 for ptxdist@pengutronix.de; Mon, 26 Jan 2015 20:16:10 +0100 Received: by mail-wg0-f51.google.com with SMTP id k14so10782572wgh.10 for ; Mon, 26 Jan 2015 11:16:04 -0800 (PST) MIME-Version: 1.0 Date: Mon, 26 Jan 2015 20:16:04 +0100 Message-ID: From: Guillermo Rodriguez Garcia Subject: [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="===============1649586963==" Sender: ptxdist-bounces@pengutronix.de Errors-To: ptxdist-bounces@pengutronix.de To: "ptxdist@pengutronix.de" --===============1649586963== Content-Type: multipart/alternative; boundary=089e013d1b2c3b501f050d92f83d --089e013d1b2c3b501f050d92f83d Content-Type: text/plain; charset=UTF-8 Hello all, 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? -- Guillermo Rodriguez Garcia guille.rodriguez@gmail.com --089e013d1b2c3b501f050d92f83d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello all,

I wrote a custom driver for = my BSP, and I initially made it an out-of-tree driver (ptxdist newpackage s= rc-linux-driver and so on)

This driver needs to ex= port a header file (defining some ioctl values) for use by other (custom) p= txdist packages. I am currently exporting this header file in the "ins= tall" stage of the out-of-tree driver:

cp $(M= Y_DRIVER_DIR)/someheader.h $(PTXDIST_SYSROOT_TARGET)/usr/include
<= div>
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 ca= n I export the custom header in this case? I assume that modifying the gene= ric kernel.make is not the way to go.

Any hints?
<= div>

--
Guillermo Rodrigue= z Garcia
guille.rodriguez@= gmail.com
--089e013d1b2c3b501f050d92f83d-- --===============1649586963== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline -- ptxdist mailing list ptxdist@pengutronix.de --===============1649586963==-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from smtprelay01.ispgateway.de ([80.67.31.24]) by metis.ext.pengutronix.de with esmtp (Exim 4.72) (envelope-from ) id 1YG0ND-00014j-8e for ptxdist@pengutronix.de; Tue, 27 Jan 2015 08:15:43 +0100 Message-ID: <54C73EBE.10803@tqsc.de> Date: Tue, 27 Jan 2015 08:31:10 +0100 From: Markus Niebel MIME-Version: 1.0 References: In-Reply-To: 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: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ptxdist-bounces@pengutronix.de Errors-To: ptxdist-bounces@pengutronix.de To: ptxdist@pengutronix.de Cc: guille.rodriguez@gmail.com Hello, Am 26.01.2015 um 20:16 schrieb Guillermo Rodriguez Garcia: > Hello all, > > 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 > > Markus -- ptxdist mailing list ptxdist@pengutronix.de From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-we0-x234.google.com ([2a00:1450:400c:c03::234]) by metis.ext.pengutronix.de with esmtp (Exim 4.72) (envelope-from ) id 1YGCkC-0004su-KR for ptxdist@pengutronix.de; Tue, 27 Jan 2015 21:28:17 +0100 Received: by mail-we0-f180.google.com with SMTP id m14so17043208wev.11 for ; Tue, 27 Jan 2015 12:28:10 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <54C73EBE.10803@tqsc.de> References: <54C73EBE.10803@tqsc.de> Date: Tue, 27 Jan 2015 21:28:10 +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="===============1001597419==" Sender: ptxdist-bounces@pengutronix.de Errors-To: ptxdist-bounces@pengutronix.de To: Markus Niebel Cc: "ptxdist@pengutronix.de" --===============1001597419== Content-Type: multipart/alternative; boundary=001a1134cd58efd0fd050da81762 --001a1134cd58efd0fd050da81762 Content-Type: text/plain; charset=UTF-8 Hello, 2015-01-27 8:31 GMT+01:00 Markus Niebel : > Hello, > Am 26.01.2015 um 20:16 schrieb Guillermo Rodriguez Garcia: > > Hello all, > > > > 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! Best, Guillermo --001a1134cd58efd0fd050da81762 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello,

2015-01-27 8:31 GMT+01:00 Markus Niebel <list-09_ptxdist@tqsc.= de>:
Hello,
Am 26.01.2015 um 20:16 schrieb Guillermo Rodriguez Garcia:
> Hello all,
>
> 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<= br> > 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<= br> > driver and for that I am generating a set of patches against the kerne= l
> 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
<kernel>/include/uapi/<correct subdir>
modify the Kbuild script in this subdir to add your header to the headers t= o 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!

Best,=

Guillermo
--001a1134cd58efd0fd050da81762-- --===============1001597419== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline -- ptxdist mailing list ptxdist@pengutronix.de --===============1001597419==-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: From: Juergen Borleis Date: Wed, 28 Jan 2015 09:44:38 +0100 References: In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Message-Id: <201501280944.38868.jbe@pengutronix.de> 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: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Sender: ptxdist-bounces@pengutronix.de Errors-To: ptxdist-bounces@pengutronix.de To: ptxdist@pengutronix.de Cc: Markus Niebel , Guillermo Rodriguez Garcia 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 valu= es) > > > > 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/incl= ude > > > > > > > > So far so good. > > > > > > > > Now I would like to transform this out-of-tree driver into an in-tr= ee > > > > 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 t= he > > > > way to go. > > > > > > > > Any hints? > > > > > > split the internal from the external part and place the header to exp= ort > > > 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 th= e = additional include path is now gone as well. Regards, Juergen -- = Pengutronix e.K. =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0| Juergen Borleis =A0 =A0 =A0 =A0 =A0 =A0 | Industrial Linux Solutions =A0 =A0 =A0| http://www.pengutroni= x.de/ | -- = ptxdist mailing list ptxdist@pengutronix.de From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-wi0-x234.google.com ([2a00:1450:400c:c05::234]) by metis.ext.pengutronix.de with esmtp (Exim 4.72) (envelope-from ) id 1YGD0c-0005zG-HB for ptxdist@pengutronix.de; Tue, 27 Jan 2015 21:45:15 +0100 Received: by mail-wi0-f180.google.com with SMTP id h11so7660076wiw.1 for ; Tue, 27 Jan 2015 12:45:09 -0800 (PST) MIME-Version: 1.0 In-Reply-To: References: <54C73EBE.10803@tqsc.de> Date: Tue, 27 Jan 2015 21:45:08 +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="===============1590741763==" Sender: ptxdist-bounces@pengutronix.de Errors-To: ptxdist-bounces@pengutronix.de To: Markus Niebel Cc: "ptxdist@pengutronix.de" --===============1590741763== Content-Type: multipart/alternative; boundary=f46d043895779c192b050da854f2 --f46d043895779c192b050da854f2 Content-Type: text/plain; charset=UTF-8 2015-01-27 21:28 GMT+01:00 Guillermo Rodriguez Garcia < guille.rodriguez@gmail.com>: > Hello, > > 2015-01-27 8:31 GMT+01:00 Markus Niebel : > >> Hello, >> Am 26.01.2015 um 20:16 schrieb Guillermo Rodriguez Garcia: >> > Hello all, >> > >> > 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? 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? Thank you, Guillermo --f46d043895779c192b050da854f2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


2015-01-27 21:28 GMT+01:00 Guillermo Rodriguez Garcia <guille= .rodriguez@gmail.com>:
Hello,

2015-01-27 8:31 GMT+01:00 Markus Niebel <l= ist-09_ptxdist@tqsc.de>:
He= llo,
Am 26.01.2015 um 20:16 schrieb Guillermo Rodriguez Garcia:
> Hello all,
>
> 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<= br> > 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<= br> > driver and for that I am generating a set of patches against the kerne= l
> 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
<kernel>/include/uapi/<correct subdir>
modify the Kbuild script in this subdir to add your header to the headers t= o 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 i= t normal that after selecting the kernel headers
package in= ptxdist it wants to rebuild all other packages?

Is the= re any way to use the "modified" kernel headers only for a specif= ic
package (the custom driver mentioned above) without affe= cting the rest of
the packages?

Thank y= ou,

Guillermo
--f46d043895779c192b050da854f2-- --===============1590741763== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline -- ptxdist mailing list ptxdist@pengutronix.de --===============1590741763==-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: From: Juergen Borleis Date: Wed, 28 Jan 2015 10:45:52 +0100 References: <201501280944.38868.jbe@pengutronix.de> In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Message-Id: <201501281045.52493.jbe@pengutronix.de> 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: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Sender: ptxdist-bounces@pengutronix.de Errors-To: ptxdist-bounces@pengutronix.de To: Guillermo Rodriguez Garcia Cc: Markus Niebel , "ptxdist@pengutronix.de" Hi Guillermo, On Wednesday 28 January 2015 10:21:44 Guillermo Rodriguez Garcia wrote: > [...] > Thank you for the feedback. > I'm not sure to understand this, can you elaborate on how you did this > exactly? I created my kernel git repository in "local_src/kernel." and= did = all development within it (including the new ioctl header file) and with = PTXdist. To compile the package which needs this new ioctl header file I added the p= ath = to this development tree by adding "-I(KERNEL_DIR)/include/uapi/" into = package's rule file. Regards Juergen -- = Pengutronix e.K. =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0| Juergen Borleis =A0 =A0 =A0 =A0 =A0 =A0 | Industrial Linux Solutions =A0 =A0 =A0| http://www.pengutroni= x.de/ | -- = ptxdist mailing list ptxdist@pengutronix.de 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==--