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==--