The initial patches to get the screen displayed correctly are below. I
think a similar patch may need to be applied to some of the
applications to get them to display correctly.
> The initial patches to get the screen displayed correctly are below. I > think a similar patch may need to be applied to some of the > applications to get them to display correctly.
> On Aug 2, 8:48 am, mtx512 <mtx51...@gmail.com> wrote: >> Hi,
>> Has anyone worked out the 32bpp fixes for Froyo. The patches for that >> I had for Eclair (EGLDisplaySurface.cpp) won't work in Froyo.
>> many thanks!
> -- > You received this message because you are subscribed to the Google Groups "Android-x86" group. > To post to this group, send email to android-x86@googlegroups.com. > To unsubscribe from this group, send email to android-x86+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.
> On Aug 8, 2010, at 7:41 AM, mtx512 <mtx51...@gmail.com> wrote:
> > The initial patches to get the screen displayed correctly are below. I
> > think a similar patch may need to be applied to some of the
> > applications to get them to display correctly.
> > On Aug 2, 8:48 am, mtx512 <mtx51...@gmail.com> wrote:
> >> Hi,
> >> Has anyone worked out the 32bpp fixes for Froyo. The patches for that
> >> I had for Eclair (EGLDisplaySurface.cpp) won't work in Froyo.
> >> many thanks!
> > --
> > You received this message because you are subscribed to the Google Groups "Android-x86" group.
> > To post to this group, send email to android-x86@googlegroups.com.
> > To unsubscribe from this group, send email to android-x86+unsubscribe@googlegroups.com.
> > For more options, visit this group athttp://groups.google.com/group/android-x86?hl=en.
I assume that you have test this patch somehow, do you mind that I put this patch on to the android-x86.org downloading page? And we could merge it into the foyo tree later. Yi
On Sun, Aug 8, 2010 at 12:54 PM, mtx512 <mtx51...@gmail.com> wrote: > We're still depend on finding a OpenGL ES driver for adequate > performance.
> On Aug 8, 7:17 pm, Yi Sun <beyo...@gmail.com> wrote: >> How about the performance? >> Yi
>> On Aug 8, 2010, at 7:41 AM, mtx512 <mtx51...@gmail.com> wrote:
>> > The initial patches to get the screen displayed correctly are below. I >> > think a similar patch may need to be applied to some of the >> > applications to get them to display correctly.
>> > On Aug 2, 8:48 am, mtx512 <mtx51...@gmail.com> wrote: >> >> Hi,
>> >> Has anyone worked out the 32bpp fixes for Froyo. The patches for that >> >> I had for Eclair (EGLDisplaySurface.cpp) won't work in Froyo.
>> >> many thanks!
>> > -- >> > You received this message because you are subscribed to the Google Groups "Android-x86" group. >> > To post to this group, send email to android-x86@googlegroups.com. >> > To unsubscribe from this group, send email to android-x86+unsubscribe@googlegroups.com. >> > For more options, visit this group athttp://groups.google.com/group/android-x86?hl=en.
> -- > You received this message because you are subscribed to the Google Groups "Android-x86" group. > To post to this group, send email to android-x86@googlegroups.com. > To unsubscribe from this group, send email to android-x86+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.
I'm testing for x86 by building the source from the main repo
(android.git.kernel.org), unfortunately the trunk for froyo has now
been restricted to build a 64 bit OS only. Therefore I'm currently
using the tag android-2.2_r1.1. I'm currently trying to fix
touchscreen for my board as well explore an OpenGL ES solution for
GMA500.
On Aug 9, 5:35 am, Yi Sun <beyo...@gmail.com> wrote:
> I assume that you have test this patch somehow, do you mind that I put
> this patch on to the android-x86.org downloading page? And we could
> merge it into the foyo tree later.
> Yi
> On Sun, Aug 8, 2010 at 12:54 PM, mtx512 <mtx51...@gmail.com> wrote:
> > We're still depend on finding a OpenGL ES driver for adequate
> > performance.
> > On Aug 8, 7:17 pm, Yi Sun <beyo...@gmail.com> wrote:
> >> How about the performance?
> >> Yi
> >> On Aug 8, 2010, at 7:41 AM, mtx512 <mtx51...@gmail.com> wrote:
> >> > The initial patches to get the screen displayed correctly are below. I
> >> > think a similar patch may need to be applied to some of the
> >> > applications to get them to display correctly.
> >> > On Aug 2, 8:48 am, mtx512 <mtx51...@gmail.com> wrote:
> >> >> Hi,
> >> >> Has anyone worked out the 32bpp fixes for Froyo. The patches for that
> >> >> I had for Eclair (EGLDisplaySurface.cpp) won't work in Froyo.
> >> >> many thanks!
> >> > --
> >> > You received this message because you are subscribed to the Google Groups "Android-x86" group.
> >> > To post to this group, send email to android-x86@googlegroups.com.
> >> > To unsubscribe from this group, send email to android-x86+unsubscribe@googlegroups.com.
> >> > For more options, visit this group athttp://groups.google.com/group/android-x86?hl=en.
> > --
> > You received this message because you are subscribed to the Google Groups "Android-x86" group.
> > To post to this group, send email to android-x86@googlegroups.com.
> > To unsubscribe from this group, send email to android-x86+unsubscribe@googlegroups.com.
> > For more options, visit this group athttp://groups.google.com/group/android-x86?hl=en.
On Mon, Aug 9, 2010 at 5:40 AM, mtx512 <mtx51...@gmail.com> wrote: > Yes you can put the patch on android-x86.org.
> I'm testing for x86 by building the source from the main repo > (android.git.kernel.org), unfortunately the trunk for froyo has now > been restricted to build a 64 bit OS only. Therefore I'm currently > using the tag android-2.2_r1.1. I'm currently trying to fix > touchscreen for my board as well explore an OpenGL ES solution for > GMA500.
Just a double confirm, you did tested your patch with android-2.2_r1.1 and it works, right?
> On Mon, Aug 9, 2010 at 5:40 AM, mtx512 <mtx51...@gmail.com> wrote:
> > Yes you can put the patch on android-x86.org.
> > I'm testing for x86 by building the source from the main repo
> > (android.git.kernel.org), unfortunately the trunk for froyo has now
> > been restricted to build a 64 bit OS only. Therefore I'm currently
> > using the tag android-2.2_r1.1. I'm currently trying to fix
> > touchscreen for my board as well explore an OpenGL ES solution for
> > GMA500.
> Just a double confirm, you did tested your patch with android-2.2_r1.1
> and it works, right?
On Mon, Aug 9, 2010 at 1:03 PM, mtx512 <mtx51...@gmail.com> wrote: > Yes have tested, my screen now displays correctly.
> On Aug 9, 7:51 pm, Yi Sun <beyo...@gmail.com> wrote: >> On Mon, Aug 9, 2010 at 5:40 AM, mtx512 <mtx51...@gmail.com> wrote: >> > Yes you can put the patch on android-x86.org.
>> > I'm testing for x86 by building the source from the main repo >> > (android.git.kernel.org), unfortunately the trunk for froyo has now >> > been restricted to build a 64 bit OS only. Therefore I'm currently >> > using the tag android-2.2_r1.1. I'm currently trying to fix >> > touchscreen for my board as well explore an OpenGL ES solution for >> > GMA500.
>> Just a double confirm, you did tested your patch with android-2.2_r1.1 >> and it works, right?
> -- > You received this message because you are subscribed to the Google Groups "Android-x86" group. > To post to this group, send email to android-x86@googlegroups.com. > To unsubscribe from this group, send email to android-x86+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.
It is a way to hard code for 32bpp. That is not good if we want to
support devices which could not support it. Is there a way to
automatically detect current depth and initialize the framebuffer for
it?
On 8月20日, 下午5时16分, Chih-Wei Huang <cwhu...@android-x86.org> wrote:
> It is a way to hard code for 32bpp. That is not good if we want to > support devices which could not support it. Is there a way to > automatically detect current depth and initialize the framebuffer for > it?