Re: [MeeGo-dev] why my text display scratched
On Thursday, 25 de November de 2010 04:22:08 Leo wrote: > 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! The raster engine wouldn't be enough. You can try it, but it's likely that we won't reach the performance required for the smooth animations we want to have. We need the OpenGL ES drivers. -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Senior Product Manager - Nokia, Qt Development Frameworks PGP/GPG: 0x6EF45358; fingerprint: E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358 signature.asc Description: This is a digitally signed message part. ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] why my text display scratched
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 > -- Forwarded message -- > From: Thomas B. Ruecker > Date: 2010/11/24 > Subject: Re: [MeeGo-dev] why my text display scratched > To: meego-dev@meego.com > > > 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 > MeeGo-dev@meego.com > http://lists.meego.com/listinfo/meego-dev > ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] why my text display scratched
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 MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] why my text display scratched
Em Quarta-feira, 24 de Novembro de 2010, às 10:47:17, joern escreveu: > So why don't we use the N900 SGX driver generally? > Does anybody knows the difference beteween the official TI driver > and the N900 Nokia ones? Because the driver is patched to hell by the different device vendors to cope with their specific software and hardware specificities. I don't think anyone has a full view of the patches applied and bugs fixed. -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Senior Product Manager - Nokia, Qt Development Frameworks PGP/GPG: 0x6EF45358; fingerprint: E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358 signature.asc Description: This is a digitally signed message part. ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] why my text display scratched
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. BR Carsten Munk 2010/11/24 joern : > So why don't we use the N900 SGX driver generally? > Does anybody knows the difference beteween the official TI driver > and the N900 Nokia ones? > > Where can I get the N900 SGX driver? I would like to test it, to > see if I get the same results as you. > > B.R. > Jörn > > Am 24.11.2010 10:28, schrieb Carsten Munk: >> >> 2010/11/24 Thiago Macieira: >>> >>> Em Quarta-feira, 24 de Novembro de 2010, às 09:28:29, Leo escreveu: Hi Joern: [?] to hear that, I think we'd check the component one by one, QT depends on the Xlib and X extension, I will do the test to check whether it's ok if I draw the string via Xlib, and to make clear which level it happened. >>> >>> Make sure you're using standard, modern client-side fonts (fontconfig, >>> freetype), not old-style X server-side fonts. >> >> The funny thing about this problem is that we see it when we have >> pretty much same image as N900, but drop in 'official' TI OMAP3 GFX, >> the fonts corrupt. We've seen that when using the N900 sgx drivers on >> Beagleboard, this problem doesn't manifest.. >> >> >> BR >> Carsten Munk >> ___ >> MeeGo-dev mailing list >> MeeGo-dev@meego.com >> http://lists.meego.com/listinfo/meego-dev > > ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] why my text display scratched
So why don't we use the N900 SGX driver generally? Does anybody knows the difference beteween the official TI driver and the N900 Nokia ones? Where can I get the N900 SGX driver? I would like to test it, to see if I get the same results as you. B.R. Jörn Am 24.11.2010 10:28, schrieb Carsten Munk: 2010/11/24 Thiago Macieira: Em Quarta-feira, 24 de Novembro de 2010, às 09:28:29, Leo escreveu: Hi Joern: [?] to hear that, I think we'd check the component one by one, QT depends on the Xlib and X extension, I will do the test to check whether it's ok if I draw the string via Xlib, and to make clear which level it happened. Make sure you're using standard, modern client-side fonts (fontconfig, freetype), not old-style X server-side fonts. The funny thing about this problem is that we see it when we have pretty much same image as N900, but drop in 'official' TI OMAP3 GFX, the fonts corrupt. We've seen that when using the N900 sgx drivers on Beagleboard, this problem doesn't manifest.. BR Carsten Munk ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] why my text display scratched
2010/11/24 Thiago Macieira : > Em Quarta-feira, 24 de Novembro de 2010, às 09:28:29, Leo escreveu: >> Hi Joern: >> [?] to hear that, I think we'd check the component one by one, >> QT depends on the Xlib and X extension, >> I will do the test to check whether it's ok if I draw the string via Xlib, >> and to make clear which level it happened. > > Make sure you're using standard, modern client-side fonts (fontconfig, > freetype), not old-style X server-side fonts. The funny thing about this problem is that we see it when we have pretty much same image as N900, but drop in 'official' TI OMAP3 GFX, the fonts corrupt. We've seen that when using the N900 sgx drivers on Beagleboard, this problem doesn't manifest.. BR Carsten Munk ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] why my text display scratched
Em Quarta-feira, 24 de Novembro de 2010, às 09:28:29, Leo escreveu: > Hi Joern: > [?] to hear that, I think we'd check the component one by one, > QT depends on the Xlib and X extension, > I will do the test to check whether it's ok if I draw the string via Xlib, > and to make clear which level it happened. Make sure you're using standard, modern client-side fonts (fontconfig, freetype), not old-style X server-side fonts. -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Senior Product Manager - Nokia, Qt Development Frameworks PGP/GPG: 0x6EF45358; fingerprint: E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358 signature.asc Description: This is a digitally signed message part. ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] why my text display scratched
Hi Joern: [?] to hear that, I think we'd check the component one by one, QT depends on the Xlib and X extension, I will do the test to check whether it's ok if I draw the string via Xlib, and to make clear which level it happened. B.R Leo 2010/11/24 joern > Hi Leo, > I can report the same issue on Gumstix Overo with Chestnut43 Board. > The UI is running on a 4,3" LCD with 480x272 resolution. > > Running a daily Meego Build from last week. (Meego 1.1 and > GFX_4_00_00_01_libs.tar.gz) > The driver which is used is: mesa-dri-swrast-driver. > > Can there be the issue? Because Nokia uses another driver on N900 and it > works fine. > > Regards > Jörn > > > Am 24.11.2010 08:27, schrieb Leo: > > Hi Carsten: >GFX version is the latest:GFX_4_00_00_01_libs.tar.gz. Meego1.1 handset. > > But if I use Xlib create window, and use userdefined font, we can render > text correctly. > Browser I think may also use their own font. How about your QT application? > > > B.R > Leo > > 2010/11/24 Carsten Munk > >> >> 2010/11/24 Leo : >> >> > http://bugs.meego.com/show_bug.cgi?id=5616 >> >> > please look at this bug, I found there is a bug same as mine >> >> 2010/11/24 Leo : >> > My device is devkit8000, CPU->OMAP3530, >> >-600-MHz ARM Cortex-A8 Core >> >-412-MHz TMS320C64x+ DSP Core >> > >> > Here is details about hardware: >> > http://www.armkits.com/Product/devkit8000.asp >> > >> > I launch the browser, it's good! I'm not familiar with the >> Gecko/Fennec, >> > But I have some experience with webkit, As I know, Webkit will do its >> > layout and >> > use the cairo/skia/gdk... to generate its pixbuf, then copy to GPU or >> the >> > framebuffer to ask for render. >> > And consider the situation I talked, it means we can draw the pixbuf >> > correctly. >> > >> > If the text is not ok, why browser can get the correct layout? >> > I feel very confused. >> > >> >> Yeah, you're running into bug 5616 alright - we don't know exactly >> what causes it. If we use the SGX driver from Nokia N900 + it's >> libraries, the problem does not manifest. >> >> Could you note down the version of SGX drivers/GFX package you use in >> the bug report? >> >> BR >> Carsten Munk >> > > > ___ > MeeGo-dev mailing > listmeego-...@meego.comhttp://lists.meego.com/listinfo/meego-dev > > > <<33A.gif>>___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] why my text display scratched
Hi Leo, I can report the same issue on Gumstix Overo with Chestnut43 Board. The UI is running on a 4,3" LCD with 480x272 resolution. Running a daily Meego Build from last week. (Meego 1.1 and GFX_4_00_00_01_libs.tar.gz) The driver which is used is: mesa-dri-swrast-driver. Can there be the issue? Because Nokia uses another driver on N900 and it works fine. Regards Jörn Am 24.11.2010 08:27, schrieb Leo: Hi Carsten: GFX version is the latest:GFX_4_00_00_01_libs.tar.gz. Meego1.1 handset. But if I use Xlib create window, and use userdefined font, we can render text correctly. Browser I think may also use their own font. How about your QT application? B.R Leo 2010/11/24 Carsten Munk mailto:cars...@maemo.org>> >> 2010/11/24 Leo mailto:leo20090...@gmail.com>>: >> > http://bugs.meego.com/show_bug.cgi?id=5616 >> > please look at this bug, I found there is a bug same as mine 2010/11/24 Leo mailto:leo20090...@gmail.com>>: > My device is devkit8000, CPU->OMAP3530, >-600-MHz ARM Cortex-A8 Core >-412-MHz TMS320C64x+ DSP Core > > Here is details about hardware: > http://www.armkits.com/Product/devkit8000.asp > > I launch the browser, it's good! I'm not familiar with the Gecko/Fennec, > But I have some experience with webkit, As I know, Webkit will do its > layout and > use the cairo/skia/gdk... to generate its pixbuf, then copy to GPU or the > framebuffer to ask for render. > And consider the situation I talked, it means we can draw the pixbuf > correctly. > > If the text is not ok, why browser can get the correct layout? > I feel very confused. > Yeah, you're running into bug 5616 alright - we don't know exactly what causes it. If we use the SGX driver from Nokia N900 + it's libraries, the problem does not manifest. Could you note down the version of SGX drivers/GFX package you use in the bug report? BR Carsten Munk ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] why my text display scratched
Hi Carsten: GFX version is the latest:GFX_4_00_00_01_libs.tar.gz. Meego1.1 handset. But if I use Xlib create window, and use userdefined font, we can render text correctly. Browser I think may also use their own font. How about your QT application? B.R Leo 2010/11/24 Carsten Munk > >> 2010/11/24 Leo : > >> > http://bugs.meego.com/show_bug.cgi?id=5616 > >> > please look at this bug, I found there is a bug same as mine > > 2010/11/24 Leo : > > My device is devkit8000, CPU->OMAP3530, > >-600-MHz ARM Cortex-A8 Core > >-412-MHz TMS320C64x+ DSP Core > > > > Here is details about hardware: > > http://www.armkits.com/Product/devkit8000.asp > > > > I launch the browser, it's good! I'm not familiar with the Gecko/Fennec, > > But I have some experience with webkit, As I know, Webkit will do its > > layout and > > use the cairo/skia/gdk... to generate its pixbuf, then copy to GPU or the > > framebuffer to ask for render. > > And consider the situation I talked, it means we can draw the pixbuf > > correctly. > > > > If the text is not ok, why browser can get the correct layout? > > I feel very confused. > > > > Yeah, you're running into bug 5616 alright - we don't know exactly > what causes it. If we use the SGX driver from Nokia N900 + it's > libraries, the problem does not manifest. > > Could you note down the version of SGX drivers/GFX package you use in > the bug report? > > BR > Carsten Munk > ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] why my text display scratched
>> 2010/11/24 Leo : >> > http://bugs.meego.com/show_bug.cgi?id=5616 >> > please look at this bug, I found there is a bug same as mine 2010/11/24 Leo : > My device is devkit8000, CPU->OMAP3530, > -600-MHz ARM Cortex-A8 Core > -412-MHz TMS320C64x+ DSP Core > > Here is details about hardware: > http://www.armkits.com/Product/devkit8000.asp > > I launch the browser, it's good! I'm not familiar with the Gecko/Fennec, > But I have some experience with webkit, As I know, Webkit will do its > layout and > use the cairo/skia/gdk... to generate its pixbuf, then copy to GPU or the > framebuffer to ask for render. > And consider the situation I talked, it means we can draw the pixbuf > correctly. > > If the text is not ok, why browser can get the correct layout? > I feel very confused. > Yeah, you're running into bug 5616 alright - we don't know exactly what causes it. If we use the SGX driver from Nokia N900 + it's libraries, the problem does not manifest. Could you note down the version of SGX drivers/GFX package you use in the bug report? BR Carsten Munk ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] why my text display scratched
My device is devkit8000, CPU->OMAP3530, -600-MHz ARM Cortex-A8 Core -412-MHz TMS320C64x+ DSP Core Here is details about hardware: http://www.armkits.com/Product/devkit8000.asp I launch the browser, it's good! I'm not familiar with the Gecko/Fennec, But I have some experience with webkit, As I know, Webkit will do its layout and use the cairo/skia/gdk... to generate its pixbuf, then copy to GPU or the framebuffer to ask for render. And consider the situation I talked, it means we can draw the pixbuf correctly. If the text is not ok, why browser can get the correct layout? I feel very confused. 2010/11/24 Carsten Munk > 2010/11/24 Leo : > > http://bugs.meego.com/show_bug.cgi?id=5616 > > please look at this bug, I found there is a bug same as mine. > > > > > Could you tell what device (specifically, what SoC/chipset?) this is from? > > /Carsten > ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] why my text display scratched
2010/11/24 Leo : > http://bugs.meego.com/show_bug.cgi?id=5616 > please look at this bug, I found there is a bug same as mine. > > Could you tell what device (specifically, what SoC/chipset?) this is from? /Carsten ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] why my text display scratched
Am Mittwoch, den 24.11.2010, 10:54 +0800 schrieb Leo: >After I do a workaround to fix touchscreen's problem. I can touch > main menu to enter the application. > But there's problem when app launched, the text is always scratched, > but I found the image is ok. > Please look at the my meego screen snap! Can't recognize much on your picture (for future reference, better quality and uploading it somewhere & posting the URL to it is welcome), but did you trying using another font already? andre -- Andre Klapper (maemo.org bugmaster) ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
