Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Pohanka <xhpohanka@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] custom linux headers from custom kernel
Date: Tue, 16 Jul 2013 11:55:03 +0200	[thread overview]
Message-ID: <51E51877.4080004@gmail.com> (raw)

Hi all,

in our project using buildroot we are using a heavily patched kernel, 
which is retrieved form our GIT server. Thanks to buildroot this can be 
set up very easily. All is compiled by Codesourcery toolchain.

The kernel contains also a number of modules with own ioctls, so we need 
to use specific headers. I have found a *linux-headers* package, which 
installs own headers into staging directory, however there are also 
options using official headers or the ones from local kernel snapshot. 
Is there please any reason while there is no option for do 
headers-install from the kernel built by buildroot? If not I would 
prepare a patch adding this possibility into linux-headers package.

thanks
Jan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20130716/8bec131b/attachment.html>

                 reply	other threads:[~2013-07-16  9:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=51E51877.4080004@gmail.com \
    --to=xhpohanka@gmail.com \
    --cc=buildroot@busybox.net \
    /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