> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:linux-omap- > [EMAIL PROTECTED] On Behalf Of Kevin Hilman > Sent: Friday, May 02, 2008 3:18 AM > To: Nishanth Menon > Cc: [EMAIL PROTECTED]; linux-omap@vger.kernel.org > Subject: Re: PM Issues after Android bootup on 2430 > > "Nishanth Menon" <[EMAIL PROTECTED]> writes: > > > On 4/29/08, [EMAIL PROTECTED] <[EMAIL PROTECTED]> > wrote: > >> omapfb omapfb: irq error status 00e2 > >> omapfb omapfb: irq error status 0040 > >> omapfb omapfb: irq error status 0040 > >> omapfb omapfb: irq error status 0040 > >> omapfb omapfb: irq error status 0040 > >> omapfb omapfb: irq error status 0040 > >> omapfb omapfb: irq error status 0040 > >> omapfb omapfb: irq error status 0040 > >> omapfb omapfb: irq error status 0040 > >> omapfb omapfb: irq error status 0040 > > This does look suspiciously like the thread > > http://linux.omap.com/pipermail/linux-omap-open-source/2007- > July/010566.html > > > > Interesting... ;)... I never got the chance to debug this issue.. > > > > Kevin, Khasim, did u guys get a chance to look at this later?? I dont > > recollect hearing any one saying the same for 3430 though.. > > No, I never debugged this any further. AFAIK, the omapfb is still > broken in git. > Me too :(.
We have FB working for 3530 EVM / Beagle boards. Should be same for 2430/2530 as well. Regards, Khasim -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
