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
akaizen has joined #linux-rockchip
akaizen has quit [Read error: Connection reset by peer]
levd has joined #linux-rockchip
levd1 has joined #linux-rockchip
em|biketron has quit [Ping timeout: 246 seconds]
levd has quit [Ping timeout: 250 seconds]
levd1 is now known as levd
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 240 seconds]
levd1 is now known as levd
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 265 seconds]
levd1 is now known as levd
naobsd has joined #linux-rockchip
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 256 seconds]
levd1 is now known as levd
cnxsoft has joined #linux-rockchip
akaizen has joined #linux-rockchip
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 250 seconds]
levd1 is now known as levd
em|biketron has joined #linux-rockchip
akaizen has quit [Remote host closed the connection]
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 250 seconds]
levd1 is now known as levd
akaizen has joined #linux-rockchip
c0d3z3r0 has quit [Ping timeout: 240 seconds]
levd1 has joined #linux-rockchip
c0d3z3r0 has joined #linux-rockchip
akaizen has quit [Ping timeout: 256 seconds]
levd has quit [Ping timeout: 264 seconds]
levd1 is now known as levd
naobsd has quit [Ping timeout: 268 seconds]
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 244 seconds]
levd1 is now known as levd
akaizen has joined #linux-rockchip
naobsd has joined #linux-rockchip
levd has quit [Remote host closed the connection]
levd has joined #linux-rockchip
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 240 seconds]
levd1 is now known as levd
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 264 seconds]
levd1 is now known as levd
levd1 has joined #linux-rockchip
GriefNorth has joined #linux-rockchip
levd has quit [Ping timeout: 264 seconds]
levd1 is now known as levd
markm__ has quit [Ping timeout: 240 seconds]
cosm has joined #linux-rockchip
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 240 seconds]
levd1 is now known as levd
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 255 seconds]
levd1 is now known as levd
cosm has quit [Quit: Leaving]
akaizen has quit [Remote host closed the connection]
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 244 seconds]
levd1 is now known as levd
amstan has quit [Ping timeout: 272 seconds]
akaizen has joined #linux-rockchip
amstan has joined #linux-rockchip
levd1 has joined #linux-rockchip
amstan has quit [Changing host]
amstan has joined #linux-rockchip
levd has quit [Ping timeout: 246 seconds]
levd1 is now known as levd
akaizen has quit [Ping timeout: 268 seconds]
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 250 seconds]
levd1 is now known as levd
<bashintosh> hi amstan, do you know if on Chromebooks kernel.img also combines the device tree?
<bashintosh> combines as contains
<amstan> kernel.img?
<amstan> you mean the thing we put in the k partition? it does have the device tree, yes
<bashintosh> the k partition contains the kernel I assume :)
<bashintosh> because I am looking at chrome/build_gpt_kernel.sh (rkchrome v3.14) which does something with the dtb file, then builds kernel.img - is this not standard for Chromebooks? As in, you don't use kernel.img?
<amstan> "rkchrome v3.14"?
<bashintosh> yes
<amstan> that has nothing to do with what's on the chromebooks right now
<amstan> it's something rockchip abandoned last august, probably just used as temporary space for development
<bashintosh> Ah good to know - won't rely on that script to build the kernel then.
<amstan> no, don't rely on anything from that repository
<amstan> this is what chromeos actually does for the kernel packaging: bashintosh: this is what chromeos actually uses to compule
<amstan> but that's quite huge, and unnecessarly large
<amstan> so i usually suggest looking at archlinux's package for the rockchip chromebooks: https://github.com/archlinuxarm/PKGBUILDs/tree/master/core/linux-veyron
<amstan> it just takes chromeos's kernel, adds it's own config and packages it in a pretty simple looking script: https://github.com/archlinuxarm/PKGBUILDs/blob/master/core/linux-veyron/PKGBUILD
<amstan> line 111 is where the magic with the dts happens
<bashintosh> Mmmh nice! But NOT to be used with rkchrome source right? Sadly (for now) rkchrome builds just fine, while chromeos v3.14 doesn't. Something with the config I am doing wrong I am sure...
akaizen has joined #linux-rockchip
<amstan> again, rkchrome looks to be abandoned since august of last year
<amstan> at that point i'm pretty sure there was no graphics working
<bashintosh> amstan: alright, worth understanding why chomeos kernel doesn't build then! Thanks a million, as usual ;)
<amstan> what compiler?
<amstan> it is gcc 5.2 by chance?
<bashintosh> linaro arm-eabi
<bashintosh> 4.8
<bashintosh> I meant the toolchain - gcc of course :)
<rperier> hi all
<amstan> bashintosh: do you have any errors from the failed compile?
dlezcano has joined #linux-rockchip
akaizen has quit [Ping timeout: 240 seconds]
<bashintosh> amstan: I am not on the builds workstation now but the build fails complaining about missing references to trace_clock_dev, very related to this patch: https://lkml.org/lkml/2013/12/6/1044
<bashintosh> Will post the full error tomorrow
<sjoerd> rperier: If you could drop a note on the mailing list that my patch also fixes your kexec use-case (and add a Tested-By if not Reviewed-By) that would be lovely :)
<amstan> bashintosh: you could ask srao directly
<bashintosh> amstan: here? Or email?
<amstan> just saying that he's already in this channel
<amstan> how did you get your config?
<bashintosh> amstan: with './chromeos/scripts/kernelconfig oldconfig' then './chromeos/scripts/prepareconfig chromiumos-rockchip'
<amstan> ok, that sounds right, hmm
<amstan> well... you can try the arch config, there's not much you can lose
<amstan> it was generated the same way, then a few more things were enabled, but it's a known working config
<bashintosh> I tried removing CONFIG_TRACING but no luck, too many dependencies - will ask srao when I get the full error trace
<bashintosh> Yes I can try with arch config too!
premoboss has joined #linux-rockchip
<amstan> alright, time for bed, good luck!
<bashintosh> amstan: sleep sound! Thx!
sunilmohan_w_ has quit [Ping timeout: 256 seconds]
sunilmohan_w_ has joined #linux-rockchip
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 256 seconds]
levd1 is now known as levd
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 244 seconds]
levd1 is now known as levd
apritzel has joined #linux-rockchip
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 246 seconds]
levd1 is now known as levd
cnxsoft1 has joined #linux-rockchip
levd1 has joined #linux-rockchip
markm has joined #linux-rockchip
cnxsoft has quit [Ping timeout: 250 seconds]
cnxsoft1 is now known as cnxsoft
levd has quit [Ping timeout: 240 seconds]
levd1 is now known as levd
markm has quit [Ping timeout: 246 seconds]
markm has joined #linux-rockchip
levd1 has joined #linux-rockchip
naobsd has quit [Quit: naobsd]
levd has quit [Ping timeout: 264 seconds]
levd1 is now known as levd
akaizen has joined #linux-rockchip
akaizen has quit [Ping timeout: 264 seconds]
<rperier> sjoerd: sure will do
<rperier> sjoerd: done
<sjoerd> Thanks ;)
levd1 has joined #linux-rockchip
levd has quit [Ping timeout: 265 seconds]
levd1 is now known as levd
levd has quit [Quit: levd]
premoboss has quit [Quit: Sto andando via]
markm has quit [Ping timeout: 246 seconds]
premoboss has joined #linux-rockchip
markm has joined #linux-rockchip
<rperier> kernel). It would be interesting to add this support to mainline. I will investigate
<rperier> mhhh... pwm-backlight does not support changing the power state of the screen via the devicetree (like this is the case in the chromeos kernel via the dts property "backlight-boot-off"). So when we boot a veyron chromebook, the backlight is powered one and it is white until the edp is bounded to the vop. If we can ask the driver to blank the screen until the edp is loaded, the screen would be black in this case (like with the chromeos
<rperier> instead of adding a specific property for "FB_BLANK_POWERDOWN", perhaps it would be more interesting to select the power state from the devicetree directly... something like "backlight-power-state = <1>;"
<sjoerd> rperier: you can set teh default in device-tree
<rperier> in mainline ?
<rperier> I will have a look at the documentation again
<sjoerd> - default-brightness-level: the default brightness level (index into the
<sjoerd> array defined by the "brightness-levels" property)
<sjoerd> from Documentation/devicetree/bindings/video/backlight/pwm-backlight.txt
<rperier> no that's brightness, not blank or power state. Assuming that I change the brightness to 0, this value won't change automatically when the edp is bounded, right ?
akaizen has joined #linux-rockchip
<sjoerd> brightness 0 is power off normally
<sjoerd> And no it's seperate from the edp setup
<sjoerd> Only a display server can tie those together
<sjoerd> usually systemd-backlight will ramp it up during early boot (but i think that's after the various modules have loaded)
<sjoerd> Wonder why your screen is white when the backlight comes up though
<sjoerd> Guess it's not powered at all making it whitewash?
akaizen has quit [Ping timeout: 268 seconds]
premoboss has quit [Ping timeout: 244 seconds]
VargaD has quit [Ping timeout: 264 seconds]
VargaD has joined #linux-rockchip
nighty-_ has joined #linux-rockchip
akaizen has joined #linux-rockchip
akaizen has quit [Ping timeout: 268 seconds]
<popolon> mmind00: do you know if someone started to implement drmmode_rockchip (in xf86-video-armsoc)?
<popolon> as that's not in master branch
<mmind00> popolon: yes me ... see the rockchip (or packaging/debian) branch in the armsoc repo in my github account
<mmind00> popolon: there is still something about the drm ioctls I do not fully understand, so haven't posted that for upstream inclusion yet
<mmind00> popolon: short version ... the ROCKCHIP_GEM_CREATE rockchip ioctl is currently limited to the chromeos kernel and my somewhat-stable branch, and I don't really want it in mainline, because it essentially does the same as the generic CREATE_DUMB ioctl <= vs => http://lists.freedesktop.org/archives/dri-devel/2013-April/037823.html
<popolon> oh, ok, thanks
<rperier> sjoerd: when I tested locally yesterday, if I force the screen to be "FB_BLANK_POWERDOWN" when the pwm-backlight driver is initialized (statically into the code), the screen is no longer white but black, and edp still works (with a console). What I concluded is that as your screen is not off and the brightness is set to "128" as default... your screen is white in early boot...
<rperier> the problem does not exist in the chromeos kernel because there is the property "backlight-boot-off" which force the screen to be powered off in early boot
<rperier> forces*
<rperier> at least, as I understood
GriefNorth has quit [Ping timeout: 268 seconds]
<sjoerd> rperier: I don't know the code well enough sorry
apritzel has quit [Ping timeout: 264 seconds]
cnxsoft has quit [Quit: cnxsoft]
<rperier> sjoerd: yeah, I know . I was just explaining you what I found in the code and what I understood :)
akaizen has joined #linux-rockchip
akaizen has quit [Ping timeout: 240 seconds]
akaizen has joined #linux-rockchip
akaizen has quit [Ping timeout: 272 seconds]
akaizen has joined #linux-rockchip
gb_master has joined #linux-rockchip
jas-hacks has joined #linux-rockchip
<amstan> bashintosh: any luck?
<xcasex> which soc are we trying our damndest with?
jas-hacks has left #linux-rockchip [#linux-rockchip]
RokQuarry has joined #linux-rockchip
cristian_c has joined #linux-rockchip
else- has quit [Remote host closed the connection]
cristian_c has quit [Quit: Bye]
gb_master has quit [Remote host closed the connection]
<bashintosh> amstan: getting onto it now.. Downloading the latest sources from here: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/chromeos-3.14/ The repo I have is a few months old..
naobsd has joined #linux-rockchip
naobsd has quit [Quit: naobsd]
nighty-_ has quit [Quit: Disappears in a puff of smoke]