genpaku has quit [Remote host closed the connection]
amitk has joined #linux-exynos
zenmetsu has joined #linux-exynos
<zenmetsu>
Wizzup, I'm rebuilding gentoo on my arm chromebook and it's been quite a while, much appears to have changed. Are you still running gentoo on yours?
<Wizzup>
Yes
<Wizzup>
What appears to have changed / what can I help with
<zenmetsu>
well, trying to figure out why i have no /dev/mali0 for instance
<zenmetsu>
is that kernel source, or is there a driver that i have to grab from somewhere
<zenmetsu>
pretty hard to find up to date documentation on the build, everyone seems to be running pre-canned *buntu variants :(
<Wizzup>
I never used mali
<Wizzup>
It is indeed in the kernel, and it may be in some close-to-mainstream kernels like the one liquidacid has, which I think tracks the odroid one, but I am not sure
<Wizzup>
but aside from the kernel interface you also need the binary userspace blob
<Wizzup>
and you don't get opengl, only opengles
<zenmetsu>
yeah, the userspace blob i can figure out. just trying to get the kernel part nailed down. I kinda want hw acceleration
<zenmetsu>
i'll poke around some more i suppose. i haven't had luck finding a kernel tree that had the driver included. i'll look at the liquidacid kernel and see if it helps out. thanks :)
<Wizzup>
I don't know where he syncs to/from, what his intensions are. Maybe wait for someone who does use mali
<zenmetsu>
i'm cloning that repo now. it looks like it will work.
dlezcano has joined #linux-exynos
krzk has joined #linux-exynos
<zenmetsu>
bah, looks like i'll have to wait for someone that knows about the mali setup. That kernel only has the 3xx and 4xx mali devices, not the 6xx that's in this chromebook
<steev>
zenmetsu: that kernel is for the odroid devices; if you want mali, you'll need to use the cros kernel
<zenmetsu>
it seems as if I'm doing something fundamentally stupid :/ trying to figure out how the odroid boards using this GPU are getting HW support
<krzk>
zenmetsu, which odroid? Different exynos SoCs had different Mali so completely different drivers are used
<krzk>
and for working Mali acceleration you need both kernel drivers (open) and user-space DDK (binary only)
<zenmetsu>
I have a mali T628 in my chromebook. this appears to be what's in the odroid XU3 and XU4
<krzk>
zenmetsu, yes. But on chromebook you probably have ChromeOs... so they should provide you package with mali DDK
<Wizzup>
It seems like he wants to use a recent kernel though - I presume the mali ddk will be usable on that as well, if the interface stays the ame
<zenmetsu>
i didn't have any luck with the chromeos kernel... and all of the other kernels seem to have something wrong with them. it's almost laughable, i cannot imagine that it would be this difficult
<Wizzup>
I have almost everything worked well with 4.5, except for 2d/3d accel and audio speed issues
<zenmetsu>
yeah, 2d is fine, but lack of 3d accel is a dealbreaker for me
<Wizzup>
I don't use a lot of 3d, and mali is 'only' opengles, so useless for most purposes.
<zenmetsu>
i'm aware...
<zenmetsu>
looks like i'll have to use my ancient kernel and userland binaries from the last time i did this install :/ kinda pathetic that the situation has gone from bad to worse in the past year
<amitk>
zenmetsu: I have never seen a happy story with userland gpu binaries and updated kernels ever.
<amitk>
I think the chromebook's upstream story is fantastic, they can't be faulted for awfully maintained mali drivers
<zenmetsu>
yeah... unfortunately i had to re-visit running linux natively after chromeos axed xorg
<zenmetsu>
i had been running gentoo in a chroot from chromeos and that was pretty nice, but now i can't run most graphical apps :(
<amitk>
zenmetsu: just curious, what do you use the opengles acceleration with?
<zenmetsu>
amitk: i do 3d modeling and have an app for my 3d printer control which is opengles capable
<amitk>
zenmetsu: aah, so custom app. I haven't found too many uses for opengles in the generic desktop stack other than playing specially created graphics demos :)
<Wizzup>
amitk: well, I think that maybe GLAMOR can use opengles
<Wizzup>
and some window managers have support for it
<Wizzup>
and maybe with the opengles->opengl emu-layer it may be somewhat useful
<sjoerd`>
amitk: runing gnomne-shell on arm is a good usage of GL ES ;)
<sjoerd`>
gnome-shell is usuable in both ways otherwise you don't ~ever use it in arm :)
isaque has joined #linux-exynos
wwilly has joined #linux-exynos
amoon has joined #linux-exynos
amoon has quit [Client Quit]
krzk has quit [Quit: Ex-Chat]
Vasco_O is now known as Vasco
<zenmetsu>
sjoerd', i'm still using a 3.17 kernel from one of your repos... only one i've managed to get acceleration to work with on my chromebook
<zenmetsu>
only problem with that kernel is the builtin wifi driver is absent, but that's what they make usb dongles for :)
paulk-collins has joined #linux-exynos
zenmetsu has quit [Ping timeout: 250 seconds]
amitk has quit [Quit: leaving]
<steev>
since when sjoerd` ?
<steev>
gnome-shell has a full opengl check that fails horribly on arm, unless they've *finally* fixed that, and i highly doubt they did
zenmetsu has joined #linux-exynos
<sjoerd`>
steev: easy to disable; I've had customer projects using gnome-hsell on arm for quite a while and we've got another one using mutter as the bases of the composotir on ARM
<steev>
odd, i haven't had gnome-shell work since ~3.4
<steev>
i used to use the hack of symlinking bin/true to the gnome-accelerated-check-helper or whatever