, Richard
Subject: Re: State of LDP3430 platform
* Russell King - ARM Linux li...@arm.linux.org.uk [110212 08:09]:
On Sat, Feb 12, 2011 at 04:02:16PM +, Russell King - ARM Linux
wrote:
Another LDP3430 report...
The LDP3430 seems to be getting there, but:
1. LCD screen seems wrong
On Thu, Feb 24, 2011 at 01:51:50PM +0530, Janorkar, Mayuresh wrote:
Also, could you please share other CONFIG options which you are enabling
over omap2plus_defconfig? (Otherwise please share .config)
Attached.
#
# Automatically generated make config: don't edit
# Linux/arm 2.6.38-rc4 Kernel
-Original Message-
From: Rajendra Nayak [mailto:rna...@ti.com]
Sent: Thursday, February 24, 2011 12:39 PM
To: Richard Woodruff; Tony Lindgren; Russell King - ARM Linux
Cc: linux-omap@vger.kernel.org; Paul Walmsley; Santosh Shilimkar
Subject: RE: State of LDP3430 platform
* Russell King - ARM Linux li...@arm.linux.org.uk [110212 08:09]:
On Sat, Feb 12, 2011 at 04:02:16PM +, Russell King - ARM Linux wrote:
Another LDP3430 report...
The LDP3430 seems to be getting there, but:
1. LCD screen seems wrong. The X display looks rather large, and
From: Tony Lindgren [mailto:t...@atomide.com]
Sent: Wednesday, February 23, 2011 4:50 PM
Anybody from TI looking into these?
I'll poke some folks and check. I've not booted my LDP for a while.
As an older 3430 dev board its lost its shine compared to 3630 and 4430 dev
boards.
Regards,
Subject: RE: State of LDP3430 platform
From: Tony Lindgren [mailto:t...@atomide.com]
Sent: Wednesday, February 23, 2011 4:50 PM
Anybody from TI looking into these?
I'll poke some folks and check. I've not booted my LDP for a while.
There was a regulator mapping issue on 3430SDP because
Another LDP3430 report...
The LDP3430 seems to be getting there, but:
1. LCD screen seems wrong. The X display looks rather large, and
flickery - looks like the LCD timing parameters are wrong. Some
text disappears off the RHS.
fbset reports:
mode 240x320-510
On Sat, Feb 12, 2011 at 04:02:16PM +, Russell King - ARM Linux wrote:
Another LDP3430 report...
The LDP3430 seems to be getting there, but:
1. LCD screen seems wrong. The X display looks rather large, and
flickery - looks like the LCD timing parameters are wrong. Some
text
On Tue, 18 Jan 2011 12:36:26 -0700 (MST)
Paul Walmsley p...@pwsan.com wrote:
This is due to the recent ARM init_sched_clock() changes and the late
initialization of the counter_32k clock source. More information here:
http://marc.info/?l=linux-omapm=129513468605208w=2
Fix by
* Tony Lindgren t...@atomide.com [110118 15:20]:
* Tony Lindgren t...@atomide.com [110118 14:34]:
For omap15xx and 730 we need to use the MPU timer
as the 32K timer is not available. For omap16xx
we want to use the 32K timer because of PM. Fix this
by allowing to build in both timers.
* Tony Lindgren t...@atomide.com [110118 14:25]:
* Paul Walmsley p...@pwsan.com [110118 11:35]:
Here's a slightly updated version of this patch, fixing a bug in one of
the comments, and revising the commit message. There's no functional
difference between this and the previous version
On Mon, 17 Jan 2011, Tony Lindgren wrote:
* Paul Walmsley p...@pwsan.com [110115 20:31]:
--- a/arch/arm/mach-omap1/time.c
+++ b/arch/arm/mach-omap1/time.c
@@ -244,6 +244,13 @@ static void __init omap_timer_init(void)
omap_init_mpu_timer(rate);
omap_init_clocksource(rate);
Here's a slightly updated version of this patch, fixing a bug in one of
the comments, and revising the commit message. There's no functional
difference between this and the previous version of this patch.
- Paul
[PATCH] OMAP: counter_32k: init clocksource as part of machine timer init
* Paul Walmsley p...@pwsan.com [110118 11:35]:
Here's a slightly updated version of this patch, fixing a bug in one of
the comments, and revising the commit message. There's no functional
difference between this and the previous version of this patch.
Thanks, here are two patches to fix
For omap15xx and 730 we need to use the MPU timer
as the 32K timer is not available. For omap16xx
we want to use the 32K timer because of PM. Fix this
by allowing to build in both timers.
Signed-off-by: Tony Lindgren t...@atomide.com
--- a/arch/arm/mach-omap1/Kconfig
+++
* Tony Lindgren t...@atomide.com [110118 14:34]:
For omap15xx and 730 we need to use the MPU timer
as the 32K timer is not available. For omap16xx
we want to use the 32K timer because of PM. Fix this
by allowing to build in both timers.
This still needs one more patch to deal with the
* Woodruff, Richard r-woodru...@ti.com [110115 15:48]:
From: Tony Lindgren [mailto:t...@atomide.com]
Sent: Friday, January 14, 2011 6:03 PM
I've been seeing this on my omap4 panda. While debugging it, I left
u-boot console only running for a few minutes to see if that stays up.
It
From: Tony Lindgren [mailto:t...@atomide.com]
Sent: Monday, January 17, 2011 11:35 AM
This happened for a few days both with 2.6.37 and current mainline
kernel. After I started debugging it went away with no changes to
anything.. So can't debug any further at this point unfortunately.
Odd.
Hi,
* Paul Walmsley p...@pwsan.com [110115 20:31]:
--- a/arch/arm/mach-omap1/time.c
+++ b/arch/arm/mach-omap1/time.c
@@ -244,6 +244,13 @@ static void __init omap_timer_init(void)
omap_init_mpu_timer(rate);
omap_init_clocksource(rate);
+ /*
+ * XXX Since this file
Am 16.01.2011 05:32, schrieb Paul Walmsley:
On Sat, 15 Jan 2011, Russell King - ARM Linux wrote:
On Sat, Jan 15, 2011 at 12:38:46PM -0700, Paul Walmsley wrote:
On Fri, 14 Jan 2011, Tony Lindgren wrote:
* Paul Walmsley p...@pwsan.com [101207 19:30]:
On Tue, 7 Dec 2010, Paul Walmsley wrote:
On Fri, 14 Jan 2011, Tony Lindgren wrote:
* Paul Walmsley p...@pwsan.com [101207 19:30]:
On Tue, 7 Dec 2010, Paul Walmsley wrote:
Regarding the watchdog problem, unfortunately, I can't reproduce on the
BeagleBoard with v2.6.37-rc5 with either omap2plus_defconfig or
On Sat, Jan 15, 2011 at 12:38:46PM -0700, Paul Walmsley wrote:
On Fri, 14 Jan 2011, Tony Lindgren wrote:
* Paul Walmsley p...@pwsan.com [101207 19:30]:
On Tue, 7 Dec 2010, Paul Walmsley wrote:
Regarding the watchdog problem, unfortunately, I can't reproduce on the
BeagleBoard
From: Tony Lindgren [mailto:t...@atomide.com]
Sent: Friday, January 14, 2011 6:03 PM
I've been seeing this on my omap4 panda. While debugging it, I left
u-boot console only running for a few minutes to see if that stays up.
It did.. And after doing that somehow now my panda boots all the
On Sat, Jan 15, 2011 at 11:37:44PM +, Russell King - ARM Linux wrote:
On Sat, Jan 15, 2011 at 12:38:46PM -0700, Paul Walmsley wrote:
On Fri, 14 Jan 2011, Tony Lindgren wrote:
* Paul Walmsley p...@pwsan.com [101207 19:30]:
On Tue, 7 Dec 2010, Paul Walmsley wrote:
Regarding
From: Russell King - ARM Linux [mailto:li...@arm.linux.org.uk]
Sent: Saturday, January 15, 2011 5:38 PM
Why does OMAP initialize its clock sources soo late, outside of
the timer initialization? This means you have no counter in place
(except for the jiffies counter) during early boot.
Is
On Sat, Jan 15, 2011 at 06:05:24PM -0600, Woodruff, Richard wrote:
From: Russell King - ARM Linux [mailto:li...@arm.linux.org.uk]
Sent: Saturday, January 15, 2011 5:38 PM
Why does OMAP initialize its clock sources soo late, outside of
the timer initialization? This means you have no
On Sat, 15 Jan 2011, Woodruff, Richard wrote:
Recurring breaks fixes happened to out of trees as owners changed.
If a change breaks something in out-of-tree code, and a patch can be
created that is valid and correct for the mainline tree, then patches are
certainly welcomed on the public
On Sat, 15 Jan 2011, Russell King - ARM Linux wrote:
On Sat, Jan 15, 2011 at 12:38:46PM -0700, Paul Walmsley wrote:
On Fri, 14 Jan 2011, Tony Lindgren wrote:
* Paul Walmsley p...@pwsan.com [101207 19:30]:
On Tue, 7 Dec 2010, Paul Walmsley wrote:
Regarding the watchdog
* Paul Walmsley p...@pwsan.com [101207 19:30]:
On Tue, 7 Dec 2010, Paul Walmsley wrote:
Regarding the watchdog problem, unfortunately, I can't reproduce on the
BeagleBoard with v2.6.37-rc5 with either omap2plus_defconfig or
omap2plus_defconfig without CONFIG_WATCHDOG. If you send along
On Mon, Dec 06, 2010 at 11:27:45AM -0700, Paul Walmsley wrote:
On Mon, 6 Dec 2010, Tony Lindgren wrote:
* Russell King - ARM Linux li...@arm.linux.org.uk [101206 04:45]:
NET: Registered protocol family 16
[ cut here ]
WARNING: at
On Tue, 7 Dec 2010, Russell King - ARM Linux wrote:
So LDP will remain unusable until after the 2.6.38 merge window?
I don't think that Tony or I realized that LDP3430 was broken until your
E-mail. Usually I use a BeagleBoard 35xx for OMAP3430 testing, and I
think Tony uses an Overo. The
On Tue, 7 Dec 2010, Paul Walmsley wrote:
I do have a LDP3430 here though. It doesn't boot past:
[0.00] Linux version 2.6.37-rc5 (p...@twilight) (gcc version 4.3.2
(Sourcery G++ Lite 2008q3-72) ) #68 SMP Tue Dec 7 17:42:20
[0.00] CPU: ARMv7 Processor [411fc083] revision 3
* Russell King - ARM Linux li...@arm.linux.org.uk [101206 04:45]:
[ cut here ]
WARNING: at arch/arm/mach-omap2/omap_hwmod.c:1185
_omap_hwmod_enable+0x34/0x114()
omap_hwmod: wd_timer2: enabled state can only be entered from initialized,
idle, or disabled state
On Mon, Dec 06, 2010 at 07:59:59AM -0800, Tony Lindgren wrote:
* Russell King - ARM Linux li...@arm.linux.org.uk [101206 04:45]:
[ cut here ]
WARNING: at arch/arm/mach-omap2/omap_hwmod.c:1185
_omap_hwmod_enable+0x34/0x114()
omap_hwmod: wd_timer2: enabled state
* Russell King - ARM Linux li...@arm.linux.org.uk [101206 09:12]:
On Mon, Dec 06, 2010 at 07:59:59AM -0800, Tony Lindgren wrote:
* Russell King - ARM Linux li...@arm.linux.org.uk [101206 04:45]:
[ cut here ]
WARNING: at arch/arm/mach-omap2/omap_hwmod.c:1185
* Russell King - ARM Linux li...@arm.linux.org.uk [101206 04:45]:
NET: Registered protocol family 16
[ cut here ]
WARNING: at arch/arm/mach-omap2/omap_hwmod.c:1185
_omap_hwmod_enable+0x34/0x114()
omap_hwmod: wd_timer2: enabled state can only be entered from
On Mon, 6 Dec 2010, Tony Lindgren wrote:
* Russell King - ARM Linux li...@arm.linux.org.uk [101206 04:45]:
NET: Registered protocol family 16
[ cut here ]
WARNING: at arch/arm/mach-omap2/omap_hwmod.c:1185
_omap_hwmod_enable+0x34/0x114()
omap_hwmod: wd_timer2:
37 matches
Mail list logo
