I am trying to compile 150 Balbes source for a customer kernel.  I would like to enable CAN,  VCAN and SLCAN support in the kernel.  I copied the config file from /boot to the Amlogic_s905-kernel directory as .config.  I then ran make menuconfig and was able to select CAN, VCAN and SLCAN to enable those modules.  I then ran make and it seemed to build fine.  It took several hours so I went to sleep.  I didn't find any errors in the morning and I was able to see the new files under /arch/arm64/boot.  At that point I was a little confused on how to get the new kernel to emmc and boot it.  I thought before I screw something up I would see if I could just build the modules with make modules.  But I first ran make clean which deleted the kernel that I compiled.  From what I could find after I compiled the modules there is no SLCAN.o so I think that must be built into the kernel?

 

Am I going about this right?  I can build the kernel again but I am a little confused what I need to do after it is done.  Any pointers will help me on the next steps.

 

Looking at my config I now have:

CONFIG_CAN=y
CONFIG_CAN_RAW=y
CONFIG_CAN_BCM=y
CONFIG_CAN_GW=y
# CAN Device Drivers
CONFIG_CAN_VCAN=y
# CONFIG_CAN_VXCAN is not set
CONFIG_CAN_SLCAN=y
CONFIG_CAN_DEV=y
CONFIG_CAN_CALC_BITTIMING=y

 

Edited February 9, 20188 yr by pfer10
update configs

"y" means embedded in the kernel.

Okay can you step through the procedure to get the kernel in the boot directory properly as it compiled fine.  Is it as simply as just renaming the one file?  Do I have to bring anything else over?

 

Thanks!

Well I tried just moving the Image file over to the boot directory and renaming to zImage.  Looks like it won't boot now.  I'll put it on a TV and see what it is doing otherwise I I guess I will delete the new zImage and rename the .old one and see if that gets it back.

 

Okay I found that I had the wrong kernel.  I now have source for 3.14.29.  I added the modules that I need and confirmed they were set to =y in the .config.  I did make -j4.  I then had the Image file in arch/arm64.  I then ran mkimage -n 'linux-3.14' -A arm64 -O linux -T kernel -C none -a 0x11000000 -e 0x11000000 -d Image zImage.   

 

I was able to get the box to boot this time but I didn't have the module.  The only thing I think I might have done wrong is after I compiled the kernel I compiled the module.  I wasn't sure how to install modules so I tried the kernel.

 

What went wrong?  I can see the compiled modules now that I need but I am not sure how to get them installed.

 

Install the modules with the "make" command and rebuild the Initrd with the new modules.

6 hours ago, balbes150 said:

Install the modules with the "make" command and rebuild the Initrd with the new modules.

Is it as simple as update-initramfs -u -b /boot?

 

So just select my modules that I need in menuconfig.  Mark them with y.  Then make.  Then update-intrramfs.  I didn't need to do the other stuff?