Current state of Nouveau \ Amd dri android modules?

[Masaykh]

Is there some WIP for these modules?
Or test images?

Looking at this https://groups.google.com/forum/#!topic/android-x86/WkwkrP38M1o%5B176-200%5D thread of Mauro Rossi , in june it was not in working state.

I dont found newer info regarding this matter.

[Mauro Rossi]

Il giorno martedì 27 settembre 2016 13:33:14 UTC+2, Masaykh ha scritto:

Is there some WIP for these modules?
Or test images?

Hi,

marshamallow-x86 released images with mesa 12.0.x are available on main website

nougat-x86 experimental images with latest mesa 12.1.0devel are here, but still under testing:

https://drive.google.com/drive/folders/0B_OFHiIqgpSFMlk4bkhaMnAwbDA

 

Looking at this https://groups.google.com/forum/#!topic/android-x86/WkwkrP38M1o%5B176-200%5D thread of Mauro Rossi , in june it was not in working state.

I dont found newer info regarding this matter.

nouveau is in much better shape thanks to WIP locking patches by Ilia Mirkin

radeon and radeonsi were already stable while for amdgpu I've not received any feedback yet, nor performed tests (no samples)

There is one bug affecting all GPUs but Intel, since RGBA/RGBX is not natively supported by DRI

apps like Basemark ES2 and Rajawali using RGBA/X textures will show black surfaces,

however marshmallow-x86 is working and usable with most of the apps with radeon(si) and nouveau now.

M.

[youling 257]

why i now know 4.8 nougat test link ? 20 days ago, i don't know ； i need 4.8 nougat 27 days ；i only know your 
https://drive.google.com/drive/folders/0B_OFHiIqgpSFaURwNGRFNU9RU3c  32days ago

在 2016年9月28日星期三 UTC+8上午6:12:17，Mauro Rossi写道：

[youling 257]

in 20 days , i used https://drive.google.com/open?id=0B43N_UcsJhpjflJHMm5uNVl2YU1jZFljMW0zTHV3VU0wYV9MY2VVVkY2eGJPT0EyTkQ4WnM ,

4.4 kernel nougat 32bit ；15 days ago , i only recompile 32 bit 4.8 kernel and modules, used them on  nougat 32bit ，get the same dmesg with now dmesg

 binder: 1361:1408 transaction failed 29201, size 68-0

<13>[  144.377670] init: Service 'audioserver' is being killed...

<13>[  144.378394] init: Service 'cameraserver' is being killed...

<13>[  144.378984] init: Service 'media' is being killed...

<13>[  144.382283] init: Service 'netd' is being killed...

<13>[  144.383318] init: Service 'audioserver' (pid 4944) killed by signal 9

<13>[  144.383891] init: Service 'audioserver' (pid 4944) killing any children in process group

<13>[  130.831653] init: Starting service 'zygote'...

<13>[  130.870676] init: Starting service 'audioserver'...

<13>[  130.892123] init: Starting service 'cameraserver'...

<13>[  130.906565] init: Starting service 'media'...

<13>[  130.919045] init: Starting service 'netd'...

在 2016年9月28日星期三 UTC+8上午6:12:17，Mauro Rossi写道：

[Mauro Rossi]

Il giorno mercoledì 28 settembre 2016 06:32:42 UTC+2, youling 257 ha scritto:

in 20 days , i used https://drive.google.com/open?id=0B43N_UcsJhpjflJHMm5uNVl2YU1jZFljMW0zTHV3VU0wYV9MY2VVVkY2eGJPT0EyTkQ4WnM ,

4.4 kernel nougat 32bit ；15 days ago , i only recompile 32 bit 4.8 kernel and modules, used them on  nougat 32bit ，get the same dmesg with now dmesg

 binder: 1361:1408 transaction failed 29201, size 68-0

<13>[  144.377670] init: Service 'audioserver' is being killed...

<13>[  144.378394] init: Service 'cameraserver' is being killed...

<13>[  144.378984] init: Service 'media' is being killed...

<13>[  144.382283] init: Service 'netd' is being killed...

<13>[  144.383318] init: Service 'audioserver' (pid 4944) killed by signal 9

<13>[  144.383891] init: Service 'audioserver' (pid 4944) killing any children in process group

<13>[  130.831653] init: Starting service 'zygote'...

<13>[  130.870676] init: Starting service 'audioserver'...

<13>[  130.892123] init: Starting service 'cameraserver'...

<13>[  130.906565] init: Starting service 'media'...

<13>[  130.919045] init: Starting service 'netd'...

在 2016年9月28日星期三 UTC+8上午6:12:17，Mauro Rossi写道：

I'm seeing issues with kernel 4.8(rc8) and mesa 12.1.0devel and some Intel GPUs

For example I can boot on laptop Sandybridge without issues, while on Ivybridge motherboard I can't complete boot and when I switch ALT+F1 to console I get a GUI restart.

Is this your case?

Could you please provide log.txt in Debug mode and provide info about your HW?

Thanks

Another info about radeonsi is that in nougat-x86 it is currently freezing and shuting down screen with HD7950

with both mesa 12.0 and 12.1devel and with both kernel 4.4. and 4.8rc, so always freezing.

M.

[youling 257]

log

在 2016年9月28日星期三 UTC+8下午4:56:52，Mauro Rossi写道：

[Masaykh]

Can DRI modules be used currently for 6.0.1 ?

currently gallium, i915 ,i965 only modules available.

вторник, 27 сентября 2016 г., 14:33:14 UTC+3 пользователь Masaykh написал:

[Mauro Rossi]

Il giorno giovedì 29 settembre 2016 22:10:27 UTC+2, Masaykh ha scritto:

Can DRI modules be used currently for 6.0.1 ?

currently gallium, i915 ,i965 only modules available.

module gallium_dri is sufficient and used for the enabled GPUs drivers except i915, i915.

other DRI drivers (in src/mesa/drivers/dri) are considered obsolete compared to the corresponding gallium implementations.

the list of enabled drivers is the one defined in device/generic/common/BoardConfig.mk

https://sourceforge.net/p/android-x86/device_generic_common/ci/marshmallow-x86/tree/BoardConfig.mk

 

[Masaykh]

пятница, 30 сентября 2016 г., 10:57:13 UTC+3 пользователь Mauro Rossi написал:

okey, so i followed your link and found :

BOARD_GPU_DRIVERS ?= i915 i965 nouveau r300g r600g radeonsi swrast virgl vmwgfx

but in current marshmallow 6.0.1 r1 only gallium (software only?), i915 and i965 present.

did other removed becouse of instability ?

[Mauro Rossi]

Il giorno venerdì 30 settembre 2016 12:27:02 UTC+2, Masaykh ha scritto:

пятница, 30 сентября 2016 г., 10:57:13 UTC+3 пользователь Mauro Rossi написал:

okey, so i followed your link and found :

BOARD_GPU_DRIVERS ?= i915 i965 nouveau r300g r600g radeonsi swrast virgl vmwgfx

but in current marshmallow 6.0.1 r1 only gallium (software only?), i915 and i965 present.

did other removed becouse of instability ?

Hi,

gallium3d architecture is a design choice in order to minimize impacts in adding new drivers,

but it is indeed HW accelerated, sw renderer driver swrast with two possible pipe drivers: softpipe and llvmpipe

i915g (gallium3d implementation for intel by LunarG ) is not used mainly because intel did not invested time/resources into it

 and i965,i915 are more perfomant compared to i915g

Here is some more detailed explanation, if you are interested:

https://blogs.igalia.com/itoral/2014/08/08/diving-into-mesa/

M.