From: Tony Lindgren <tony@atomide.com>
To: David Anders <x0132446@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: Open issues after 2.6.38 merge window
Date: Fri, 14 Jan 2011 15:59:43 -0800 [thread overview]
Message-ID: <20110114235942.GS4957@atomide.com> (raw)
In-Reply-To: <20110114233838.GR4957@atomide.com>
* Tony Lindgren <tony@atomide.com> [110114 15:38]:
> * David Anders <x0132446@ti.com> [110114 12:56]:
> > Tony,
> >
> > i've been testing the 2.6.37 kernel on ES2.0, ES2.1, ES2.2 using the
> > following:
> >
> > x-loader:
> > git://gitorious.org/x-loader/x-loader.git
> > branch: master
> > 6f3a261 omap1: remove support for 1710 and 1510
> > defconfig: omap4430panda_config
> >
> > U-boot:
> > git://git.denx.de/u-boot.git
> > tag: v2010.12
> > defconfig: omap4_panda_config
>
> That's what I'm using too.
>
> > kernel:
> > git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
> > tag: v2.6.37
> > defconfig: omap2plus_defconfig
> >
> > i've not seen the power off issue you have described.
>
> Hmm well it happens also with v2.6.37, so sounds like it's
> a u-boot or hardware issue. I'll debug a bit further.
Weird. While debugging the problem, I left just the u-boot console
running for a few minutes to see if panda shuts down on it's own.
It did not, but instead it now stays running with the kernel
booted also.. No idea why. Did not touch anything with u-boot..
Tony
next prev parent reply other threads:[~2011-01-14 23:59 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-14 19:47 Open issues after 2.6.38 merge window Tony Lindgren
2011-01-14 20:24 ` Tony Lindgren
2011-01-14 20:37 ` Jarkko Nikula
2011-01-14 20:54 ` Tony Lindgren
2011-01-14 22:22 ` Nishanth Menon
2011-01-14 20:57 ` David Anders
2011-01-14 23:38 ` Tony Lindgren
2011-01-14 23:59 ` Tony Lindgren [this message]
2011-01-14 23:54 ` Thomas Weber
2011-01-15 5:19 ` Santosh Shilimkar
2011-01-17 10:15 ` Santosh Shilimkar
2011-01-27 18:41 ` Tony Lindgren
2011-01-17 11:37 ` Aaro Koskinen
2011-01-17 11:59 ` Santosh Shilimkar
2011-01-17 12:11 ` Russell King
2011-01-17 12:19 ` Santosh Shilimkar
2011-01-17 12:24 ` Russell King
2011-01-17 18:29 ` Tony Lindgren
2011-01-17 12:22 ` Aaro Koskinen
2011-01-17 12:35 ` Santosh Shilimkar
2011-01-17 12:50 ` Russell King
2011-01-17 18:20 ` Tony Lindgren
2011-01-17 20:31 ` Paul Walmsley
2011-01-17 20:39 ` Russell King
2011-01-17 21:00 ` Paul Walmsley
2011-01-17 21:19 ` Russell King
2011-01-17 22:49 ` 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=20110114235942.GS4957@atomide.com \
--to=tony@atomide.com \
--cc=linux-omap@vger.kernel.org \
--cc=x0132446@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