search

Jonmhaney / android-x86

Automatically exported from code.google.com/p/android-x86
0 stars 0 forks source link

No hardware acceleration support on ATI RADEON RS690 graphic card #318

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
When booting a froyo 2.2.2 on a board with Ati RADEON RS690 chipset,
with "ro.arch" set up to "mesa" instead of "default",
we have full display support, but without any kind of HW acceleration.

When using "default" mode, or trying to force uvesafb driver, we have same 
issues as in bug #183 (distorted screen, still no HW accel.).

When looking at logcat output,
we clearly see that Mesa driver detects a "r300" chipset, but cannot obtain any 
drm screen :
D/libEGL  ( 1133): loaded /system/lib/egl/libGLES_android.so
D/libEGL  ( 1133): loaded /system/lib/egl/libGLES_mesa.so
W/MESA-EGL( 1133): drm PFO (line:509)
W/MESA-EGL( 1133): drm PFO (line:514)
W/MESA-EGL( 1133): drm PFO (line:517) fd = 4
W/MESA-EGL( 1133): drm PFO (line:523)
W/MESA-EGL( 1133): drm PFO (line:526) name : r300
E/MESA-EGL( 1133): failed to create DRM screen
I/MESA-EGL( 1133): using SW screen

Don't hesitate to ask for more logs.

It appears that r300 drivers are not included into Android's build process, as 
seen into external/mesa sources. Why ? I didn't found any issue mentioning r300 
chipsets..

Best regards,
Ph. FOUQUET

Original issue reported on code.google.com by ph.fouq...@gmail.com on 1 Jun 2011 at 9:26

GoogleCodeExporter commented 8 years ago 
Hi all,

I'm working with Ph. on the same issue,
and we finally obtained hardware acceleration with this Ati RADEON rs690 
chipset, by activating r300/radeon support through the mesa sources.
A patch should be proposed soon.

When booting , we got a spinning logo which is smooth, using HW accel.
(until then, we only obtained SW accel, muuuuch slooooooower.. ;))

Through logcat, we also see that or graphic board is correctly identified and 
initialized by the r300 mesa drivers, recognized as a Gallium/rs690.

However, when using Android, we got some strange graphical issues : 
some portions of the screen seems to be drawn only at half. The area seems to 
be split from top right to bottom left, upper-left part being not updated).
This area should be the whole screen, or only some parts of it : the top status 
bar of android, the web browser buffer, or others...
A screenshot should come early to clarify things.
This "half" portion is shown only on 1 frame to 2 : the screen sometimes blinks 
with full area shown correctly, and this half area with "old" graphical parts, 
such as the starting background (although we have completely booted and started 
android)..
This corresponds to screen refreshes.

I'm wondering if this issue is due to some mess we forgot to add from the r300 
Mesa drivers ?
Did we forget to configure some things ?

Best regards,
Hugues Hiegel.

Original comment by hugues.h...@gmail.com on 15 Jun 2011 at 5:28

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
Hello,

here are some screenshots of the display issues.

Best regards,
Ph. Fouquet.

Original comment by ph.fouq...@gmail.com on 16 Jun 2011 at 9:58

Attachments:

GoogleCodeExporter commented 8 years ago 
Hi!
I have same issue on Android-x86-4.4-RC2. But the area seems to be split from 
top left to bottom tight, upper-right part being not updated

Original comment by MurVla...@gmail.com on 3 Jul 2014 at 7:37

GoogleCodeExporter commented 8 years ago 
Hi!
I have the same issue on Android-x86-4.4-2. Area top left to bottom right not 
updated on Radeon x1250 in Fujitsu Futro.
Please looking for help!

Original comment by Loekie1...@gmail.com on 2 Mar 2015 at 3:20