mmmm tasty
Batch Build Kernel [Script]
1 - 11 of 11 Posts
Anytime! 
Nice script,
I do something similar, except I use a common config and sed it to build D/S kernel for ebi0 ebi1 and 2708 radios
basically I
I also package the modules in a sqf
little bit of extra junk in there for the wlan.ko
I do something similar, except I use a common config and sed it to build D/S kernel for ebi0 ebi1 and 2708 radios
basically I
Code:
make -j`grep 'processor' /proc/cpuinfo | wc -l` zImage<br />
find arch/arm/ -name zImage -exec install -D {} $OutDir/zImage \;<br />
INSTALL_MOD_PATH=${OutDir}/system make modules_install<br />
Code:
<br />
SquishModules ()<br />
{<br />
cd ${OutDir}/system/lib/modules<br />
wlan=`find -name wlan.ko |grep -v "\./wlan."|sed s~\./~~`<br />
if [ "`echo $wlan|grep -q wlan;echo $?`" = "0" ];<br />
then<br />
ln -sf $wlan `basename $wlan`<br />
fi<br />
mksquashfs * ${OutDir}/modules.sqf -all-root<br />
cd $KERNEL_DIR<br />
return<br />
}<br />Nice, might I ask why package the modules in squashfs if they are going to be installed to the given file system on the device anyways? Am I missing something?Firerat said:Nice script,
I do something similar, except I use a common config and sed it to build D/S kernel for ebi0 ebi1 and 2708 radios
basically I
I also package the modules in a sqfCode:make -j`grep 'processor' /proc/cpuinfo | wc -l` zImage<br /> find arch/arm/ -name zImage -exec install -D {} $OutDir/zImage \;<br /> INSTALL_MOD_PATH=${OutDir}/system make modules_install<br />
little bit of extra junk in there for the wlan.koCode:<br /> SquishModules ()<br /> {<br /> cd ${OutDir}/system/lib/modules<br /> wlan=`find -name wlan.ko |grep -v "\./wlan."|sed s~\./~~`<br /> if [ "`echo $wlan|grep -q wlan;echo $?`" = "0" ];<br /> then<br /> ln -sf $wlan `basename $wlan`<br /> fi<br /> mksquashfs * ${OutDir}/modules.sqf -all-root<br /> cd $KERNEL_DIR<br /> return<br /> }<br />
Oh nice, that makes sense now thanks for explaining..droid isnt hurting for space so much but I'm always looking to trim system size where I can...thanks for the tip
thanks for explaining..droid isnt hurting for space so much but I'm always looking to trim system size where I can...thanks for the tipjust noticed you pass mtdparts= on the cmdline
tbh I'm not sure how your recovery works, but I maintain a script for resizing mtd partitions
https://github.com/Firerat/CustomMTD/tree/unstable
this may be of interest
https://github.com/Firerat/CustomMTD/blob/unstable/MakeZips.sh
that is how I gen my updater-script, handy as you can input variables, e.g. print build date / version
( it's a little hacky tbh, I might switch to using python )
now this could also be useful to you
https://github.com/Firerat/android_build/commit/f6c0c448b27e93cc9c4c5a25b47713be4d9667e9
that is in python, but ignore that fact
it's the cMTD.sh script + the logic that gets added to the updater-script which may be of interest
like I said I don't know how your recovery works,
on the G1, MT3G , Hero , Desire, Bravo, Evo + others, we change the mtdparts of our recovery's kernel cmdline, format system cache and data (we only change the sizes of these), reboot and our partitions are different sizes
the AutoCMTD script then just copies this to the boot.img, thus recovery and ROM have compatible partition layouts
so you could add that logic, with a fallback to the hardcoded mtdpart cmdline
with some tinkering it may be possible that my CustomMTD script could be made compatible with the Droid 1,
omap2-nand.0: instead of msm_nand:
will have to look at it further, tbh I don't even know if you guys need or want it
Edit:
had a closer look, should be straight forward to fix my scripts ( for *any* device that can use mtdparts )
Off Topic here.. so I will create a thread for it when I have done the needed tweaks.
tbh I'm not sure how your recovery works, but I maintain a script for resizing mtd partitions
https://github.com/Firerat/CustomMTD/tree/unstable
this may be of interest
https://github.com/Firerat/CustomMTD/blob/unstable/MakeZips.sh
that is how I gen my updater-script, handy as you can input variables, e.g. print build date / version
( it's a little hacky tbh, I might switch to using python )
now this could also be useful to you
https://github.com/Firerat/android_build/commit/f6c0c448b27e93cc9c4c5a25b47713be4d9667e9
that is in python, but ignore that fact
it's the cMTD.sh script + the logic that gets added to the updater-script which may be of interest
like I said I don't know how your recovery works,
on the G1, MT3G , Hero , Desire, Bravo, Evo + others, we change the mtdparts of our recovery's kernel cmdline, format system cache and data (we only change the sizes of these), reboot and our partitions are different sizes
the AutoCMTD script then just copies this to the boot.img, thus recovery and ROM have compatible partition layouts
so you could add that logic, with a fallback to the hardcoded mtdpart cmdline
with some tinkering it may be possible that my CustomMTD script could be made compatible with the Droid 1,
omap2-nand.0: instead of msm_nand:
will have to look at it further, tbh I don't even know if you guys need or want it
Edit:
had a closer look, should be straight forward to fix my scripts ( for *any* device that can use mtdparts )
Off Topic here.. so I will create a thread for it when I have done the needed tweaks.
Awesome, thanks! Will be having a look at this
1 - 11 of 11 Posts
