![]() To them, a baseline that always has the latest code, has the latest changes from all the participants, and has the most recent, mosto up-to-date information built into it, is by definition stable. Those that work on basic board functionality, and don’t truly care about stability. There are two types of developers in the world (in this context). Focusing on “TAGS” is an excellent idea, but let me elaborate. I saw your opening comment and I thought I would reply. $ cp -a u-boot.bin $ANDROID_ROOT/device/ti/panda/bootloader.bin $ cp -a MLO $ANDROID_ROOT/device/ti/panda/xloader.bin $ git checkout -b omap4_dev origin/omap4_dev Note: though bootloader and xloader images are provided within device/ti/panda dir, you can build them from source using the following instructions $ cp -a arch/arm/boot/zImage $ANDROID_ROOT/device/ti/panda/kernel – build with panda config $ make panda_defconfig $ git checkout -b android-omap-panda-3.0 origin/android-omap-panda-3.0 $ export CROSS_COMPILE=$ANDROID_ROOT/prebuilts/gcc/linux-x86/arm/arm-eabi-4.6/bin/arm-eabi. – prepare the environment $ export ARCH=arm mksdcard_pandaboard.sh /dev/sdX $ANDROID_ROOT – format and flash from a ubuntu machine, /dev/sdx is the the sdcard device $ LANG=C sudo. $ git apply 0001-add-mksdcard_pandaboard.sh.patch – you can either use fastboot to format and flash the images or use this script instead $ cd $ANDROID_ROOT $ git apply 0001-panda-jb4.2_hardware-ti-wpan.patch $ git apply 0001-panda-jb4.2_hardware-ti-omap4xxx.patch $ git apply 0001-panda-jb4.2_device-ti-panda.patch – apply the patches $ cd $ANDROID_ROOT/build/ – get the gpu user space binaries $ wget in case repo sync hangs use repo sync -j1 to disable multi threading also check repo sync -h for other options.to save time you can use an old tree and repo init inside it’s dir, then sync will grab only the differences.$ export ANDROID_ROOT=~/panda_work/android – prepare the directory $ mkdir ~/panda_work This post is a translated version of the Japanese post on reposted under permission of the main author that describes how to build Android JB tag android-4.2.2_r1 for pandaboard, of course some patching is required to get it work, you can download all the patches required from this mirror or follow the steps to get them one by one from the main mirror. That’s what a tag means in Software Engineering anyway ! Tags should represent a stable snapshot of he source tree to build and run. Google maintainers advise to always repo sync the master branch for panda claiming it’s the most stable, but in my opinion they should focus on stabilizing tags. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |