I think that's a good idea:one driver fit for all OMAP3 device. But that's a serious bug appears on the different OMAP3 based boards,
If Ti's bug, I think engineer can re-assign the bug to TIs' and get the confirm. What I want is if there exist another way? Can we do a workaround to fix it and move on. Must we use the Ti driver? whether we can write framebuffer directly instead of TI's driver? Or any other methods Several days before, my touchscreen can not work, so I also do the similar workaround to fix it. If some one familiar with this part, please help us! Leo 2010/11/25 Chen Dai <[email protected]> > ---------- Forwarded message ---------- > From: Thomas B. Ruecker <[email protected]> > Date: 2010/11/24 > Subject: Re: [MeeGo-dev] why my text display scratched > To: [email protected] > > > On Wed, Nov 24, 2010 at 10:54:42AM +0100, Carsten Munk wrote: > > I'd like us to use same SGX driver on all OMAP3 devices, yes. We've > > verified it worked on Beagle, but it requires that everyone uses the > > same kernel side driver too, that is, you should be working with the > > MeeGo kernel directly and contribute there. > Which although a nice goal poses a significant workload to > 'This device now allows arbitrary linux+userspace' projects. > Because arbitrary linux in most cases still means that you are locked > in to the ginormous undocumented patchset and kernel version > from the hardware vendor. Most of those projects have only very limited > resources. > > I once spent a weekend trying to make the n900 2.6.28 SGX source > work on the Archos 5 Internet Tablet 2.6.27.10 source. No joy. > And those are still fairly simmilar kernels in that domain. > The TI SGX driver just compiles. > > My opinion is still that if the TI driver is broken then we should > try to get TI to fix it. As it poses yet-another-high-hurdle to > anyone who tries to get MeeGo running on some OMAP3 based device > if you first have to find someone with serious kernel-kung-fu to > merge your kernel hardware specifics with an meego kernel in an > several week effort. Instead of just compiling the TI SGX driver. > > Don't misunderstand me. I think that the MeeGo approach is admirable. > I just don't see it fly in the real world in this context. > > my 0,02€ > > Thomas > > _______________________________________________ > MeeGo-dev mailing list > [email protected] > http://lists.meego.com/listinfo/meego-dev >
_______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
