From: Kevin Hilman <khilman@kernel.org>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3] ARM: multi_v7_defconfig: Enable shmobile platforms
Date: Wed, 04 Feb 2015 17:08:39 +0000 [thread overview]
Message-ID: <7h1tm5li3s.fsf@deeprootsystems.com> (raw)
In-Reply-To: <CAMuHMdWObPPnpDPQbrq1HRj9BSBFuNNusQkDhaDTxP+_16oMNg@mail.gmail.com> (Geert Uytterhoeven's message of "Wed, 21 Jan 2015 14:09:56 +0100")
Geert Uytterhoeven <geert@linux-m68k.org> writes:
> Hi Laurent,
>
> On Wed, Jan 21, 2015 at 2:02 PM, Laurent Pinchart
> <laurent.pinchart@ideasonboard.com> wrote:
>> To avoid bloating the kernel needlessly, couldn't at least some of the drivers
>> needed for the shmobile boards be compiled as modules ? Audio, USB, SATA,
>> touchscreen are possible candidates, depending on what we need to boot the
>> boards to userspace.
>
> That's a possibility.
>
> Note that currently there are almost no modules in multi_v7_defconfig:
> CONFIG_INET6_AH=m
> CONFIG_INET6_ESP=m
> CONFIG_INET6_IPCOMP=m
> CONFIG_IPV6_MIP6=m
> CONFIG_IPV6_TUNNEL=m
> CONFIG_CFG80211=m
> CONFIG_MAC80211=m
> CONFIG_BRCMFMAC=m
> CONFIG_RT2X00=m
> CONFIG_RT2800USB=m
>
> Arnd, Olof: What do you prefer?
The general rule (though not really enforced) has been: if it's needed for
a rootfs, it's OK to be built in (e.g. MMC, network, etc.) Everything
else should be modules.
FWIW, in my farm, modules are built and installed into the ramdisk so if
the kernel/rootfs needs them, they will be loaded.
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: khilman@kernel.org (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] ARM: multi_v7_defconfig: Enable shmobile platforms
Date: Wed, 04 Feb 2015 09:08:39 -0800 [thread overview]
Message-ID: <7h1tm5li3s.fsf@deeprootsystems.com> (raw)
In-Reply-To: <CAMuHMdWObPPnpDPQbrq1HRj9BSBFuNNusQkDhaDTxP+_16oMNg@mail.gmail.com> (Geert Uytterhoeven's message of "Wed, 21 Jan 2015 14:09:56 +0100")
Geert Uytterhoeven <geert@linux-m68k.org> writes:
> Hi Laurent,
>
> On Wed, Jan 21, 2015 at 2:02 PM, Laurent Pinchart
> <laurent.pinchart@ideasonboard.com> wrote:
>> To avoid bloating the kernel needlessly, couldn't at least some of the drivers
>> needed for the shmobile boards be compiled as modules ? Audio, USB, SATA,
>> touchscreen are possible candidates, depending on what we need to boot the
>> boards to userspace.
>
> That's a possibility.
>
> Note that currently there are almost no modules in multi_v7_defconfig:
> CONFIG_INET6_AH=m
> CONFIG_INET6_ESP=m
> CONFIG_INET6_IPCOMP=m
> CONFIG_IPV6_MIP6=m
> CONFIG_IPV6_TUNNEL=m
> CONFIG_CFG80211=m
> CONFIG_MAC80211=m
> CONFIG_BRCMFMAC=m
> CONFIG_RT2X00=m
> CONFIG_RT2800USB=m
>
> Arnd, Olof: What do you prefer?
The general rule (though not really enforced) has been: if it's needed for
a rootfs, it's OK to be built in (e.g. MMC, network, etc.) Everything
else should be modules.
FWIW, in my farm, modules are built and installed into the ramdisk so if
the kernel/rootfs needs them, they will be loaded.
Kevin
next prev parent reply other threads:[~2015-02-04 17:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-19 16:13 [PATCH v3] ARM: multi_v7_defconfig: Enable shmobile platforms Geert Uytterhoeven
2015-01-19 16:13 ` Geert Uytterhoeven
2015-01-20 1:25 ` Simon Horman
2015-01-20 1:25 ` Simon Horman
2015-01-21 13:02 ` Laurent Pinchart
2015-01-21 13:02 ` Laurent Pinchart
2015-01-21 13:09 ` Geert Uytterhoeven
2015-01-21 13:09 ` Geert Uytterhoeven
2015-01-21 13:15 ` Arnd Bergmann
2015-01-21 13:15 ` Arnd Bergmann
2015-02-04 10:12 ` Geert Uytterhoeven
2015-02-04 10:12 ` Geert Uytterhoeven
2015-02-04 10:16 ` Arnd Bergmann
2015-02-04 10:16 ` Arnd Bergmann
2015-02-04 17:08 ` Kevin Hilman [this message]
2015-02-04 17:08 ` Kevin Hilman
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=7h1tm5li3s.fsf@deeprootsystems.com \
--to=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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.