Pineview is not supported by Mesa as it has a PowerVR GPU. While Mesa is looking to support PowerVR, it's just not there yet and will likely skip Intel-integrated PowerVR GPUs.I do recall a Pineview driver in one of the older Intel BSPs, but support for that was abandoned long ago, even Intel private drivers for Atom N450, etc won't work with modern Android versions. In fact, I suspect the SGX53x line would run too poorly to be worth the effort under Lollipop.However, the GL_INVALID_ENUM indicates that the Mesa driver isn't binding to Intel GPUs. I was getting that same error when I tested a stock Lollipop repo-based build that I did a night or two ago. So, I think Mesa 10.4 builds aren't locking onto the Intel GPU.I have requested a sitrep on Intel support for Mesa under Lollipop Android kernels. It was supported under KitKat, even after Android-IA switched to UFO prebuilds. I'm waiting to hear back and will share once I do. We obviously at Team Console want to see that happen.Christopher PriceOn Thu, Jan 22, 2015 at 2:02 PM, Mauro Rossi <issor...@gmail.com> wrote:Hi meerio,thanks, from the snapshot is possible to see the error is 0x500 (GL_INVALID_ENUM).
I get the same error on ITX board Jetway NF96FL-525-LF with Intel Pineview chipset.If you want to practice with logs you can find here a compact procedure:Mauro
Il giorno giovedì 22 gennaio 2015 19:37:21 UTC+1, Meerio ha scritto:sorry pstiglia but i'm very noob :(how can i attach the file here if the system doesn't boot? ( do i have to mount manually an usb key and use cp? i don't know how but i'm willing to learn)in the mean time i attach a screenshoot of the command you gave me
Il giorno giovedì 22 gennaio 2015 10:55:31 UTC+1, pstglia ha scritto:If possible, anyone could test this img on hw with Intel based GPUs?If it doesn't work, please provide logcat file (/data/log.txt if booting under debug mode).If the entire file can't be attached, at least this output:cd /data/grep -iE "mesa|0x50" log.txt | tail -40Thanks in advancePstglia--
You received this message because you are subscribed to a topic in the Google Groups "Android-x86" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/android-x86/VL7asaRnvCY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to android-x86...@googlegroups.com.
To post to this group, send email to andro...@googlegroups.com.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Hi friends,After some efforts, Emil Velikov, Mauro Rossi and me finally got intel classic drivers working on Mesa 10.4.0 under Android-x86Some changes/hacks were necessary in order to make it work (put the worst and the buggy ones on my account :D ). One of them was crucial to enable display: disabling a check on src/mesa/drivers/dri/i965/intel_tex_image.c that forced a GL_INVALID_OPERATION (retcode 0x502) on every attempt to map a image/texture to display on screen (see commit 23291b05ca7885047eb908cf3e19746ee43d00db). As this check doesn't exists on 9.2.0 (The current version used by Android-x86) I thought we can live without it while someone provides the correct solution (maybe some dependency).To compile this, You'll have to replace/change 2 components and include a new one (in fact is not new - libpciaccess):1) external/mesa (remove 9.2.0 and use the one on link bellow):2) external/drm (revert commit "android: intel: disable drm_intel_get_aperture_sizes" - this is required for this build)3) You'll need libpciaccess, that is available on android-ia:If everything goes as expected, You'll have a build with mesa 10.4 to play around, support new hardware, discover new bugs... :)Here's a testing ISO in case anyone wants it (tested on a IvyBridge core i5 - worked for basic functions, Antutu & Candy Crush Soda):As usual, try it at your own risk, this is serious. You can lose data and even your hardware due potential bugs that may be included with these changes...Thanks:Chih-Wei Huang for Android-x86 project.Mauro Rossi and Emil Velikov for their changes on Mesa code (many pushed upstream)AMD A10 5800K for compiling all this stuff for me :)And everyone else who likes and support this open source project
I know this is not a technical question, but are there any advantages in using mesa 10.4 over 9.2 on an already supported hw( like my gma 3150)? i'll do my test, even i'm not shure if the benchmarks are the proper tool to test this kind of changes!
ok, my apologies, it seems that mesa 10.4 can't even boot my netbook, probably due to my gpu
--