From: lokeshvutla@ti•com (Lokesh Vutla)
To: linux-arm-kernel@lists•infradead.org
Subject: OMAP baseline test results for v3.10-rc6
Date: Thu, 27 Jun 2013 09:47:28 +0530 [thread overview]
Message-ID: <51CBBCD8.5030600@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1306261722520.6135@utopia.booyaka.com>
Hi Paul,
On Wednesday 26 June 2013 10:56 PM, Paul Walmsley wrote:
> On Wed, 26 Jun 2013, Rajendra Nayak wrote:
>
>> Apart from confirming if you are manually enabling these options, can you also give some
>> details on how you append the dtb to the kernel image?
>>
>> Most of us use an out-of-tree patch from Grant to do this, which I have shared below [2]
>>
>> Even without the patch with the below commands [1] to append the dtb, it still works, so it
>> would be good to know what steps you follow to append the dtb to the kernel image.
>
> Here's how I do it:
>
> ARCH=arm CROSS_COMPILE=${TOOLCHAIN_PATH}/bin/${TOOLCHAIN_PREFIX} nice make -j$CORES zImage am335x-bone.dtb
>
> cat arch/arm/boot/zImage arch/arm/boot/am335x-bone.dtb > arch/arm/boot/zImage-dtb.am335x-bone
Here is the catch..
Your dtb is generated in arch/arm/boot/dts/ folder(before V3.8 dtb was
generated in arch/arm/boot).
You are using very old dtb file. Please delete all your dtb files in
arch/arm/boot/ folder and check once.
Here is the patch from Grant Likely which does that.
https://patchwork.kernel.org/patch/1813321/
Can you please give a try updating this ..:)
Thanks and regards,
Lokesh
>
> scripts/mkuboot.sh -A arm -O linux -C none -T kernel -a 0x80008000 -e 0x80008000 -n 'Linux-' -d arch/arm/boot/zImage-dtb.am335x-bone arch/arm/boot/uImage-dtb.am335x-bone
>
>
> - Paul
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2013-06-27 4:17 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-17 5:23 OMAP baseline test results for v3.10-rc6 Paul Walmsley
2013-06-25 16:02 ` Felipe Balbi
2013-06-25 18:20 ` Paul Walmsley
2013-06-25 19:34 ` Tom Rini
2013-06-25 19:57 ` Kevin Hilman
2013-06-25 20:22 ` Tom Rini
2013-06-26 9:15 ` Russell King - ARM Linux
2013-06-26 11:27 ` Tom Rini
2013-06-26 4:53 ` Hiremath, Vaibhav
2013-06-26 13:22 ` Rajendra Nayak
2013-06-26 13:26 ` Tom Rini
2013-06-26 17:28 ` Paul Walmsley
2013-06-26 17:45 ` Tom Rini
2013-06-26 17:58 ` Paul Walmsley
2013-06-26 20:02 ` Tom Rini
2013-06-26 23:57 ` Kevin Hilman
2013-06-26 17:26 ` Paul Walmsley
2013-06-27 4:17 ` Lokesh Vutla [this message]
2013-06-28 18:45 ` Paul Walmsley
2013-07-01 2:15 ` Paul Walmsley
2013-07-02 4:29 ` Hiremath, Vaibhav
2013-07-02 14:15 ` Nishanth Menon
2013-07-03 19:51 ` Paul Walmsley
2013-07-04 18:12 ` Paul Walmsley
2013-07-05 5:48 ` Rajendra Nayak
2013-07-05 14:14 ` Tom Rini
2013-07-05 15:44 ` Paul Walmsley
2013-06-26 20:56 ` Kevin Hilman
2013-06-26 17:19 ` Paul Walmsley
2013-06-26 20:16 ` Tom Rini
2013-07-29 8:29 ` Paul Walmsley
2013-07-29 12:29 ` Tom Rini
2013-07-30 20:23 ` Paul Walmsley
2013-07-30 20:28 ` Nishanth Menon
2013-06-25 20:39 ` Felipe Balbi
2013-06-26 4:57 ` Hiremath, Vaibhav
2013-06-26 16:51 ` Paul Walmsley
2013-06-26 17:41 ` Paul Walmsley
2013-06-26 9:21 ` Lokesh Vutla
2013-06-26 17:36 ` Paul Walmsley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51CBBCD8.5030600@ti.com \
--to=lokeshvutla@ti$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox