From: Tony Lindgren <tony@atomide.com>
To: Lokesh Vutla <lokeshvutla@ti.com>
Cc: Jacob Minshall <jacob@cozybit.com>, linux-omap@vger.kernel.org
Subject: Re: Unable to boot with kernel 3.11-rc1 on Panda Board ES Rev B1
Date: Tue, 16 Jul 2013 02:24:36 -0700 [thread overview]
Message-ID: <20130716092435.GV7656@atomide.com> (raw)
In-Reply-To: <51E4C836.1040300@ti.com>
* Lokesh Vutla <lokeshvutla@ti.com> [130715 21:19]:
> Hi Jacob,
> On Tuesday 16 July 2013 06:15 AM, Jacob Minshall wrote:
> > When trying to boot a Panda Board ES Rev B1 with the 3.11-rc1 kernel,
> > the boot does not work. All that happens is pasted below, and then it
> > just hangs there not actually starting the kernel. I have also
> > appended my .config file to the end of this email. I have tried this
> > exact setup only with a different image pointed to by the
> > pxelinux.cfg/<file> of a 3.6 kernel which works fine. Any help would
> > be appreciated.
> I guess you are not using DT boot. With the commit
> "ARM: OMAP2+: Remove board-omap4panda.c" from Tony non-dt boot is
> removed from mainline for OMAP4.
> Please use omap4-panda-es.dtb file for using dt boot on PANDA ES.
> I have boot tested 3.11-rc1 on PANDA ES, here is the log: http://pastebin.com/cnqpWT6m
> Please let me know if you need more info..:)
Also updating u-boot is recommended so you don't have to use appended
DTB. For appended DTB usage, there are some instructions in commit
b42b918194.
If using your custom .config file instead of omap2plus_defconfig,
you need to check that you have CONFIG_MACH_OMAP_GENERIC=y,
CONFIG_REGULATOR_FIXED_VOLTAGE=y, CONFIG_PINCTRL_SINGLE=y.
Regards,
Tony
prev parent reply other threads:[~2013-07-16 9:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-16 0:45 Unable to boot with kernel 3.11-rc1 on Panda Board ES Rev B1 Jacob Minshall
2013-07-16 4:12 ` Lokesh Vutla
2013-07-16 9:24 ` Tony Lindgren [this message]
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=20130716092435.GV7656@atomide.com \
--to=tony@atomide.com \
--cc=jacob@cozybit.com \
--cc=linux-omap@vger.kernel.org \
--cc=lokeshvutla@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).