Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dimitrios Siganos <dimitris@siganos.org>
To: buildroot@busybox.net
Subject: [Buildroot] kernel drivers
Date: Mon, 11 Feb 2013 20:52:22 +0000	[thread overview]
Message-ID: <51195A06.8000505@siganos.org> (raw)
In-Reply-To: <1360613608.96975.YahooMailNeo@web164601.mail.gq1.yahoo.com>

Hi Zoran,

Your question is not really buildroor specific, it is more linux kernel
specific. You need to learn how to write linux drivers. I can recommend
this open source book:
http://lwn.net/Kernel/LDD3

There are two options:

* Incorporate it into linux kernel sources (this can be linked in
statically or it can be a module). You choose linked in or module from
linux menuconfig, which at buildroot level you involve like this:
make linux-menuconfig

* The other way is to have your driver sources outside of the kernel and
build it as a module. This is the easiest way to start with. Have a look
at the package 'lttng-modules' for a simple example of this method.

But make sure you read the relevant chapters in LDD first.

Regards,
Dimitris

On 11/02/13 20:13, Zoran Djordjevic wrote:
> 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)?
> 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
> 

  reply	other threads:[~2013-02-11 20:52 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 [this message]
2013-02-11 21:11 ` Grant Edwards
2013-02-12  8:12 ` Stephan Hoffmann

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=51195A06.8000505@siganos.org \
    --to=dimitris@siganos.org \
    --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