xf86-video-armsoc on Chromebooks

$this->bbcode_second_pass_quote('WarheadsSE', 'X')E303 or XE503?

[WarheadsSE]

Okay, on the XE303 it is the T604 drivers.

You then need to extract & copy those to /usr/lib (most of those are provided by mesa, if you want to revert them just re-install the package)

Install & use xf86-video-armsoc-odroid

Remember, these are NOT 2D graphics devices.

[vampirex]

$this->bbcode_second_pass_quote('WarheadsSE', 'O')kay, on the XE303 it is the T604 drivers.

You then need to extract & copy those to /usr/lib (most of those are provided by mesa, if you want to revert them just re-install the package)

Install & use xf86-video-armsoc-odroid

Remember, these are NOT 2D graphics devices.

[WarheadsSE]

These are the Mali drivers, not the VPU drivers. The Mali is a 3d GPU.

[stronnag]

Are there any specific xorg.conf.d settings needed?. Installing xf86-video-armsoc-odroid with

$this->bbcode_second_pass_code('', 'Section "Device"
Identifier "ArmDev"
Driver "armsoc"
EndSection')
results in:
$this->bbcode_second_pass_code('', '[292108.356] (--) Depth 24 pixmap format is 32 bpp
[292108.356] (EE) _CREATE_GEM({height: 768, width: 1366, bpp: 32 buf_type: 0x0}) failed. errno: 22 - Invalid argument
[292108.356] (EE) ARMSOC(0): ERROR: Cannot allocate scanout buffer

[292108.356] (EE)
Fatal server error:
[292108.356] (EE) AddScreen/ScreenInit failed for driver 0
[292108.356] (EE)
')
This is on one of the Mali 604 chromebooks. the original armsoc (with the patches at the start of this thread) runs with the new libmali, but not with the new *GL libraries.

[isaque]

I had the same issue, so I returned to framebuffer.
Anyone has a good xorg.conf we can use with armsoc?
Thanks.

[WarheadsSE]

Here is my XE503C xorg.conf.d entry

$this->bbcode_second_pass_code('', '
Section "Monitor"
Identifier "LVDS-1"
Option "DPMS" "standby"
#Option "DPMS" "false" #mw04/11/2013
Option "Enable" "True"
Option "Primary" "False"
Option "RightOf" "HDMI-1"
EndSection

Section "Monitor"
Identifier "HDMI-1"
Option "DPMS" "standby"
#Option "DPMS" "false" #mw04/11/2013
Option "Primary" "True"
Option "Enable" "True"
Option "DefaultMode" "1920x1080"
EndSection

Section "ServerLayout"
Identifier "ServerLayout0"
Option "BlankTime" "0"
Option "StandbyTime" "0"
Option "SuspendTime" "0"
Option "OffTime" "0"
#Option "OffTime" "30" #mw04/11/2013
EndSection

Section "Device"
Identifier "Mali FBDEV"
Driver "armsoc"
Option "fbdev" "/dev/fb0"
Option "DRI2" "true"
Option "DRI2_PAGE_FLIP" "false"
Option "DRI2_WAIT_VSYNC" "true"
Option "Fimg2DExa" "false"
# Option "Fimg2DExaSolid" "false"
# Option "Fimg2DExaCopy" "false"
# Option "Fimg2DExaComposite" "false"
Option "SWcursorLCD" "false"
EndSection

Section "Screen"
Identifier "DefaultScreen"
Device "Mali FBDEV"
DefaultDepth 24
SubSection "Display"
Modes "1920x1080"
EndSubSection
EndSection

')

[stronnag]

Pretty similar to what I had, and does not help T604 users.

Dear ARM, I will *never* buy another ARM based system until you get your sh*t togther on OSS drivers. Intel worked this out ages ago.

[WarheadsSE]

Tried this? https://github.com/karlssonjohan/ubuntu ... ntu/x.conf

[stronnag]

No joy. My guess it's a kernel thing that has been patched in the odroid / Chromebook2 kernels and not for Chromebook1.