ok so I found the header but its for the wrong kernel mt6572 but still no joy
make zImage fails for a related df0* object
code tidied up so its easier to reaad
I can not edit first post, but that is not important
If you are on Linux there are a number of Linaro toolchains to choose from
I chose the simplest cos I am a simple person .....giggles
click on d/l link = android-toolchain-eabi-4.9-2014.07-x86.tar.bz2
good luck
now we look to see if we can choose a different custom kernel within the kernel source
eg
#ifndef __ARCH_ARM_MACH_MT6575 visible from
/home/gordon/MT6582-KK-KERNEL/mediatek/custom/bird82_tb_td_a_kk/kernel/core/src/board-custom.h
mine is mt6582 so we can't use that one
2) Can't use same pathway for next kernel
but
/home/gordon/MT6582-KK-KERNEL/mediatek/custom/banyan_addon_x86/factory/init.rc
contents includes
chmod 0777 /dev/mt6516
and
mount yaffs2 mtd@system /system
Nope....my partition does not use yaffs nor do I have such dev
3) other one is also not mine as this pathway exist
/home/gordon/MT6582-KK-KERNEL/mediatek/custom/common/kernel/wifi/mt592x/
so I can't use "common" in my export pathway
I am no closer than before but I have eliminated all but mt6582 as potential custom kernel configs
grrrrrrrrrrr
make zImage fails for a related df0* object
code tidied up so its easier to reaad
Code:
KS=MT6582-KK-KERNEL
DN=mt6582
# fix errors in Linaro bin
cd /home/gordon/android-toolchain-eabi/bin
ln -s arm-linux-androideabi-ld.bfd arm-eabi-ld.bfd
ln -s arm-linux-androideabi-gcc arm-eabi-gcc
cd ~
# fix missing headers
cd $KS/mediatek
S1=platform/mt6582/kernel/core/include/mach
L2=kernel/include/mach
ln -s $S1/timex.h $L2/timex.h
ln -s $S1/memory.h $L2/memory.h
ln -s $S1/irqs.h $L2/irqs.h
ln -s $S1/mt_irq.h $L2/mt_irq.h
ln -s $S1/x_define_irq.h $L2/x_define_irq.h
ln -s $S1/mt_spm_idle.h $L2/mt_spm_idle.h
ln -s $S1/mt_devinfo.h $L2/mt_devinfo.h
ln -s $S1/entry-macro.S $L2/entry-macro.S
cd ~
# commands done in same shell, no persistence at this stage
export TARGET_PRODUCT=A9CL
export PATH=/home/gordon/android-toolchain-eabi/bin:$PATH
export ARCH_MTK_PLATFORM=mt6582
export TARGET_BUILD_VARIANT=user
export TARGET_PRODUCT=A9CL
export MTK_ROOT_CUSTOM=/home/gordon/$KS/mediatek/custom/
export TARGET_KERNEL_VERSION=mt6582
export CROSS_COMPILE=arm-eabi-
export ARCH=arm
cd $KS
cp mediatek/config/$DN/autoconfig/kconfig/platform kernel/.config
cd kernel
make prepare
# do not proceed unless no errors
# make menuconfig # no changes at this stage
# make zImage
# unresolved error no dfo_boot.h
# google and borrow the header from mt6572
# inject it and sym link it
I can not edit first post, but that is not important
If you are on Linux there are a number of Linaro toolchains to choose from
I chose the simplest cos I am a simple person .....giggles
click on d/l link = android-toolchain-eabi-4.9-2014.07-x86.tar.bz2
good luck
now we look to see if we can choose a different custom kernel within the kernel source
eg
#ifndef __ARCH_ARM_MACH_MT6575 visible from
/home/gordon/MT6582-KK-KERNEL/mediatek/custom/bird82_tb_td_a_kk/kernel/core/src/board-custom.h
mine is mt6582 so we can't use that one
2) Can't use same pathway for next kernel
but
/home/gordon/MT6582-KK-KERNEL/mediatek/custom/banyan_addon_x86/factory/init.rc
contents includes
chmod 0777 /dev/mt6516
and
mount yaffs2 mtd@system /system
Nope....my partition does not use yaffs nor do I have such dev
3) other one is also not mine as this pathway exist
/home/gordon/MT6582-KK-KERNEL/mediatek/custom/common/kernel/wifi/mt592x/
so I can't use "common" in my export pathway
I am no closer than before but I have eliminated all but mt6582 as potential custom kernel configs
grrrrrrrrrrr