Hardware Acceleration For intels GM950

[Windsor Kitaka]

How to enable, i figured it wasn't enabled, when i tried the camera
app it started showed a preview for like 1 sec, and it crashed on me.
So i checked out the logcat, and i saw this. its kind of self
explanatory

LOGCAT ERROR MESSAGE:
I/ActivityManager( 2409): Starting activity: Intent
{ act=android.intent.action.MAIN
cat=[android.intent.category.LAUNCHER] flg=0x10200000
cmp=com.android.camera/.Camera }
I/ActivityManager( 2409): Start proc com.android.camera for activity
com.android.camera/.Camera: pid=7478 uid=10035 gids={1006, 1015}
D/CameraHardware( 7445): PREVIEW SIZE: w=640 h=480 framerate=15
D/Camera ( 7478): app passed NULL surface
E/CameraSettings( 7478): No supported picture size found
D/CameraHardware( 7445): PREVIEW SIZE: w=640 h=480 framerate=15
V/camera ( 7478): startPreview
I/ActivityManager( 2409): Displayed activity
com.android.camera/.Camera: 710 ms (total 710 ms)
W/OrientationEventListener( 7478): Cannot detect sensors. Not enabled
D/dalvikvm( 7478): GC_EXTERNAL_ALLOC freed 1701 objects / 110608 bytes
in 26ms
D/libEGL ( 7478): egl.cfg not found, using default config
D/libEGL ( 7478): loaded /system/lib/egl/libGLES_android.so
D/libEGL ( 7478): 3D hardware acceleration is disabled
W/dalvikvm( 7478): threadid=7: thread exiting with uncaught exception
(group=0xb5892290)
E/AndroidRuntime( 7478): FATAL EXCEPTION: GLThread 10
E/AndroidRuntime( 7478): java.lang.IllegalArgumentException: No
configs match configSpec
E/AndroidRuntime( 7478): at android.opengl.GLSurfaceView
$BaseConfigChooser.chooseConfig(GLSurfaceView.java:760)
E/AndroidRuntime( 7478): at android.opengl.GLSurfaceView
$EglHelper.start(GLSurfaceView.java:916)
E/AndroidRuntime( 7478): at android.opengl.GLSurfaceView
$GLThread.guardedRun(GLSurfaceView.java:1246)
E/AndroidRuntime( 7478): at android.opengl.GLSurfaceView
$GLThread.run(GLSurfaceView.java:1116)
W/ActivityManager( 2409): Force finishing activity
com.android.camera/.Camera
V/camera ( 7478): stopPreview
W/ActivityManager( 2409): Activity pause timeout for
HistoryRecord{ae3b3a60 com.android.camera/.Camera}
D/MobileDataStateTracker( 2409): default Received state= DISCONNECTED,
old= DISCONNECTED, reason= radioTurnedOff, apnTypeList= default
I/Process ( 7478): Sending signal. PID: 7478 SIG: 9
I/WindowManager( 2409): WIN DEATH: Window{ae3b7050 OnScreenHint
paused=false}
I/WindowManager( 2409): WIN DEATH: Window{ae3de320 SurfaceView
paused=false}
I/ActivityManager( 2409): Process com.android.camera (pid 7478) has
died.
I/WindowManager( 2409): WIN DEATH: Window{ae33f890 com.android.camera/
com.android.camera.Camera paused=false}
I/WindowManager( 2409): WIN DEATH: Window{ae35a1f0 SurfaceView
paused=false}

[Arobase40]

If I do recall you have a custom device so you may have to get the
informations from the different existing targets in the tree (viliv or
such), and do a mix according to your hardwares... ^^

[Shady]

Hello,

Does this mean that the intel 950 graphics card is supported? Is it
the same as the 915 driver? Or am I asking the wrong questions at the
wrong post?

Am using a lenovo idea pad... and it uses the intel 950 card... the
915 driver is loaded... the interface is responsive but video playback
(and the gallery are so so slow)

[Arobase40]

Intel 950 chipset is a different one (some kind of a subset of the
915), and even though if 915 driver is loaded and sounds to work at
the UI, if you look at the above log, HW acceleration is disabled !!!
That explains why everything else is so slow : try to have a look at
the Photos Gallery if you have some on an SD Card and at the Webcam as
well.

This is the case with any Froyo builds without i950 chipset support :
they works mostly as if in Vesa mode.

For Gingerbread, you have to same problem in addition that GB does not
support Mesa nor Drm... ^^

[Windsor Kitaka]

first of what is this commands function

TARGET_HARDWARE_3D ?= false

and i have done some serious research on the whole gm950 hardware
acceleration support, and havent come up with much, although i did
pick this up

http://groups.google.com/group/android-x86/browse_thread/thread/edc575b103bcf30f

one guy went with the i915 approach not sure, this is of any value, or
is there a specific driver for gm950?

[Arobase40]

Will you compare to what have been done on 2009, with what exists
actually with the viliv target in the latest Froyo version ? lol

As I said, what you have to do is to use the existing targets ! ;-)

Otherwise you will waste your time in research with out dated or
expired codes.

I gave you the clues and you can do want you want with them... ^^

On 21 juin, 07:23, Windsor Kitaka <w.kit...@gmail.com> wrote:
> first of what is this commands function
>
> TARGET_HARDWARE_3D ?= false
>
> and i have done some serious research on the whole gm950 hardware
> acceleration support, and havent come up with much, although i did
> pick this up
>

> http://groups.google.com/group/android-x86/browse_thread/thread/edc57...

[Douglas Santillan]

i915 should work ok for GMA950

build/target/board/generic-x86/BoardConfig.mk

TARGET_HARDWARE_3D ?= true    <----- change to true

BOARD_USES_I915 := true                 <----- uncomment, same goes for wpa supplicant

while on that folder, may be a plus getting minfree tweaked, I use x6 values on 1GB memory

build/target/board/generic-x86/init.rc  (3 sections modified)

    setprop ro.FOREGROUND_APP_MEM 9216

    setprop ro.VISIBLE_APP_MEM 12288

    setprop ro.SECONDARY_SERVER_MEM 24576

    setprop ro.BACKUP_APP_MEM 24576

    setprop ro.HOME_APP_MEM 24576

    setprop ro.HIDDEN_APP_MEM 30720

    setprop ro.CONTENT_PROVIDER_MEM 33792

    setprop ro.EMPTY_APP_MEM 36864

    write /sys/module/lowmemorykiller/parameters/minfree 9216,12288,24576,30720,33792,36864

other useful tweak, regarding memory and power

    write /proc/sys/vm/dirty_expire_centisecs 0

    write /proc/sys/vm/dirty_background_ratio 60

device/xxx/yyy/BoardConfig.mk             xxx: asus yyy:eeepc

BOARD_USES_I915C := true      <----   mesa classic, seems that i915G / Gallium is not ready 

device/xxx/yyy/xxx_defconfig   (4 sections modified)

CONFIG_DRM_I915=y

CONFIG_DRM_I915_KMS=y

while on that file

modify CPU scaling sections for ondemand governor

CONFIG_CPU_FREQ=y

CONFIG_CPU_FREQ_TABLE=y

# CONFIG_CPU_FREQ_DEBUG is not set

CONFIG_CPU_FREQ_STAT=y

# CONFIG_CPU_FREQ_STAT_DETAILS=y

# CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set

# CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE=y

# CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE=y

CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y

# CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE=y

# CONFIG_CPU_FREQ_DEFAULT_GOV_INTERACTIVE is not set

# CONFIG_CPU_FREQ_GOV_PERFORMANCE=y

# CONFIG_CPU_FREQ_GOV_POWERSAVE=y

# CONFIG_CPU_FREQ_GOV_USERSPACE=y

CONFIG_CPU_FREQ_GOV_ONDEMAND=y

# CONFIG_CPU_FREQ_GOV_INTERACTIVE is not set

# CONFIG_CPU_FREQ_GOV_CONSERVATIVE=y

# CONFIG_X86_PCC_CPUFREQ is not set

CONFIG_X86_ACPI_CPUFREQ=y

# CONFIG_X86_POWERNOW_K6 is not set

# CONFIG_X86_POWERNOW_K7 is not set

# CONFIG_X86_POWERNOW_K8 is not set

# CONFIG_X86_GX_SUSPMOD is not set

# CONFIG_X86_SPEEDSTEP_CENTRINO is not set

CONFIG_X86_SPEEDSTEP_ICH=y

# CONFIG_X86_SPEEDSTEP_SMI=y

# CONFIG_X86_P4_CLOCKMOD=y

# CONFIG_X86_CPUFREQ_NFORCE2 is not set

# CONFIG_X86_LONGRUN is not set

# CONFIG_X86_LONGHAUL is not set

# CONFIG_X86_E_POWERSAVER is not set

get atom processor up

CONFIG_MATOM=y 

comment CONFIG_MPENTIUM4=y

-------

confirm 3D is up via glinfo from the market

market works fine without fingerprint tweaks using this Archos pack

http://code.google.com/p/archos-apps-installer/downloads/list

just modify build.prop from test-keys to release-keys

add/modify lines to turn jit on, and play with the heap size, 64Mb work fine

dalvik.vm.heapsize=64m

dalvik.vm.execution-mode=int:jit

dalvik.vm.stack-trace-file=/data/anr/traces.txt

----

basically:

915 kernel kms suport is turned on 

on top of that, 915c follows tuning drm with gem and opengles

the other tweaks are just extra, but should make things work better

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To post to this group, send email to andro...@googlegroups.com.
To unsubscribe from this group, send email to android-x86...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.

[Arobase40]

OOops, my mistake ! I did a mismatch between I950 and Intel Poulsbo
GMA500 !!! ^^ :p

Thanks for correcting and the input.

I guess I need to sleep a little longer... lol

> market works fine without fingerprint tweaks using this Archos packhttp://code.google.com/p/archos-apps-installer/downloads/list

>
> just modify build.prop from test-keys to release-keys
> add/modify lines to turn jit on, and play with the heap size, 64Mb work fine
> dalvik.vm.heapsize=64m
> dalvik.vm.execution-mode=int:jit
> dalvik.vm.stack-trace-file=/data/anr/traces.txt
>
> ----
>
> basically:
>
> 915 kernel kms suport is turned on
> on top of that, 915c follows tuning drm with gem and opengles
>
> the other tweaks are just extra, but should make things work better
>

> On Mon, Jun 20, 2011 at 11:23 PM, Windsor Kitaka <w.kit...@gmail.com> wrote:
> > first of what is this commands function
>
> > TARGET_HARDWARE_3D ?= false
>
> > and i have done some serious research on the whole gm950 hardware
> > acceleration support, and havent come up with much, although i did
> > pick this up
>

> >http://groups.google.com/group/android-x86/browse_thread/thread/edc57...

[Chih-Wei Huang]

Thank you for sharing.

2011/6/22 Douglas Santillan <capri...@gmail.com>:

> i915 should work ok for GMA950
> build/target/board/generic-x86/BoardConfig.mk
> TARGET_HARDWARE_3D ?= true    <----- change to true
> BOARD_USES_I915 := true                 <----- uncomment, same goes for wpa

Nice doc, except these changes.

TARGET_HARDWARE_3D, BOARD_USES_I915
are unused now, so no need to change that.

--
Chih-Wei
Android-x86 project
http://www.android-x86.org

[Douglas Santillan]

Anytime! Actually thank you and all the  passionate bunch who contribute to this list. I am new pretty to Android and reading here has helped a lot. I was wondering what was that Poulsbo for. 

another piece that may help regarding system responsiveness is init.rc on /system/core/rootdir

    write /proc/sys/kernel/sched_latency_ns 900000

    write /proc/sys/kernel/sched_wakeup_granularity_ns 550000

since lowering those values, processes seem more responsive. 

there was also a value which I changed on the kernel from 4 to 2 (signal to fix), which had to do with stack compatibility / cpu alignment, supposedly not required, leading to less force quits on applications, however I cannot remember where I modified it. I should keep a change log somewhere. 

[Arobase40]

On 21 juin, 20:30, Douglas Santillan <capricor...@gmail.com> wrote:
> Anytime! Actually thank you and all the  passionate bunch who contribute to
> this list. I am new pretty to Android and reading here has helped a lot. I
> was wondering what was that Poulsbo for.

Well Poulsbo GMA500 was an f*** GPU integrated onto the chipset itself
and and integrated in some netbooks such as the MSI Wind U115 Hybrid,
Dell Mini, Packard Bell Dot M, Acer Aspire One 751h, Sony Vaio P,
Viliv S5, ...

It was supposed to add improvement over other GPU and chipsets. The
sole problem is that Intel just decided to not support it : most Win x
drivers are quite old, and Linux or Android drivers are mostly hacked
versions...
There were also confusing news about GMA500 support with Meego.... ^^
I coudn't even get my hand on the global Meego git tree, just sparsed
rpm files, and the building process just need a Suse distribution if
I'm not wrong.

If you want to know more about Poulsbo GMA500 :

http://www.netbookmarket.net/intel-gma950-vs-gma500/

On the other hand if you have some tricks to get HW acceleration with
the 945GM , you're welcome ! :-) I'm stuck on Vesa mode and of course
HW Acceleration disabled ! :(

Arobase

>
> another piece that may help regarding system responsiveness is init.rc on
> /system/core/rootdir
>
>     write /proc/sys/kernel/sched_latency_ns 900000
>     write /proc/sys/kernel/sched_wakeup_granularity_ns 550000
>
> since lowering those values, processes seem more responsive.
>
> there was also a value which I changed on the kernel from 4 to 2 (signal to
> fix), which had to do with stack compatibility / cpu alignment, supposedly
> not required, leading to less force quits on applications, however I cannot
> remember where I modified it. I should keep a change log somewhere.
>

> ...
>
> plus de détails »

[Douglas Santillan]

Aero, 

GMA900 and GMA950 should work just fine with i915C (kernel mode setting in general, not just 915 chipsets). 

As I understand it, activating the  module and  KMS for 915 in the kernel is just the entry point for mesa drivers. i915C is mesa classic which is working, it should support GMA900 being chipsets 910 and 915, GMA950 covers 945s, I think. i915G activates Gallium. However, mesa pages I read do not indicate that Intel Gallium portions are done, just ATI and NVIDIA, if I remember it correct. I tried to compile i915G but I got to a wall where the compiler just quit with an error 1, perhaps I am missing  dev packages for mesa, not sure. 

For 945, in theory, Graphics support section of defconfig should look something like this

CONFIG_AGP=y

# CONFIG_AGP_ALI is not set

# CONFIG_AGP_ATI is not set

# CONFIG_AGP_AMD is not set

# CONFIG_AGP_AMD64 is not set

CONFIG_AGP_INTEL=y

# CONFIG_AGP_NVIDIA is not set

# CONFIG_AGP_SIS is not set

# CONFIG_AGP_SWORKS is not set

# CONFIG_AGP_VIA is not set

# CONFIG_AGP_EFFICEON is not set

CONFIG_VGA_ARB=y

CONFIG_VGA_ARB_MAX_GPUS=4

# CONFIG_VGA_SWITCHEROO is not set

CONFIG_DRM=y

CONFIG_DRM_KMS_HELPER=y

# CONFIG_DRM_TDFX is not set

# CONFIG_DRM_R128 is not set

# CONFIG_DRM_RADEON is not set

# CONFIG_DRM_I810 is not set

# CONFIG_DRM_I830 is not set

CONFIG_DRM_I915=y

CONFIG_DRM_I915_KMS=y

# CONFIG_DRM_MGA is not set

# CONFIG_DRM_SIS is not set

# CONFIG_DRM_VIA is not set

# CONFIG_DRM_SAVAGE is not set

CONFIG_STUB_POULSBO=m

# CONFIG_VGASTATE is not set

CONFIG_VIDEO_OUTPUT_CONTROL=y

CONFIG_FB=y

# CONFIG_FIRMWARE_EDID is not set

# CONFIG_FB_DDC is not set

CONFIG_FB_BOOT_VESA_SUPPORT=y

CONFIG_FB_CFB_FILLRECT=y

CONFIG_FB_CFB_COPYAREA=y

CONFIG_FB_CFB_IMAGEBLIT=y

# CONFIG_FB_CFB_REV_PIXELS_IN_BYTE is not set

# CONFIG_FB_SYS_FILLRECT is not set

# CONFIG_FB_SYS_COPYAREA is not set

# CONFIG_FB_SYS_IMAGEBLIT is not set

# CONFIG_FB_FOREIGN_ENDIAN is not set

# CONFIG_FB_SYS_FOPS is not set

# CONFIG_FB_WMT_GE_ROPS is not set

# CONFIG_FB_SVGALIB is not set

# CONFIG_FB_MACMODES is not set

# CONFIG_FB_BACKLIGHT is not set

CONFIG_FB_MODE_HELPERS=y

CONFIG_FB_TILEBLITTING=y

Framebuffer section should disable all modes, like this

# CONFIG_FB_CIRRUS is not set

# CONFIG_FB_PM2 is not set

# CONFIG_FB_CYBER2000 is not set

# CONFIG_FB_ARC is not set

# CONFIG_FB_ASILIANT is not set

# CONFIG_FB_IMSTT is not set

# CONFIG_FB_VGA16 is not set

# CONFIG_FB_UVESA=m

# CONFIG_FB_VESA=y

# CONFIG_FB_N411 is not set

# CONFIG_FB_HGA is not set

# CONFIG_FB_S1D13XXX is not set

# CONFIG_FB_NVIDIA is not set

# CONFIG_FB_RIVA is not set

# CONFIG_FB_I810 is not set

# CONFIG_FB_LE80578 is not set

# CONFIG_FB_INTEL=y

# CONFIG_FB_MATROX is not set

# CONFIG_FB_RADEON is not set

# CONFIG_FB_ATY128 is not set

# CONFIG_FB_ATY is not set

# CONFIG_FB_S3 is not set

# CONFIG_FB_SAVAGE is not set

# CONFIG_FB_SIS is not set

# CONFIG_FB_VIA is not set

# CONFIG_FB_NEOMAGIC is not set

# CONFIG_FB_KYRO is not set

# CONFIG_FB_3DFX is not set

# CONFIG_FB_VOODOO1 is not set

# CONFIG_FB_VT8623 is not set

# CONFIG_FB_TRIDENT is not set

# CONFIG_FB_ARK is not set

# CONFIG_FB_PM3 is not set

# CONFIG_FB_CARMINE is not set

# CONFIG_FB_GEODE is not set

# CONFIG_FB_TMIO is not set

# CONFIG_FB_UDL is not set

# CONFIG_FB_VIRTUAL is not set

# CONFIG_FB_METRONOME is not set

# CONFIG_FB_MB862XX is not set

# CONFIG_FB_BROADSHEET is not set

CONFIG_BACKLIGHT_LCD_SUPPORT=y

CONFIG_LCD_CLASS_DEVICE=y

# CONFIG_LCD_PLATFORM is not set

CONFIG_BACKLIGHT_CLASS_DEVICE=y

CONFIG_BACKLIGHT_GENERIC=y

# CONFIG_BACKLIGHT_PROGEAR is not set

# CONFIG_BACKLIGHT_MBP_NVIDIA is not set

# CONFIG_BACKLIGHT_SAHARA is not set

# CONFIG_BACKLIGHT_ADP8860 is not set

Make sure you have BOARD_USES_I915C := true in /device/xxx/yyy/BoardConfig.mk

UVESA_MODE=${UVESA_MODE:-1024x600} in xxxx_info file

Once the iso starts, you should notice that verbose is interrupted momentarily and resolution adjusted to a finer mode, that should mean it is going well. 

I hope it works. 

[Arobase40]

On 21 juin, 22:45, Douglas Santillan <capricor...@gmail.com> wrote:
> Aero,
>
> GMA900 and GMA950 should work just fine with i915C (kernel mode setting in
> general, not just 915 chipsets).
>
> As I understand it, activating the  module and  KMS for 915 in the kernel is
> just the entry point for mesa drivers. i915C is mesa classic which is
> working, it should support GMA900 being chipsets 910 and 915, GMA950 covers
> 945s, I think. i915G activates Gallium. However, mesa pages I read do not
> indicate that Intel Gallium portions are done, just ATI and NVIDIA, if I
> remember it correct. I tried to compile i915G but I got to a wall where the
> compiler just quit with an error 1, perhaps I am missing  dev packages for
> mesa, not sure.

Well, all your explanations about Atom based GPU chipsets, I can't
tell much as AFAIK everything (or mostly) are already working fine
with the latest build tree version, called FRG83G, and I don't work
much with these chipsets. I have tested most builds based on FRG83G
with some netbooks such as MSI U100+ or Asus N10Jb with GMA950 and no
isssues.

The problems come up with Intel Notebook with other other CPU than
Atom, such as Fujitsu P1610, Asus U1F, Acer Aspire 1825ptz (same size
than Netbook but not really Netbook due to the CPU and the GPU, as I
had no display at all !!!

With the previous tree version based named as Master (2.2.1), I got
display and functional with the Acer Aspire 1825ptz with HW, while
this is not the case with Fujitsu P1610 and Asus U1F with which I only
have Vesa mode, and so no HW acceleration (both based on the same GPU
chipset : 945GM). Got the same result with latest Android-x86 version.

I tried your settings but I have no display at all with the P1610, and
only Vesa mode with some changes with the Asus U1F. Sounds like the
settings you proposed were made on a Atom based devices basis while
the two latter ones are not ! Then there are some mistakes as some
drivers you compiled as integrated have to be compiled as modules.
Then the setting "BOARD_USES_I915C := true" can't be use as they are
based on I965C.

Finally, the main problem is Mesa, as you quoted, some codes for these
chipsets are not really implemented or buggy. I have another theory I
have to verify is the Mesa gralloc implementation which sounds to be
buggy as well. I have some clues after watching the logcat with the
945GM chipset and I have to test them.

If I can't solve this by myself, I hope to get some helps from Chia
from olv.

I'll let you know how it goes... ^^

Best regards,

Arobase

> ...
>
> plus de détails »

[Shady]

Hello

I tried your post to build gingerbread image. It boots and the ui is responsive (however, video playback and the gallery are still slow)

Am running it on a Lenovo ideapad. In ubuntu it says the chipset is 945GME. I managed to get the same results with the generic_x86

What I would like to know, is 3D  supported for this chipset using any combination of settings?

And for the sake of knowledge can someone briefly explain what the terms MESA and DRM  mean? I read somewhere that gingerbread doesn't have mesa and drm implemented. (i could've misunderstood that post)

Hope that the questions aren't too silly... am new to all this 

I would like to contribute in any way... a though at the moment my contribution are limited to running test builds on my netbook (ideapad s10e, Atom with 945GM graphics card).

Thanks in advance

[fuzzy7k]

DRM stands for direct rendering manager and is part of a kernel side
driver. It allows for orderly and direct access to the graphics
hardware. Mesa, I don't think stands for anything but is just a
project name. It is an open source repository for user space drivers
used by X. Android does not use X, thus the mesa drivers are not
directly usable and mesa must be ported to android to utilize those
drivers already written. The process of porting is still under way.
Most of the work in froyo is done, but not all. I believe the focus
has shifted to the yet to be released honycomb, thus, we may never see
mesa support in gingerbread.

[Arobase40]

http://en.wikipedia.org/wiki/Mesa_3D_%28OpenGL%29

http://en.wikipedia.org/wiki/Direct_Rendering_Infrastructure

And in regard with Gingerbread-x86, as already stated Mesa and DRM are
not supported, the reason why everything is so slow with every x86
devices.

[Shady]

Thanks for the explanation!!
The gingerbread generic_x86 is working great so far, even some opengl test apps do work, although with low frame rate

What I need help with is video playback ... I would be greatly thankful if anybody can point me in the right direction.
The framerate is very low making videos unwatchable.. any way of improving that? Or should I just give up?

That is my priority at the moment. Other items are Camera (which worked in Froyo), the Mic (which I can see is detected in the logs and the alsa_amixer), Bluetooth (which is also deteceted, but refuses to turn on, also worked in Foryo) but these would be better discussed in another post

Willing to try anything... just don't know what to try..

Thanks in advance

[Arobase40]

I'm not quite positive but I don't think you will find any video
playback apps unless someone takes the time to rebuild a RockPlayer or
MoboPlayer OpenGL version compatible with x86 devices.
Still waiting also after VLC Player version... ^^

[Douglas Santillan]

Aero,

GPUs may be used with different processors, it depends on the
chipset's specs, compatibility and in laptops manufacturer's choice.

Please accept my apologies as I did not provide info about the tree I
am tinkering with, being Froyo 2.2.2 FRG83G repoed on 20110515.

Mesa's site is http://www.mesa3d.org there is a lot of information there.

GMA900, GMA 950 families and GMA 3000/3100  GPUs use i915 as per
http://dri.freedesktop.org/wiki/Intel?action=show&redirect=IntelGMA.
i965 is for chipsets 965G, G31, G33, G35 the GMAX series, being GMA
X3000, GMA X3100, GMA X3500 and GMA X4500. Mesa classic and Gallium
are two different approaches for graphics acceleration.

945s should use i915C, mesa classic, or i915G, mesa with Gallium, or
at least that is how interpret the code I see in the tree.

Now, gralloc... It is not a part of Mesa libs. As I see it, it is an
approach to ID and integrate Gem DRI to get DRM going. DRM folder IDs
and patches code for the GPU, intel's case xf86.DRI+EGL surely allows
OpenGL acceleration, I am not sure about OpenGL ES, it should,
somehow.

Reading code from the tree. /Android-x86/external/mesa... There is a
make file which seems to lead to some of the reported no acceleration
issues:
/Android-x86/external/mesa/src/egl/Android.mk
MESA_BUILD_CLASSIC section LOCAL_CFLAGS seems flat, I think that a
-DFEATURE_GL=1 \ is missing setting OpenGL acceleration and/or
-DFEATURE_ES1=1 \ for OpenGL ES. I will test as soon as I have some
time.

MESA_BUILD_GALLIUM section seems empty and I do not understand yet how
that code produces
libmesa_st_egl
libmesa_egl
libmesa_st_mesa
libmesa_pipe
libmesa_winsys_device
libmesa_gallium

If you are getting no video with i915C, try changing grub boot line
adding video=-16, that may do it. i915 is the correct match, I am
uncertain why it does not work for those two devices, may even be the
DPI setting being passed.

Core solo and duo, should use CONFIG_MPENTIUMM instead of MATOM or
MPENTIUM4, and CONFIG_NR_CPUS=1 or 2 as needed. Also tweak governors
via centrino speedstep, I guess.

Hopefully somebody will figure things out.

Good luck !

[Arobase40]

Hi Doug,

> GPUs may be used with different processors, it depends on the
> chipset's specs, compatibility and in laptops manufacturer's choice.
>
> Please accept my apologies as I did not provide info about the tree I
> am tinkering with, being Froyo 2.2.2 FRG83G repoed on 20110515.

There is no problem with this, as, as I already mentioned I get
exactly the same issue whether with Froyo 2.2.2 (FRG83G) or Froyo
2.2.1 (MASTER ?) for 945GM.

>
> Mesa's site is http://www.mesa3d.org there is a lot of information there.

I already know the Mesa's site, but it doesn't really help as this is
the generic one, and not related to Android-x86.

>
> GMA900, GMA 950 families and GMA 3000/3100  GPUs use i915 as perhttp://dri.freedesktop.org/wiki/Intel?action=show&redirect=IntelGMA.

> i965 is for chipsets 965G, G31, G33, G35 the GMAX series, being GMA
> X3000, GMA X3100, GMA X3500 and GMA X4500. Mesa classic and Gallium
> are two different approaches for graphics acceleration.
>
> 945s should use i915C, mesa classic, or i915G, mesa with Gallium, or
> at least that is how interpret the code I see in the tree.

I know more or less all of this as I got an in depth look at the Mesa
source code for some months now and tried to figure out what was the
problem between the previous version and the new one. I already
reported some bugs and issues on this group.

Since now, I just focused on the i965 code part, and specially for the
GMA4500HD, as I was mostly working on the Acer Aspire (1825PTZ)
target.

I then discovered this new problem with 945GM when I tried to create a
new target for the Fujitsu P1610 when Stefan releases the code for the
serial wacom touchscreen and as there were demands for the Fujitsu
P1510 (mostly the same as P1610) device.
I though that using the older source code (Froyo 2.2.1), there should
not be a problem. alas...

>
> Now, gralloc... It is not a part of Mesa libs. As I see it, it is an
> approach to ID and integrate Gem DRI to get DRM going. DRM folder IDs
> and patches code for the GPU, intel's case xf86.DRI+EGL surely allows
> OpenGL acceleration, I am not sure about OpenGL ES, it should,
> somehow.

About gralloc, I'm talking about this portion of code in /external/
mesa/src/gralloc/*

As When I logcat I got different references about issues with
gralloc !

I can't remember them all, as after installing ATI proprietary driver
it broke my host system a second time and I partially lost my previous
def config files for the P1610 target, so I'm trying to recover them
from the backup... ^^
At least, my actual build target is not working anymore with the P1610
device (no display at all whether in MDPI or Vesa mode) but partially
with the Asus U1F in vesa mode, and the messages I got from logcat
refers to :

I/SurfaceFlinger (1517) : SurfaceFlinger's main thread ready to run.
Initializing graphics H/W...
W/gralloc (1517) page flipping not supported (yres_virtual=600,
requested=1200
I/gralloc (1517) using (fd=24)
I/gralloc (1517): id = VESA VGA
I/gralloc (1517): xres = 800 px
I/gralloc (1517): yres = 600 px
I/gralloc (1517): xres_virtual = 800 px
I/gralloc (1517): yres_virtual = 600 px
I/gralloc (1517): bpp = 16
I/gralloc (1517): r = 11:5
I/gralloc (1517): g = 5:6
I/gralloc (1517): b = 0:5
I/gralloc (1517): width = 127 mm (160.000000 dpi)
I/gralloc (1517): height = 95 mm (160.421051 dpi)
I/gralloc (1517): refresh rate = 91.11 Hz
D/libEGL (1517): loaded /system/lib/egl/libGLES_android.so
D/libEGL (1517): 3D hardware acceleration is disabled

This is of course a partial log of the actual build, while with the
previous build I got at least 1024x768x16 res while I'm now stuck on
800x600x16... ^^

That's why I first changed the internal gralloc codes with the one
from olv/froyo-next, and got at least a garbled display in MDPI mode,
but still a Vesa display with 1366x768x16 res and of course HW
disabled with the same issue, in regard to logcat :

I/SurfaceFlinger (1517) : SurfaceFlinger's main thread ready to run.
Initializing graphics H/W...
W/gralloc (1517) page flipping not supported (yres_virtual=768,
requested=1536
I/gralloc (1517) using (fd=24)
I/gralloc (1517): id = VESA VGA
I/gralloc (1517): xres = 1366 px
I/gralloc (1517): yres = 768 px
I/gralloc (1517): xres_virtual = 1366 px
I/gralloc (1517): yres_virtual = 768 px
I/gralloc (1517): bpp = 16
I/gralloc (1517): r = 11:5
I/gralloc (1517): g = 5:6
I/gralloc (1517): b = 0:5
I/gralloc (1517): width = 217 mm (159.8991235 dpi)
I/gralloc (1517): height = 122 mm (159.8995081 dpi)
I/gralloc (1517): refresh rate = 65.48 Hz
D/libEGL (1517): loaded /system/lib/egl/libGLES_android.so
D/libEGL (1517): 3D hardware acceleration is disabled

This is at least the native res for the Asus U1F notebook, and not
garbled with my previous (lost) build... ^^
With the previous build, I also got a nice display with 1024x768x16
for the P1610, but again in Vesa...

That's why I announced I just give up the P1510/P1610 project in
another thread.

http://groups.google.com/group/android-x86/browse_thread/thread/534fd3615282fd10/c2f95420f12e9118?lnk=gst&q=P1510#c2f95420f12e9118

But I could change my mind, if anyone has a better idea about the
problem... ^^

> Reading code from the tree. /Android-x86/external/mesa... There is a
> make file which seems to lead to some of the reported no acceleration

> issues, just the res has changed :

> /Android-x86/external/mesa/src/egl/Android.mk
> MESA_BUILD_CLASSIC section LOCAL_CFLAGS seems flat, I think that a
> -DFEATURE_GL=1 \  is missing setting OpenGL acceleration and/or
> -DFEATURE_ES1=1 \ for OpenGL ES. I will test as soon as I have some
> time.
>
> MESA_BUILD_GALLIUM section seems empty and I do not understand yet how
> that code produces
>         libmesa_st_egl
>         libmesa_egl
>         libmesa_st_mesa
>         libmesa_pipe
>         libmesa_winsys_device
>         libmesa_gallium

There are indeed very strange things with that codes ... ^^ ;-)

http://groups.google.com/group/android-x86/browse_thread/thread/c30a72066eb854d3/c4ffefd368d920d9?lnk=gst&q=useless#c4ffefd368d920d9

There was also another thread about these weirdness, but I can
remember the link.

>
> If you are getting no video with i915C, try changing grub boot line
> adding video=-16, that may do it. i915 is the correct match, I am
> uncertain why it does not work for those two devices, may even be the
> DPI setting being passed.

Hmmm, I'll try that, even though I'm a bit suspicious... :)

> Core solo and duo, should use CONFIG_MPENTIUMM instead of MATOM or
> MPENTIUM4, and CONFIG_NR_CPUS=1 or 2 as needed. Also tweak governors
> via centrino speedstep, I guess.

Yes, I already know about these settings as this is what I already
use. :p

Thanks again for thge helps.

Arobase

>
> Hopefully somebody will figure things out.
>
> Good luck !
>

> ...
>
> plus de détails »

[Shady]

So I've reached a dead end with this i945GME chip on my netbook. It's a shame cause android was the only OS that I could use this netbook with.

It came with windows XP: that was too slow and the screen was too small... switch to ubuntu... solved the performance, but the screen was still small for comfortable use

With android, using it was so natural and comfortable... But without being able to watch videos, use the microphone, and camera... i guess it's just too much functionality lost... 

Thank you all for your help!! I will keep following the project.... but I just gave up trying to get the Graphics working properly!