All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Antw: Re:  In Buildroot, how to compile kernel modules
Date: Tue, 25 Feb 2014 21:40:50 +0100	[thread overview]
Message-ID: <530CFFD2.4040606@mind.be> (raw)
In-Reply-To: <530C80B0020000460004B17F@gwia2.rz.hs-offenburg.de>

On 25/02/14 11:38, Frank Ihle wrote:
> Hi and thanks for your response. Before i start hacking this, is it
> really that complicated ? For me it doesn't seem a big deal ?

 Actually, a much better example for simple modules is
package/on2-8170-modules/on2-8170-modules.mk

 You need to set VERSION and SITE like for all packages.

 You need to set DEPENDENCIES to LINUX (and also in the Config.in you
need to depend on BR2_LINUX_KERNEL).

 And you need the following build/install commands:

define ON2_8170_MODULES_BUILD_CMDS
        $(MAKE) -C $(LINUX_DIR) $(LINUX_MAKE_FLAGS) M=$(@D)
endef

define ON2_8170_MODULES_INSTALL_TARGET_CMDS
        $(MAKE) -C $(LINUX_DIR) $(LINUX_MAKE_FLAGS) M=$(@D) \
		modules_install
endef



 Regards,
 Arnout

-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2014-02-25 20:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-25  9:04 [Buildroot] In Buildroot, how to compile kernel modules Frank Ihle
2014-02-25 10:23 ` Raúl Sánchez Siles
2014-02-25 10:38   ` [Buildroot] Antw: " Frank Ihle
2014-02-25 20:40     ` Arnout Vandecappelle [this message]
2014-02-26  7:31       ` [Buildroot] " Frank Ihle
2014-02-26 17:32         ` Arnout Vandecappelle
2014-02-28  8:05           ` [Buildroot] Antw: " Frank Ihle

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=530CFFD2.4040606@mind.be \
    --to=arnout@mind.be \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.