From: Tony Lindgren <tony@atomide.com>
To: Michael Welling <mwelling@emacinc.com>
Cc: linux-omap@vger.kernel.org,
Benoit Cousson <bcousson@baylibre.com>,
paul@pwsan.com
Subject: Re: AM3517 fails to boot 3.16-rc5 device tree kernel
Date: Mon, 21 Jul 2014 00:09:13 -0700 [thread overview]
Message-ID: <20140721070913.GN18374@atomide.com> (raw)
In-Reply-To: <CAO5Z=i1WdcrwWP2F6XZimUD5ts66AsV3RrvA31g71aUJewbNJA@mail.gmail.com>
* Michael Welling <mwelling@emacinc.com> [140718 07:42]:
> On Fri, Jul 18, 2014 at 1:38 AM, Tony Lindgren <tony@atomide.com> wrote:
> >
> > Hmm maybe double check your're booting device tree based kernel
> > instead of legacy machine ID based kernel? The legacy booting should
> > still work just fine and no changes has been made to it, but it will
> > get removed shortly.
>
> I downloaded the version from the test results and it did boot.
OK that's good to hear.
> These are combining the uImage and dtb. How do you accomplish this?
You need to make sure you have the appended DTB support enabled like
we do in omap2plus_defconfig:
CONFIG_ARM_APPENDED_DTB=y
CONFIG_ARM_ATAG_DTB_COMPAT=y
CONFIG_ARM_ATAG_DTB_COMPAT_CMDLINE_FROM_BOOTLOADER=y
Then just cat zImage board.dtb > /tmp/zImage-dtba and run
mkimage to convert it to a uImage:
$ mkimage -A arm -O linux -T kernel -C none -a 0x80008000 -e 0x80008000 \
-n "Linux" -d /tmp/zImage-dtba /tmp/uImage
Regards,
Tony
next prev parent reply other threads:[~2014-07-21 7:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-17 23:40 AM3517 fails to boot 3.16-rc5 device tree kernel mwelling
2014-07-18 6:38 ` Tony Lindgren
2014-07-18 14:40 ` Michael Welling
2014-07-18 15:02 ` Michael Welling
2014-07-21 7:17 ` Tony Lindgren
2014-07-18 16:13 ` Michael Welling
2014-07-21 7:19 ` Tony Lindgren
2014-07-21 7:09 ` Tony Lindgren [this message]
2014-07-21 16:38 ` Michael Welling
2014-07-22 0:15 ` Michael Welling
2014-07-22 6:20 ` Tony Lindgren
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=20140721070913.GN18374@atomide.com \
--to=tony@atomide.com \
--cc=bcousson@baylibre.com \
--cc=linux-omap@vger.kernel.org \
--cc=mwelling@emacinc.com \
--cc=paul@pwsan.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.