Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Stephan Hoffmann <sho@relinux.de>
To: buildroot@busybox.net
Subject: [Buildroot] kernel drivers
Date: Tue, 12 Feb 2013 09:12:46 +0100	[thread overview]
Message-ID: <5119F97E.2040405@relinux.de> (raw)
In-Reply-To: <1360613608.96975.YahooMailNeo@web164601.mail.gq1.yahoo.com>

Am 11.02.2013 21:13, schrieb Zoran Djordjevic:
> My question is mostly theoretical, so I will be much obliged if I'll be pointed at some links, although
> (as Buildroot user) I am interested in the way I can do things with Buildroot. What I would like to 
> know is how can I incorporate some new kernel driver (having it's source) into kernel build? First, where 
> should I put it in kernel source tree, then can I compile it independently, without rebuilding whole kernel 
> (I imagine modules can do the job)?
Hello Zoran,

there are some topics not already mentioned by Dimitros' and Grant's
replies:

* If you put your driver into the kernel tree it has to be GPL
* Nowadays editing the kernel outside of buildroot and building it with
buildroot is easy thanks to the source override feature
* There are some samples of "out-of-kerneltree" drivers in buildroot
that can be used as a guideline for this, e.g. package/owl-linux/

Reards

Stephan
> How can I compile it as a module or to be more precise, do I write driver in some special way to be a module? 
> (I see that Buildroot offers some driver to be choosed for module compiling or to be part of monolitic kernel).
>  
> Regards
>
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20130212/fb0e7ea2/attachment.html>

      parent reply	other threads:[~2013-02-12  8:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-11 20:13 [Buildroot] kernel drivers Zoran Djordjevic
2013-02-11 20:52 ` Dimitrios Siganos
2013-02-11 21:11 ` Grant Edwards
2013-02-12  8:12 ` Stephan Hoffmann [this message]

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=5119F97E.2040405@relinux.de \
    --to=sho@relinux.de \
    --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