From: Jon Hunter <jon-hunter@ti.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Kevin Hilman <khilman@deeprootsystems.com>,
Sam Ravnborg <sam@ravnborg.org>, Kalle Valo <kalle.valo@iki.fi>,
"stanley.miao" <stanley.miao@windriver.com>,
"Gadiyar, Anand" <gadiyar@ti.com>,
Tony Lindgren <tony@atomide.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
Imre Deak <imre.deak@nokia.com>,
Tomi Valkeinen <tomi.valkeinen@nokia.com>
Subject: Re: [PATCH] OMAP_LDP: Support LCD display as a FB device on ZOOM MDK (Re: LDP support)
Date: Tue, 19 May 2009 15:54:15 -0500 [thread overview]
Message-ID: <4A131C77.1050001@ti.com> (raw)
In-Reply-To: <20090518185934.GL7042@n2100.arm.linux.org.uk>
Russell King - ARM Linux wrote:
> Moreover, I don't think forcing frame pointers to be enabled even with
> unwinding support is the right solution - if we have frame pointers
> there's no need for unwind support (so maybe the right answer is to
> force unwind support off for the time being?)
Ok, so I have tested this and if we add the following to the omap
defconfigs then this will enable frame pointers and disable unwinding
support. Hence, this should avoid the problems seen with the 2007q3 code
sourcery compiler.
# CONFIG_ARM_UNWIND is not set
Tony, would this be ok with you?
Russell, sorry I did not see this thread earlier.
Jon
next prev parent reply other threads:[~2009-05-19 20:55 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-28 22:07 LDP support Russell King - ARM Linux
2009-04-28 22:42 ` Tony Lindgren
2009-04-30 17:28 ` Koen Kooi
2009-05-05 19:52 ` Russell King - ARM Linux
2009-05-06 4:00 ` Tony Lindgren
2009-05-06 22:49 ` [PATCH] OMAP_LDP: Support LCD display as a FB device on ZOOM MDK (Re: LDP support) Tony Lindgren
2009-05-07 15:01 ` stanley.miao
2009-05-07 16:19 ` Russell King - ARM Linux
2009-05-07 16:28 ` Tony Lindgren
2009-05-07 16:34 ` Russell King - ARM Linux
2009-05-07 16:37 ` Russell King - ARM Linux
2009-05-07 16:41 ` Tony Lindgren
2009-05-07 16:56 ` Koen Kooi
2009-05-07 17:18 ` Tony Lindgren
2009-05-07 18:45 ` Koen Kooi
2009-05-08 3:26 ` stanley.miao
2009-05-08 3:27 ` Gadiyar, Anand
2009-05-08 9:18 ` stanley.miao
2009-05-08 15:22 ` Tony Lindgren
2009-05-08 16:47 ` Kalle Valo
2009-05-16 8:19 ` Russell King - ARM Linux
2009-05-18 15:54 ` Kalle Valo
2009-05-18 16:09 ` Russell King - ARM Linux
2009-05-18 17:13 ` Kevin Hilman
2009-05-18 18:59 ` Russell King - ARM Linux
2009-05-19 20:54 ` Jon Hunter [this message]
2009-05-07 21:42 ` Tony Lindgren
2009-05-14 9:07 ` LDP support Imre Deak
2009-05-14 17:33 ` Tony Lindgren
2009-05-31 21:24 ` Russell King - ARM Linux
2009-06-01 0:24 ` Woodruff, Richard
2009-06-01 7:45 ` Russell King - ARM Linux
2009-06-01 15:18 ` Woodruff, Richard
2009-06-01 15:26 ` Woodruff, Richard
2009-06-01 4:51 ` Felipe Balbi
2009-06-01 16:00 ` Tony Lindgren
2009-06-01 16:16 ` Russell King - ARM Linux
2009-06-03 21:39 ` Imre Deak
2009-06-03 22:33 ` Russell King - ARM Linux
2009-06-03 23:41 ` Tony Lindgren
2009-06-04 14:58 ` Imre Deak
2009-06-04 15:25 ` 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=4A131C77.1050001@ti.com \
--to=jon-hunter@ti.com \
--cc=gadiyar@ti.com \
--cc=imre.deak@nokia.com \
--cc=kalle.valo@iki.fi \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=sam@ravnborg.org \
--cc=stanley.miao@windriver.com \
--cc=tomi.valkeinen@nokia.com \
--cc=tony@atomide.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