From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/3] packages: ensure linux supports modules even when not using kernel-module
Date: Mon, 24 Aug 2015 17:34:43 +0200 [thread overview]
Message-ID: <20150824153443.GC3619@free.fr> (raw)
In-Reply-To: <87d1yczovv.fsf@dell.be.48ers.dk>
PEter, All,
On 2015-08-24 17:29 +0200, Peter Korsgaard spake thusly:
> >>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
>
> > Some packages build kernel modules without using the kernel-module infra
> > (because they use custom build systems); they do not automatically get
> > the kernel to support modules which is ensured when using the infra.
>
> > It must be done manually for all those packages.
>
> > Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> > Cc: Peter Korsgaard <jacmet@uclibc.org>
> > Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> > Cc: No? Rubinstein <nrubinstein@aldebaran.com>
> > Cc: Jan Viktorin <viktorin@rehivetech.com>
> > Cc: Gustavo Zacarias <gustavo@zacarias.com.ar>
> > ---
> > package/linux-fusion/linux-fusion.mk | 9 ++++++---
> > package/nvidia-driver/nvidia-driver.mk | 4 ++++
> > package/racehound/racehound.mk | 4 ++++
> > package/rtai/rtai.mk | 4 ++++
> > package/ti-gfx/ti-gfx.mk | 5 +++++
> > package/xtables-addons/xtables-addons.mk | 4 ++++
> > 6 files changed, 27 insertions(+), 3 deletions(-)
>
> > +++ b/package/nvidia-driver/nvidia-driver.mk
> > @@ -91,6 +91,10 @@ ifeq ($(BR2_PACKAGE_NVIDIA_DRIVER_MODULE),y)
>
> > NVIDIA_DRIVER_DEPENDENCIES += linux
>
> > +# We're building a kernel module without using the kernel-module infra,
> > +# so we need to tell we want module support in the kernel:
> > +LINUX_NEEDS_MODULES = y
> > +
>
> Ehh, this should only be done if the package is enabled, E.G.
>
> ifeq ($(BR2_PACKAGE_NVIDIA_DRIVER),y)
> LINUX_NEEDS_MODULES = y
> endif
Indeed. I just checked that when a module-building package was enabled,
that would turn CONFIG_MODULES on, but I did not check that it would not
touch it withour such a package.
Shame on me...
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2015-08-24 15:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-24 12:27 [Buildroot] [PATCH 0/3] core/pkg-kernel-config: ensure linux supports modules (branch yem/kernel-module) Yann E. MORIN
2015-08-24 12:27 ` [Buildroot] [PATCH 1/3] core/pkg-kernel-module: ensure linux supports modules Yann E. MORIN
2015-08-24 12:27 ` [Buildroot] [PATCH 2/3] core/pkg-kernel-module: drop now-useles check for CONFIG_MODULES Yann E. MORIN
2015-08-24 12:27 ` [Buildroot] [PATCH 3/3] packages: ensure linux supports modules even when not using kernel-module Yann E. MORIN
2015-08-24 15:29 ` Peter Korsgaard
2015-08-24 15:34 ` Yann E. MORIN [this message]
2015-08-24 14:11 ` [Buildroot] [PATCH 0/3] core/pkg-kernel-config: ensure linux supports modules (branch yem/kernel-module) Jan Viktorin
2015-08-24 15:33 ` Yann E. MORIN
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=20150824153443.GC3619@free.fr \
--to=yann.morin.1998@free.fr \
--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