alexst has quit [Ping timeout: 250 seconds]
alexst has joined #linux-exynos
alexst has quit [Ping timeout: 250 seconds]
alexst has joined #linux-exynos
alexst has quit [Ping timeout: 240 seconds]
alexst has joined #linux-exynos
alexst has quit [Ping timeout: 256 seconds]
alexst has joined #linux-exynos
alexst has quit [Ping timeout: 264 seconds]
alexst has joined #linux-exynos
alexst has quit [Ping timeout: 240 seconds]
alexst has joined #linux-exynos
alexst has quit [Ping timeout: 264 seconds]
swabbles_ has joined #linux-exynos
swabbles has quit [Ping timeout: 240 seconds]
tfiga has quit [Ping timeout: 240 seconds]
afaerber has quit [Ping timeout: 240 seconds]
tfiga has joined #linux-exynos
afaerber has joined #linux-exynos
alexst has joined #linux-exynos
alexst has quit [Ping timeout: 240 seconds]
alexst has joined #linux-exynos
alexst has quit [Ping timeout: 240 seconds]
alexst has joined #linux-exynos
alexst has quit [Ping timeout: 240 seconds]
alexst has joined #linux-exynos
alexst has quit [Ping timeout: 260 seconds]
alexst has joined #linux-exynos
alexst has quit [Client Quit]
<Wizzup> swabbles_: We should have a look at mainline 3.16 soon, do you have some time somewhere next week?
<Wizzup> I'm back in the netherlands now
ssvb_ has quit [Quit: Leaving]
liquidAcid has joined #linux-exynos
tfiga_ has joined #linux-exynos
<Wizzup> swabbles_: As in, it would be nice to actually use all dem cores ;-)
tfiga has quit [*.net *.split]
ssvb has joined #linux-exynos
tfiga_ has quit [Quit: http://quassel-irc.org - Chat comfortably. Anywhere.]
tfiga has joined #linux-exynos
<swabbles_> Wizzup: would cost me money to go to Amsterdam, though, except for the weekend.
<Wizzup> Ah.
<Wizzup> Well, weekend is probably doable? Otherwise we can also do something remotely I suppose
<swabbles_> Weekend is doable for me :).
<chrs_> how many cores does the mainline support?
<swabbles_> chrs_: from what I have read global task scheduling should be available since 3.10.
<swabbles_> So if that works, all of them.
<Wizzup> swabbles_: not sure if this weekend or the next one, though.
<swabbles_> Whichever suits you best.
<Wizzup> ah. probably this weekend somewhere is better.
<chrs_> i'm more worried about emmc subsystem stability than core support atm
<chrs_> if you can't run, it doesn't matter how many cores you have
<Wizzup> I have yet to see it actually boot up.
<chrs_> what seems to be the gating issue now?
<Wizzup> It doesn't boot. And we don't know why.
<Wizzup> I guess I could solder a serial onto it.
<Wizzup> but it's also my day-to-day machine
<Wizzup> possible on the older chromebook I can try to solder a serial onto it, since I don't use it (that much) anymore
<Wizzup> possibly*
afaerber has quit [Quit: Verlassend]
afaerber has joined #linux-exynos
ukki has joined #linux-exynos
liquidAcid has quit [Quit: Leaving]
<chrs_> i was booting mainline on the original arm chromebook
<chrs_> i forget which kernel version
<chrs_> 3.8.11
<Wizzup> yes, swabbles also got that to work, at least partially
<chrs_> but it was ubuntu
<chrs_> and pretty unstable
<Wizzup> with simplefb, and audio/wifi
<chrs_> i don't know about simplefb
<chrs_> i was able to use the mali opengl es driver
<swabbles_> Wizzup: that was 3.14 actually.
<Wizzup> mmm pi
<chrs_> supposedly there is a new mali binary binary blob coming too
<chrs_> not sure what kernel versions that's compatible with
* Wizzup doesn't care about binary blobs:)
<swabbles_> 3.16 should work without simplefb (at least, assuming the DRM bridge patches that have been integrated work).
<chrs_> Wizzup: you're not interested in getting something working if it's binary blob only?
<Wizzup> Personally, no
<chrs_> i get that
<Wizzup> I am very careful not compromising this laptop
<chrs_> compromising?
<Wizzup> Yes, compromising :)
<Wizzup> (compromising the security)
<chrs_> oh ok
<Wizzup> if such a thing even exists with software
<Wizzup> mainline would be sweet though
<Wizzup> then I can finally switch back to grsec
<chrs_> you believe running a binary driver would compromise your security?
<_anomaly_> could
<Wizzup> Most definitely.
<Wizzup> In fact, one of my main (silly) reasons to also go to ARM was that, at least at the time, all exploits were for intel
<Wizzup> ;-)
<Wizzup> Security through obscurity
<Wizzup> And it has worked in occasions
<Wizzup> (where all the intel laptops kernel paniced at the same time, my chromebook didn't panic)
<_anomaly_> :|
<_anomaly_> paniced?
<_anomaly_> also how are you going to get around using a binary driver on mali, is lima maturing?
<Wizzup> _anomaly_: Well, you know, some agencies...
afaerber has quit [*.net *.split]
tfiga has quit [*.net *.split]
ssvb has quit [*.net *.split]
plazmonii has quit [*.net *.split]
<Wizzup> Targetted attacks aren't that uncommon
<Wizzup> _anomaly_: I simply use no 3d
<Wizzup> well, I have llvmpipe
robclark has quit [*.net *.split]
meridion has quit [*.net *.split]
leming has quit [*.net *.split]
WarheadsSE has quit [*.net *.split]
luka has quit [*.net *.split]
swabbles_ has quit [*.net *.split]
ukki has quit [*.net *.split]
suihkulokki has quit [*.net *.split]
cmuller has quit [*.net *.split]
steev has quit [*.net *.split]
mdrjr has quit [*.net *.split]
libv has quit [*.net *.split]
dddh has quit [*.net *.split]
Wizzup has quit [*.net *.split]
javier__ has quit [*.net *.split]
chrs_ has quit [*.net *.split]
ukki has joined #linux-exynos
swabbles_ has joined #linux-exynos
chrs_ has joined #linux-exynos
mdrjr has joined #linux-exynos
suihkulokki has joined #linux-exynos
luka has joined #linux-exynos
robclark has joined #linux-exynos
WarheadsSE has joined #linux-exynos
leming has joined #linux-exynos
steev has joined #linux-exynos
meridion has joined #linux-exynos
libv has joined #linux-exynos
cmuller has joined #linux-exynos
dddh has joined #linux-exynos
javier__ has joined #linux-exynos
Wizzup has joined #linux-exynos
afaerber has joined #linux-exynos
tfiga has joined #linux-exynos
plazmonii has joined #linux-exynos
ssvb has joined #linux-exynos
<chrs_> i agree it could compromise security in theory
<_anomaly_> i think it's more likely to compromise stability though tbh
<_anomaly_> but not trying to marginalize the security concern
<Wizzup> well, I mostly don't care about GLES either
<_anomaly_> i do
<Wizzup> Name a few applications that actually use gles
<_anomaly_> kwin_gles
dddh has quit [*.net *.split]
<Wizzup> I use ... awesome ... firefox ... thunderbird (sometimes), terminals...
<Wizzup> that's it.
Wizzup has quit [*.net *.split]
javier__ has quit [*.net *.split]
chrs_ has quit [*.net *.split]
dddh has joined #linux-exynos
<_anomaly_> i'm saying I would like to try a new mali binary
<_anomaly_> hm
chrs_ has joined #linux-exynos
javier__ has joined #linux-exynos
Wizzup has joined #linux-exynos
ukki_ has joined #linux-exynos
<chrs_> is freenode finally getting too big for it's own good?
<chrs_> i just hate the idea of gpu silicon sitting in my machine that i paid for that i can't use
<chrs_> sitting there doing nothing while my browser chugs along struggling to render graphics
swabbles has joined #linux-exynos
<Wizzup> it wouldn't be doing anything for me anyway.
<Wizzup> opengl is much more useful for me
ukki has quit [Remote host closed the connection]
swabbles_ has quit [Write error: Broken pipe]
<chrs_> i expect application level opengl es support to improve
<chrs_> as more things become lower power, mobile based
<chrs_> compiz still wont run under opengl es iirc
<chrs_> maybe it runs w/ mesa libs. not sure. but i don't think it runs with hardware opengl es
<Wizzup> the only thing I need is video scaling and possible decoding
<Wizzup> and that's both not mali :)
<chrs_> i want the same hardware support i can get under chromeos
<chrs_> ultimately
<Wizzup> 3d would be nice, but notma priority
<chrs_> when i last ran 3.8.11 on my chromebook i didn't test audio
<chrs_> and i'm not sure if wifi worked, but i think it was recognized at least
<Wizzup> chromeos works with both wifi and audio
<Wizzup> mainline not ootb
<chrs_> what distro are you running on your chromebook?
<chrs_> yeah, chromeos works fine. when i said 3.8.11 i was talking about mainline
<chrs_> i don't even have an idea of what kernel version chromeos is using
<Wizzup> gentoo
* Wizzup needs sleep
<chrs_> how did you build your gentoo image?
<chrs_> mine is ubuntu, but i followed someone else's instructions
<Wizzup> extract stage 3
<Wizzup> done
<Wizzup> hehe
<Wizzup> I can help later - need sleep first
<chrs_> later
<Wizzup> also, i think the wiki actually has instructions