Subject: [PATCH v3] ARM: multi_v7_defconfig: Enable shmobile platforms

From: [email-masked] (Kevin Hilman)
Date: Wed, 04 Feb 2015 09:08:39 -0800

Geert Uytterhoeven <[email-masked]> writes:

> Hi Laurent,
>
> On Wed, Jan 21, 2015 at 2:02 PM, Laurent Pinchart
> <[email-masked]> 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