Commit graph

3 commits

Author SHA1 Message Date
Daniel Mentz
fe798d9f4f Use modprobe --all to load all modules in modules.load
Previously, we ran modprobe command for every .ko file listed in
init.insmod.*.cfg. Let's move to a different approach where we call
modprobe with the following command line.

modprobe -b --all=/vendor/lib/modules/modules.load

This will insmod all modules listed in modules.load except for those
that are mentioned in the blocklist at
/vendor/lib/modules/modules.blocklist

A common reason for a module to be on the blocklist is that it must only
be loaded under a certain condition like when a specific service is
launched.

Bug: 190652328
Change-Id: I37dfc83cbc90534243765f6985bc53f3fa83aef0
2021-06-23 05:10:36 +00:00
Daniel Mentz
5888eed0d1 init.insmod.sh: Find modules in different directories
Currenlty, kernel modules are only looked for in /vendor/lib/modules/.
With this change, we enable kernel modules to be stored under paths that
contain the kernel version string e.g.
/vendor/lib/modules/5.10.31-gd527c4be4795-dirty/
This aligns better with the kernel build system.

Bug: 185184472
Change-Id: I40db76f0409808700acd2d5524f8f3d606b3114f
2021-05-04 00:02:41 +00:00
Robin Peng
c2b5ca99e3 Move slider into gs101 and <device>
from: 026342771c6642980cb4653b1ec4d857a5d8be54

Bug: 167996145
Change-Id: I2ebf7f019afed1cbe9b60dcd82581bd3a52fe109
2021-03-06 16:31:12 +08:00