Instruction is only provided for installing modules in /tmp directory. It is difficult to provide
the instructions for transferring modules to rootfs since it could be in eMMC.
Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam(a)linaro.org>
---
Changes since v1:
- Added INSTALL_MOD_STRIP=1 parameter to modules_install command for reducing the size of installed modules
debian/boards/dragonboard410c/README.textile.in | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/debian/boards/dragonboard410c/README.textile.in b/debian/boards/dragonboard410c/README.textile.in
index a44d269..91abb81 100644
--- a/debian/boards/dragonboard410c/README.textile.in
+++ b/debian/boards/dragonboard410c/README.textile.in
@@ -106,6 +106,12 @@ Additionally, you might want or need to compile the kernel modules:
bc. make -j4 modules KERNELRELEASE=##KERNEL_VER##-linaro-lt-qcom
+Install the compiled modules to /tmp directory:
+
+bc. make INSTALL_MOD_PATH=/tmp modules_install INSTALL_MOD_STRIP=1 KERNELRELEASE=##KERNEL_VER##-linaro-lt-qcom
+
+Note: These compiled modules in (/tmp/lib) should be transferred to dragonboard rootfs later.
+
h5. Building a boot image
You now need to create a valid boot image with your own kernel build.
--
2.7.4
On Wed, Jun 28, 2017 at 3:56 PM, Nicolas Dechesne
<nicolas.dechesne(a)linaro.org> wrote:
> On Wed, Jun 28, 2017 at 11:25 AM, Amit Kucheria
> <amit.kucheria(a)linaro.org> wrote:
>> Here are a couple of patches on top of the LT 4.9 kernel to fix the
>> issue. This sets up USER4 led on the DB410c to blink on a kernel
>> panic.
>
> In PATCH 2/2, could/should we use panic-indicator instead of default-trigger?
Yup, that is indeed better. Didn't know about that property. I'll send
a new patch.