mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Markus Niebel <list-09_ptxdist@tqsc.de>
To: ptxdist@pengutronix.de
Cc: guille.rodriguez@gmail.com
Subject: Re: [ptxdist] ptxdist: Adding custom kernel headers
Date: Tue, 27 Jan 2015 08:31:10 +0100	[thread overview]
Message-ID: <54C73EBE.10803@tqsc.de> (raw)
In-Reply-To: <CABDcavY_DHJu3VK7s6ZeY9F7PcHtgq+rihNCdvFe0Z-Z44zsXg@mail.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
<kernel>/include/uapi/<correct subdir>
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

  reply	other threads:[~2015-01-27  7:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-26 19:16 Guillermo Rodriguez Garcia
2015-01-27  7:31 ` Markus Niebel [this message]
2015-01-27 20:28   ` Guillermo Rodriguez Garcia
2015-01-27 20:45     ` Guillermo Rodriguez Garcia
2015-01-28  8:44       ` Juergen Borleis
2015-01-28  9:21         ` Guillermo Rodriguez Garcia
2015-01-28  9:45           ` Juergen Borleis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=54C73EBE.10803@tqsc.de \
    --to=list-09_ptxdist@tqsc.de \
    --cc=guille.rodriguez@gmail.com \
    --cc=ptxdist@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox