codeworkx changed the topic of #teamhacksung to: HACKSUNG IS DEAD, HAIL HACKSUNG!
g_byers is now known as gbyers[Away]
RudyValencia- has joined #teamhacksung
Gethiox has quit [*.net *.split]
RudyValencia has quit [*.net *.split]
Gethiox has joined #teamhacksung
arcus has quit [Disconnected by services]
arcus_ has joined #teamhacksung
arcus_ is now known as arcus
slick_rick has joined #teamhacksung
Kostenko_ has joined #teamhacksung
Kostenko has quit [Ping timeout: 264 seconds]
Space- has quit [Ping timeout: 252 seconds]
Space- has joined #teamhacksung
Blaguvest has quit []
Blaguvest has joined #teamhacksung
kzard has quit [Quit: KVIrc 4.3.1 Aria http://www.kvirc.net/ | 64bit Windows version by http://kvirc.d00p.de/]
kzard has joined #teamhacksung
slick_rick has quit [Quit: Connection closed for inactivity]
slick_rick has joined #teamhacksung
geecko has joined #teamhacksung
geecko_ has joined #teamhacksung
sbrissen_gone is now known as sbrissen
Kostenko_ has quit [Quit: Reconnecting]
Kostenko has joined #teamhacksung
Kostenko_ has joined #teamhacksung
Kostenko has quit [Ping timeout: 245 seconds]
Kostenko has joined #teamhacksung
Kostenko_ has quit [Ping timeout: 240 seconds]
plastikman has joined #teamhacksung
Turtuga has quit [Ping timeout: 252 seconds]
Turtuga has joined #teamhacksung
Turtuga has quit [Ping timeout: 252 seconds]
Turtuga has joined #teamhacksung
Turtuga has quit [Ping timeout: 252 seconds]
Turtuga has joined #teamhacksung
Turtuga has quit [Ping timeout: 252 seconds]
Turtuga has joined #teamhacksung
plastikman has quit [Ping timeout: 265 seconds]
Turtuga has quit [Ping timeout: 252 seconds]
Turtuga has joined #teamhacksung
Turtuga has quit [Read error: Connection reset by peer]
plastikman has joined #teamhacksung
Turtuga has joined #teamhacksung
Turtuga has quit [Ping timeout: 264 seconds]
zeorin has joined #teamhacksung
<zeorin> Hi, I'm a user of the n9005 nightly (unified)
<zeorin> so I have it's current bugs (no calls, problems with video,time feasts badly on boot)
<zeorin> and ive been doing a lot of reading
<zeorin> it seems like (from what I hear on xda) there's no device maintainer for n9005 and that's part of the problem
<zeorin> I'm a developer irl so I'm wondering if perhaps I could contribute...
<zeorin> what does being a device maintainer entail and are there any requirements?
Turtuga has joined #teamhacksung
RudyValencia- has quit [Quit: Gone]
cuco has joined #teamhacksung
Turtuga has quit [Ping timeout: 264 seconds]
zeorin has quit [Ping timeout: 268 seconds]
cuco has quit [Ping timeout: 246 seconds]
davi has joined #teamhacksung
davi has joined #teamhacksung
Turtuga has joined #teamhacksung
evcz has quit [Read error: Connection reset by peer]
davi has quit [Ping timeout: 268 seconds]
Turtuga has quit [Ping timeout: 252 seconds]
plastikman has quit [Ping timeout: 268 seconds]
arcus has quit [Disconnected by services]
arcus_ has joined #teamhacksung
arcus_ is now known as arcus
plastikman has joined #teamhacksung
Turtuga has joined #teamhacksung
Turtuga has quit [Ping timeout: 252 seconds]
evcz has joined #teamhacksung
plastikman has quit [Quit: Leaving]
Blaguvest has quit []
plastikman has joined #teamhacksung
sbrissen is now known as sbrissen_gone
sn0w14 has joined #teamhacksung
Teemo_ has joined #teamhacksung
<Teemo_> hi ppl :)
<Teemo_> geecko, have you seen this? http://git.stlinux.com/?p=stm/linux-stm.git;a=commit;h=3a3ca5ac81dcbd4adaf8f8537ac94a6d483b574d
<geecko_> Teemo_, we don't have the blobs
<Teemo_> It seems somebody implemented r4p0 driver. :D
<geecko_> Teemo_, mali isn't the problem anyway
<Teemo_> Take a look :)
sn0w14 has quit [Ping timeout: 240 seconds]
<Teemo_> Maybe is something useful. :)
<geecko_> Teemo_, no, we don't have the blobs.
<geecko_> Teemo_, the kernel source is available since a few months
<Teemo_> So you give up? :(
NaiX has joined #teamhacksung
<NaiX> hi guys
<NaiX> i hope not
<geecko_> Teemo_, what?
<geecko_> XD
<Teemo_> There's nothing you can do?
<geecko_> Teemo_, about the mali drivers, yeah, for now, nothing we can do indeed
<geecko_> but it's not related to Our Broplem
<Teemo_> Maybe we will have blobs once KitKat official version is available for S3?
<NaiX> hopefully
<Teemo_> Or this project is dead? :(
<geecko_> Teemo_, i'm not sure we will ever see r4p0 blobs, but it's not really a problem
<geecko_> the blobs we need are r3p2 with dmabuf support. that's what is shipped with Insignal dev boards
<NaiX> geecko: i presume you're not manage kernel to boot?
<geecko_> NaiX, yeah i didn't work on it since
<NaiX> aha :-)
<geecko_> NaiX, but i will someday :3
<Teemo_> But why ARM developed r4p0 version? To be not used? I don't understand...
<geecko_> NaiX, i'm just more concerned about my studies and my career right now
<NaiX> i sincerely hope you will
<NaiX> of course, study is first thing
<geecko_> Teemo_, Samsung isn't the only company to use mali
<Teemo_> Yes, I know.
<Teemo_> Let's get the code from another platform. :D
<geecko_> Teemo_, you clearly don't understand
<NaiX> without proper blobs you can't
<geecko_> no need for code, we need the BLOBS
<Teemo_> Blobs aren't available from others than SAMSUNG?
<NaiX> for samsung phones, only from samsung yes
<Teemo_> And if we can get blobs from another manufacturer, it is going to work?
<NaiX> that's the way it is :-)
<NaiX> no, since those blobs wont have all proper code for our device :-)
<Teemo_> :(
<NaiX> yep, exactly :-P
<geecko_> NaiX, actually i'm not sure about that ;)
<NaiX> hehe
<Teemo_> But S3 will receive newer blobs. And GeeckoDev works for Galaxy Note. So... it's going to work?
<geecko_> Teemo_, it's the same SoC
<Teemo_> It's not the same device.
<geecko_> it's still Exynos 4
<Teemo_> Same family of SoC, then :D
<geecko_> but I think that blobs are compatible between devices
<NaiX> i hope it will since they are all exynos 4
<geecko_> only the kernel driver includes platform-specific code
<Teemo_> I hope we will get r4p0 driver. :D
<NaiX> here goes gecko's magic, once ge will manage to fuck samsung bsck
<NaiX> back
<geecko_> so, we may get a blob, but it needs to be the right version with the right compilation options, so it's almost the same problem
<NaiX> sorry for bsd word, but... they deserve it
<Teemo_> But maybe SAMSUNG strategy is to make a botch driver. Maybe same driver, but using KitKat. :D
<geecko_> Teemo_, they are done with Mali 400
<geecko_> it's a thing of the past now
<geecko_> but their smartwatch is using an Exynos 4212 SoC
<geecko_> which has a Mali 400
<Teemo_> Yeeeey! :D
<geecko_> there's some code for this watch into the latest kernel source for the S3
<geecko_> Teemo_, doesn't mean anything
<NaiX> smartwatch use our m400? jesus :-)
<geecko_> in their source drop they are using r3p1 drivers.
<geecko_> S3 is using r3p2 now
NaiX has quit [Quit: NaiX]
NaiX_ has joined #teamhacksung
<Teemo_> geecko_, really weird.
<geecko_> the latest release for the Note? not sure if r2p4 or r3p1
<geecko_> and we got r3p2 ;)
<Teemo_> I don't understand why SAMSUNG works with an older driver, even if they can use newer.
<geecko_> Teemo_, because, why breaking something that already works for zero income
<NaiX_> yep
<NaiX_> optimizing the profit :-)
<geecko_> actually it could be possible to update to r3p2 on official firmwares by upgrading the blobs and kernel source
<Teemo_> Even if we can get something from an upcoming release for S3, I'm curious if Project Butter would be a reality.
<geecko_> totally doable, weird that no one did it already
<geecko_> Teemo_, we don't really need Project Butter, we need something that isn't 100% broken. PB will come by fixing all the stuff
<Teemo_> geecko_ what kernel uses that smartwatch ? :D
<Teemo_> Do you know?
<geecko_> Teemo_, 3.0 of course
<Teemo_> Scumbag SAMSUNG :-))
<geecko_> they don't reinvent the wheel for a small screen smartwatch
<geecko_> Teemo_, we don't need 3.4 kernel either, as long as the graphics stack is up to date
<geecko_> actually there's some bits of 3.4 kernel in the official 3.0 kernel for the S3
<geecko_> sync driver from Android 3.4 that is required by the mali r3p2 driver
<Teemo_> But they promised they will bring source code for S2. We have not forgotten this.
<geecko_> Teemo_, insignal sources
<Teemo_> And they use same SoC, same closed source for a smartwatch... Yeah, SAMSUNG, good job. Ignoring devs is a main priority for them.
<geecko_> we have everything we need
<geecko_> now we (I) need to push
<Teemo_> To push what? :D
<geecko_> Teemo_, well they use a fucking ancient graphics stack, it's not their fault
<geecko_> a relique from gingerbread
<geecko_> Insignal devboard has the right graphics stack, from the Exynos 5 nuke
<NaiX_> geecko: exactly what are missing now for working PB? hwcomposer? buffering? or vsync?
<geecko_> 99% similar to the Nexus 10
slick_rick has quit [Quit: Connection closed for inactivity]
<geecko_> NaiX_, current hwcomposer is a mess
<geecko_> it barely does its work
<geecko_> everything is fine on the kernel side i'd say
<NaiX_> or we (you) must just connect all that
<geecko_> what i'm trying to do is:
<geecko_> completely switch the graphics stack to the one from Insignal that is designed for jelly bean
<Teemo_> A big step :)
<NaiX_> aha
<geecko_> this involves: new hwc, new gralloc, new mali blobs with dmabuf, new ION driver, new fb driver
<geecko_> fb driver is the last piece
<NaiX_> you have all sources for that?
<Teemo_> pièce de résistance :-)
<geecko_> NaiX_, gralloc and mali are blobs, the rest is open source
<geecko_> we could build gralloc with manta (nexus 10) sources though
<NaiX_> i hope you will manage it someday
<NaiX_> and my s2 will still work at that time :-)
<geecko_> yeah i should hurry before everyone has got a new phone XD
<Teemo_> NaiX, I have S2 too :D
<NaiX_> :-)
<Teemo_> Best phone ever :)
<NaiX_> all it needs, is PB
<NaiX_> yep
<NaiX_> geecko: anyway, i'm gonna buy you a beer,just tell me how can i do it?
<geecko_> NaiX_, send me some dogecoins
<NaiX_> ?
<geecko_> haha :D
<geecko_> dead serious though
<geecko_> NaiX_, http://dogecoin.com/ fyi
<NaiX_> hmm, first i will read about it
<NaiX_> np
<NaiX_> i dont use bitcoins and similar virtual coins :-)
<geecko_> NaiX_, it's real :D
arcus has quit [Quit: quit]
<NaiX_> geecko: i will do that
<geecko_> NaiX_, i'll just leave my address here
<geecko_> DLbaZo1ZECJX42w8AxJxoBMr6s9KZY3uKW
<NaiX_> ok, i will manage it somehow
<NaiX_> expect it in one of next days
<geecko_> NaiX_, new shibe :D
<geecko_> NaiX_, we got a nice community over here: http://www.reddit.com/r/dogecoin/
<geecko_> NaiX_, just post how new you are and expect some dogecoins being tipped your way
<NaiX_> hehe, i'm a total beginner :-)
<NaiX_> i will manage to buy a beer, dont worry :-)
<geecko_> NaiX_, nice :D
NaiX_ has quit [Quit: NaiX_]
Teemo_ has quit [Quit: ChatZilla 0.9.90.1 [Firefox 30.0a2/20140329004001]]
plastikman has quit [Read error: Operation timed out]
geecko has quit [Ping timeout: 240 seconds]
geecko_ has quit [Ping timeout: 240 seconds]
RudyValencia has joined #teamhacksung