Building replicant for the Galaxy Player 50 (YP-G50).
Josh Branning
lovell.joshyyy at gmail.com
Wed May 30 19:22:02 UTC 2012
On 29/05/12 21:57, PaulK wrote:
>>> , however I suspect that replacing the kernel
>>> sources have an issue: what configuration did it take(the configurations
>>> are in arch/arm/configs)? to be sure you could run
>>> script/extract-ikconfig on the kernel binary...
>
> To have this done right, you must understand a bit of how kernel
> compiling works. I'll give you some hints:
>
> - on android (and embedded devices in general), you need a per-device
> kernel configuration
> - given the number of options, you can't determine it on your own, so
> you have to take the same configuration layout as on official samsung
> images
> - to do so, download an official update package from samsung for your
> device and run "script/extract-ikconfig" against the kernel file, likely
> to be named "zImage"
> - once you have the configuration layout, store it somewhere in
> arch/arm/configs/
> - then you must make sure the android build system will load this
> configuration
> - to change it, on galaxysmtd, modify the following file:
> vendor/replicant/products/replicant_galaxysmtd.mk
> - then you are ready to build for galaxysmtd with "make -j4
> recoveryimage"
> - the file to flash with heimdall is "recovery.img" for (kernel +
> recovery) or "boot.img" for (kernel + initramfs) but if you take
> ramdisk.img, you only have initramfs which is just a couple of files in
> an archive
>
> Though, I think the correct configuration is already there, and you
> might want to search for a todo or readme file at the index of the
> archive you got from samsung with instructions. It'll likely point you
> to the correct config file to use.
>
> Please bear in mind that dealing with the kernel requires some
> particular knowledge so I encourage you to learn as much as possible how
> things work before trying to do stuff you're unsure about (like flashing
> ramdisk.img). I know we all get to start with very few knowledge but it
> is important for you to understand what you're doing.
>
Hello, I've tried extracting the kernel configuration using
extract-ikconfig, but I'm
getting the following:
./extract-ikconfig ~/YP-G50_opensrc/kernel/output/zImage 2>&1
ERROR: Unable to extract kernel configuration information.
This kernel image may not have the config info.
In the readme from Samsung it says the following:
Using built-in specs.
Target: arm-eabi
Configured with: ../../toolchain/android-toolchain/gcc-4.2.1/configure
--prefix=/android/mathias/armdev/toolchain-eabi-4.2.1
--program-transform-name=s,^,arm-eabi-,
--prefix=/android/mathias/armdev/toolchain-eabi-4.2.1 --target=arm-eabi
--host=x86_64-unknown-linux-gnu --build=x86_64-unknown-linux-gnu
--enable-languages=c,c++ --disable-libstdc__-v3 --disable-libssp
--enable-threads --disable-nls --disable-libmudflap --with-float=soft
--with-fpu=vfp --with-arch=armv5te --enable-target-optspace
--with-abi=aapcs : (reconfigured)
../../toolchain/android-toolchain/gcc-4.2.1/configure
--prefix=/android/mathias/armdev/toolchain-eabi-4.2.1
--program-transform-name=s,^,arm-eabi-,
--prefix=/android/mathias/armdev/toolchain-eabi-4.2.1 --target=arm-eabi
--host=x86_64-unknown-linux-gnu --build=x86_64-unknown-linux-gnu
--enable-languages=c,c++ --disable-libstdc__-v3 --disable-libssp
--enable-threads --disable-nls --disable-libmudflap --with-float=soft
--with-fpu=vfp --with-arch=armv5te --enable-target-optspace --with-abi=aapcs
Thread model: single
gcc version 4.2.1
Could this help me get the configuration layout needed?
Thanks,
Josh
More information about the Replicant
mailing list