summaryrefslogtreecommitdiff
path: root/ubuntu
diff options
context:
space:
mode:
authorNicolas Dechesne <nicolas.dechesne@linaro.org>2015-03-30 11:17:40 +0200
committerNicolas Dechesne <nicolas.dechesne@linaro.org>2015-03-30 11:17:40 +0200
commitd75854c577623fcadb4f9d84de3255d5de9f081d (patch)
tree1e38ea72491da8472982071fe10d06e5a9e0dba2 /ubuntu
parentcad70d203665e8f7fea0c0f756e05b02d7bafc14 (diff)
ubuntu: remove section about fixup.bin, no longer required
The release now includes a proper fix for the ATAGs issues, we no longer need to prepend fixup.bin to the zImage, clean up the release notes. Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
Diffstat (limited to 'ubuntu')
-rw-r--r--ubuntu/boards/snapdragon/README.textile.in10
1 files changed, 3 insertions, 7 deletions
diff --git a/ubuntu/boards/snapdragon/README.textile.in b/ubuntu/boards/snapdragon/README.textile.in
index 50bc761..569d456 100644
--- a/ubuntu/boards/snapdragon/README.textile.in
+++ b/ubuntu/boards/snapdragon/README.textile.in
@@ -295,17 +295,13 @@ export CROSS_COMPILE=<path to your GCC cross compiler>/arm-linux-gnueabi-
make qcom_defconfig
make -j4 zImage dtbs
-Since kernel v3.17 there is a change in the way the kernel is prepared to boot on IFC6410 and Utilite2. the issue is that bootloaders on these boards use ATAGS to pass the memory information as we use CONFIG_ARM_ATAG_DTB_COMPAT config in kernel this option will extract the memory information from the ATAG list and store it at run time into the appended DTB. But the LK booloader in this case passes an *incorrect* memory address. The workaround for now is to prepend a binary blob before the kernel, and the responsibility of this binary blob is to fixup the wrong ATAGS. While this is definitely a workaround, and not a proper fix, this is the currently proposed and recommended workaround from people from the Linux MSM community.
+The DTB file needs to be appended to the @zImage@, as such, you can run the following command to prepare an image for the IFC6410:
-This binary blob is available in the Linaro kernel tree, both in source and precompiled format. The files are @fixup.bin@ and @fixup.S@. You can refer to @fixup.txt@ for instructions on how to rebuilt the binary blob.
-
-To prepare a kernel image one need to prepend @fixup.bin@ to @zImage@. And as discussed previously, the DTB file needs to be appended to the @zImage@ as well. That leads us to the following command to prepare an image for the IFC6410:
-
-bc. cat fixup.bin arch/arm/boot/zImage arch/arm/boot/dts/qcom-apq8064-ifc6410.dtb > zImage-dtb
+bc. cat arch/arm/boot/zImage arch/arm/boot/dts/qcom-apq8064-ifc6410.dtb > zImage-dtb
or, similarly, for Utilite2:
-bc. cat fixup.bin arch/arm/boot/zImage arch/arm/boot/dts/qcom-apq8064-cm-qs600.dtb > zImage-dtb
+bc. cat arch/arm/boot/zImage arch/arm/boot/dts/qcom-apq8064-cm-qs600.dtb > zImage-dtb
To boot a custom kernel image, you can run the following @fastboot@ command: