public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Imre Deak <imre.deak@nokia.com>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"Valkeinen Tomi (Nokia-D/Helsinki)" <Tomi.Valkeinen@nokia.com>
Subject: Re: LDP support
Date: Thu, 14 May 2009 10:33:33 -0700	[thread overview]
Message-ID: <20090514173333.GL5593@atomide.com> (raw)
In-Reply-To: <20090514090731.GB29164@localhost>

* Imre Deak <imre.deak@nokia.com> [090514 02:09]:
> On Wed, May 06, 2009 at 06:00:16AM +0200, ext Tony Lindgren wrote:
> > * Russell King - ARM Linux <linux@arm.linux.org.uk> [090505 12:52]:
> > > On Tue, Apr 28, 2009 at 03:42:37PM -0700, Tony Lindgren wrote:
> > > > * Russell King - ARM Linux <linux@arm.linux.org.uk> [090428 15:07]:
> > > > > Tony, et.al.,
> > > > > 
> > > > > Any ideas when more LDP support will be pushed into mainline (such as
> > > > > the framebuffer support)?
> > > > 
> > > > I'll be looking at the board-*.c patches for the next merge window
> > > > hopefully this week or next week.
> > > > 
> > > > Looks like LDP keyboard, touchscreen & RTC are pretty much ready
> > > > to go. Then the MMC has some regulator updates, but AFAIK the MMC
> > > > should work OK already.
> > > > 
> > > > For the framebuffer, Imre and Tomi know the status the best, so
> > > > I've added them to Cc.
> > > > 
> > > > Imre has been meaning to send a bunch of drivers/video/omap changes
> > > > to the fbdev list for a while now and LDP framebuffer may depend on
> > > > those. Imre, any news on the status of sending the fb patches
> > > > upstream?
> > > > 
> > > > Then there are the upcoming DSS patches from Tomi, but those still
> > > > need some work before they're ready to go.
> > > 
> > > Is there any news on this?  Will we see more functional OMAP3 / LDP
> > > support queued for the next merge window?
> > 
> > Yes fro the stuff listed above, but still no news on the framebuffer
> > patches. Imre?
> 
> There is a mainline based tree with the missing DSS1 FB stuff that I'm
> planning to submit to fb-devel:
> 
> git clone git://koowaldah.org/people/imre/linux-2.6-fb
> 
> I could only compile test it for OMAP2/3 targets, it would be nice
> if someone could check if it works too. Also if some DSS1 FB related things
> are still missing from that tree, I could add them / submit them with
> the rest of the things.
> 
> Sorry for the big delay.

Great, I've started mirroring this as omapfb-upstream branch in the linux-omap
tree for easy testing.

Looks like your patch "ARM: OMAP: NOKIA-770: Add support for HWA742 LCD controller"
needs fixing to just pass the clocks to the LCD driver as discussed in
the recent 770 thread.

Also your patch "ARM: OMAP: FB: Add OMAP3 DISPC support" will be obsolete,
I have a fix in my omap-fixes queue that solves the problem with clkdev.

Regards,

Tony

  reply	other threads:[~2009-05-14 17:33 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
2009-05-07 21:42           ` Tony Lindgren
2009-05-14  9:07       ` LDP support Imre Deak
2009-05-14 17:33         ` Tony Lindgren [this message]
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=20090514173333.GL5593@atomide.com \
    --to=tony@atomide.com \
    --cc=Tomi.Valkeinen@nokia.com \
    --cc=imre.deak@nokia.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    /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