Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Cross-Compiling out-of-tree driver
Date: Fri, 5 Apr 2013 14:07:52 +0200	[thread overview]
Message-ID: <20130405140752.195f40c9@skate> (raw)
In-Reply-To: <trinity-59b60d3c-656f-45cc-86d2-b8be6566e03e-1365162059588@3capp-gmx-bs42>

Hello Andreas,

(Would be nice if your e-mail had been wrapped to ~80 characters).

On Fri, 5 Apr 2013 13:40:59 +0200 (CEST), universeII at gmx.de wrote:

> I'm trying to use buildroot to create a Linux system for our custom
> VME PowerPC board.
>
> I succeeded in modifying the kernel to run on our special hardware
> but I'm stuck in compiling a driver out-of-tree.
>
> In-kernel compilation is no problem but for development and
> debugging of drivers it is much simpler to be able to compile drivers
> quickly out-of-tree and insert/remove them manually.
>
> I started to compile a dummy driver out-of-tree on my linux PC
> which works fine. Now I'm trying to use the linux kernel inside
> buildroot tree (setting KDIR appropriately) and use the cross-compile
> tool from buildroot. I searched the buildroot documentation but only
> found instructions how to compile own applications/libraries. Also
> TODOs from the internet on cross-compiling drivers did not help.
>
> Maybe I just oversee some simple things
>
> Can anybody give me a hint, how to cross-compile a linux driver
> out-of-tree using buildroot?

Yes. See the mail I posted a long time ago, which provided an example
of a kernel module and the associated .mk file:

  http://lists.busybox.net/pipermail/buildroot/2011-August/044807.html

Note however that the .mk file will need a few modifications,
especially the last line should just be:

$(eval $(generic-package))

I hope this helps. If not, don't hesitate to come back with
any question you may have.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  parent reply	other threads:[~2013-04-05 12:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-05 11:40 [Buildroot] Cross-Compiling out-of-tree driver universeII at gmx.de
2013-04-05 12:01 ` Samuel Martin
2013-04-05 12:07 ` Thomas Petazzoni [this message]
     [not found]   ` <trinity-e6e255fe-1d77-40c4-934f-3c35573b2dbc-1365166479514@3capp-gmx-bs29>
2013-04-05 13:19     ` Thomas Petazzoni
     [not found]       ` <trinity-48f3adad-041a-4437-8b4e-0f18f5b0c02c-1365168640703@3capp-gmx-bs29>
2013-04-05 13:57         ` [Buildroot] Fw: Aw: " universeII at gmx.de
2013-04-05 14:03   ` [Buildroot] " universeII at gmx.de
2013-04-05 14:19     ` [Buildroot] SOLVED: " universeII at gmx.de

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=20130405140752.195f40c9@skate \
    --to=thomas.petazzoni@free-electrons.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