Re: dadd2bb931a08a4b6b17f9e82d9bbe7bedebbc98 breaks omapfb (old non-dss2)

[Tomi Valkeinen <tomi.valkeinen@nokia.com>]

On Tue, 2010-01-05 at 18:32 +0100, ext Paul Walmsley wrote:
> Hi Tomi,
> 
> On Tue, 15 Dec 2009, Tomi Valkeinen wrote:
> 
> > On Tue, 2009-12-15 at 10:58 +0100, ext Sergey Lapin wrote:
> > > dadd2bb931a08a4b6b17f9e82d9bbe7bedebbc98
> > > OMAP: OMAPFB: add omapdss device
> > > 
> > >     The upcoming new display subsystem driver is divided to two devices,
> > >     omapdss and omapfb, of which omapdss handles the actual hardware.
> > > 
> > >     This patch adds a dummy omapdss platform device for the current omapfb
> > >     driver, which is then used to get the clocks. This will make it possible
> > >     for the current and the new display drivers to co-exist.
> > > 
> > >     Signed-off-by: Tomi Valkeinen <tomi.valkeinen@nokia.com>
> > >     Acked-by: Tony Lindgren <tony@atomide.com>
> > > 
> > > breaks old omapfb.
> > 
> > I didn't look at this further, but I quickly tested with OMAP3 SDP
> > board, reverting the patch that makes SDP use DSS2, and it seems to work
> > fine with the old omapfb.
> > 
> > Perhaps you have more kernel debug options enabled, and then it
> > complains about missing release function. I'll look at it tomorrow.
> 
> This also affects omap_2430sdp_defconfig on 2430SDP:

I pushed patches fixing thisto master branch in my tree:
http://gitorious.org/linux-omap-dss2/linux

Can you try them out on 2320sdp? The commits are
3a2cbca3a3703ecd77c6fe633543ea0926b95564 and
c47f085ecf6d024c8850177694c702d814563580

 Tomi