ChanServ changed the topic of #linux-rockchip to: Rockchip development discussion | Wiki at http://linux-rockchip.info | Logs at http://irclog.whitequark.org/linux-rockchip | ML at http://groups.google.com/group/linux-rockchip
norris has joined #linux-rockchip
markm has quit [Ping timeout: 244 seconds]
markm has joined #linux-rockchip
naobsd has quit [Quit: naobsd]
Bludot has quit [Disconnected by services]
Bludot has joined #linux-rockchip
cnxsoft has joined #linux-rockchip
ganbold has quit [Remote host closed the connection]
akaizen has joined #linux-rockchip
akaizen has quit [Remote host closed the connection]
akaizen has joined #linux-rockchip
akaizen_ has joined #linux-rockchip
akaizen has quit [Ping timeout: 244 seconds]
ganbold has joined #linux-rockchip
Bludot has quit [Quit: Connection closed for inactivity]
GriefNorth has joined #linux-rockchip
markm has quit [Ping timeout: 240 seconds]
markm has joined #linux-rockchip
rory096 has quit [Ping timeout: 240 seconds]
* bashintosh has more progress on kernel v3.14 -> http://ur1.ca/nxsxa
mrueg has quit [Ping timeout: 256 seconds]
mrueg has joined #linux-rockchip
premoboss has quit [Remote host closed the connection]
naobsd has joined #linux-rockchip
naobsd1 has joined #linux-rockchip
naobsd has quit [Ping timeout: 250 seconds]
naobsd1 is now known as naobsd
naobsd1 has joined #linux-rockchip
naobsd has quit [Ping timeout: 252 seconds]
naobsd1 is now known as naobsd
naobsd1 has joined #linux-rockchip
topi`_ is now known as topi`
naobsd has quit [Ping timeout: 240 seconds]
naobsd1 is now known as naobsd
naobsd has quit [Quit: naobsd]
naobsd has joined #linux-rockchip
nighty-_ has joined #linux-rockchip
markm_ has joined #linux-rockchip
markm has quit [Ping timeout: 260 seconds]
premoboss has joined #linux-rockchip
markm_ has quit [Ping timeout: 244 seconds]
dlezcano has quit [Ping timeout: 240 seconds]
dlezcano has joined #linux-rockchip
markm_ has joined #linux-rockchip
cnxsoft has quit [Read error: Connection reset by peer]
lerc has quit [Ping timeout: 240 seconds]
cnxsoft has joined #linux-rockchip
lerc has joined #linux-rockchip
<lautriv__> bashintosh, around ?
<popolon> mmind00_: you speak last week about a guy that complained about xf86-video-armsoc : http://lists.freedesktop.org/archives/dri-devel/2013-April/037823.html
<popolon> ARM authors posted a mail about it, one year before and nobody seems to care at this time (at least no direct answer) : http://lists.x.org/archives/xorg-devel/2012-May/031250.html
<popolon> I also seen that your last modification in your fork was in about may, there was lot of work on rockchip drm driver since this time
<popolon> there are hw compositing/copy/scaling/cursor/... now, I'm really feeling that jessy use it with chromebook kernel
<popolon> still don't know if that's better to try to make rockchip mali blob working with the last chromebook kernal on a jessy debian, or look at kernel used in archlinuxarm for Veyron Pinky platforms
<lautriv__> anyone booting from SD-Card who can help me out with some details ?
VargaD has quit [Ping timeout: 246 seconds]
VargaD has joined #linux-rockchip
lautriv_ has joined #linux-rockchip
lautriv__ has quit [Ping timeout: 256 seconds]
ssvb has quit [Ping timeout: 240 seconds]
markm_ has quit [Ping timeout: 256 seconds]
<lautriv_> perfect, rockchip appears to have problems with SD anyway :(
markm_ has joined #linux-rockchip
pietrushnic`away has quit [Ping timeout: 260 seconds]
Bludot has joined #linux-rockchip
dlezcano has quit [Quit: Leaving]
ssvb has joined #linux-rockchip
lautriv_ is now known as lautriv
markm__ has joined #linux-rockchip
markm_ has quit [Ping timeout: 265 seconds]
dlezcano has joined #linux-rockchip
GriefNorth has quit [Ping timeout: 246 seconds]
premoboss has quit [Quit: Sto andando via]
cnxsoft has quit [Quit: cnxsoft]
<lautriv> when my PARM on emmc contains mtdpart for (kernel) 0x00006000@0x00004000 , for what reason may i find the real header @0x00006000 ?
sjoerd has left #linux-rockchip [#linux-rockchip]
<mmind00_> popolon: "that guy" was Deve Airlie ... the kernel-maintainer of the drm subsystem, so his words carry some weight ... still that sadly never got resolved
<mmind00_> popolon: also I'm definitly not a x11-developer, I just pummeled that into some basic form to have graphics to try out the mali blob
rory096 has joined #linux-rockchip
<mmind00_> popolon: so I don't plan to spend to much time there and instead hope somebody else will step up - I really am mainly a kernel guy right now
<mmind00_> popolon: also were did you read copying/compositing? I also saw the scaling stuff
<mmind00_> popolon: and I don't think the kernel makes an actual difference ... the interface to a xserver is mostly the same with either mainline or the chromeos-kernel
mmind00_ is now known as mmind00
markm__ has quit [Ping timeout: 264 seconds]
markm has joined #linux-rockchip
markm has quit [Ping timeout: 264 seconds]
markm has joined #linux-rockchip
cosm has joined #linux-rockchip
gb_master has joined #linux-rockchip
markm has quit [Ping timeout: 260 seconds]
markm has joined #linux-rockchip
markm has quit [Ping timeout: 250 seconds]
markm has joined #linux-rockchip
jas-hacks has joined #linux-rockchip
jas-hacks1 has joined #linux-rockchip
cosm has quit [Ping timeout: 260 seconds]
jas-hacks has quit [Ping timeout: 272 seconds]
<lautriv> :(
GriefNorth has joined #linux-rockchip
<lautriv> any non-radxa users around ?
<amstan> lautriv: i have a chromebook
<lautriv> amstan, probably 3288 ?
<amstan> yep
<lautriv> amstan, i'm looking for someone who was able to build any kernel working on 3188 since anything on the web is incomplete and outdated.
<amstan> no luck with upstream on 3188?
<lautriv> amstan, upstream supports close-to-nothing regarding 3188
<amstan> then you're probably stuck with a vendor tree
<lautriv> amstan, that was the incomplete part abut it.
<amstan> what's your end goal?
<lautriv> running linux, basically a htpc and distcc for other arms.
<amstan> not sure what the state of video will be in those trees
<lautriv> amstan, i pulled a lot from github and nothing is even complete. most lack on a defconfig which they call in their very own scripts.
<lautriv> or vanished completely.
jas-hacks1 has left #linux-rockchip [#linux-rockchip]
jas-hacks1 has joined #linux-rockchip
akaizen_ has quit [Remote host closed the connection]
akaizen has joined #linux-rockchip
akaizen has quit [Remote host closed the connection]
Apocx has joined #linux-rockchip
jas-hacks1 has left #linux-rockchip [#linux-rockchip]
Apocx_ has quit [Ping timeout: 259 seconds]
leming_ has joined #linux-rockchip
leming has quit [Ping timeout: 240 seconds]
leming_ is now known as leming
nashpa has quit [Ping timeout: 264 seconds]
nashpa has joined #linux-rockchip
<popolon> mmind00: Ok, the thing was posted on xorg, not on kernel ml. I don't think this guy (sorry doesn't remember the name) is wrong, I suppose it is 100% true, but for the time, until, ARM/google other make a good armsoc, we are dependent of it :)
<popolon> I will look a little more at it, I've no background in this domain, so it doesn't looks very hard work, I suppose, when I will look a little more it will be very hard :)
* popolon stop to say stupids thinks for this evening
gb_master has quit [Remote host closed the connection]
akaizen has joined #linux-rockchip
akaizen has quit [Remote host closed the connection]
GriefNorth has quit [Ping timeout: 256 seconds]
markm has quit [Ping timeout: 240 seconds]
<bashintosh> lautriv: surely you've seen/tried this a million times, but I assume there are too many things "broken" for your requirements? http://radxa.com/Rock/Linux_Mainline
<amstan> bashintosh: yeah, "what remains to be done" is full of stuff that he cares about
<bashintosh> amstan: mmmh tricky business - perhaps the only way is the "DIY" approach... :(
akaizen has joined #linux-rockchip
naobsd has quit [Quit: naobsd]
nighty-_ has quit [Quit: Disappears in a puff of smoke]
<bashintosh> ...or can move to "Androshit" as he calls it... :p
akaizen has quit [Remote host closed the connection]
akaizen has joined #linux-rockchip
akaizen has quit [Remote host closed the connection]
markm has joined #linux-rockchip
<bashintosh> So if a kernel is built with "CONFIG_ARM_APPENDED_DTB=y" then zImage is appended to the dtb, does that mean that as the kernel boots it will not read the dtb from the resource file (resource.img)?
<bashintosh> or rather the dtb is appended to zImage... :)