00:53 <vagrantc> alright, finally got it to recognize the initrd!

00:54 <vagrantc> apparently, depthcharge wanted the order of the images in the FIT image to be kernel first, dtb second, and initramfs third ... or at least... that's what i *think* i changed that made it work

01:30 <vagrantc> ok, now i just need to figure out how to get the LCD driver to work as a module...

01:30 <vagrantc> so close

07:25 <indy> wadim_, still no success? i played till night with u-boot and reading coresight memory mapped registers - https://da.gd/ENWqB

08:10 <wadim_> when I try to attach, trace32 still reports "debug port fail"

11:25 <msgctl> Hey, has anyone tried booting linux on GPD XD?

11:25 <msgctl> (RK3188)

11:26 <msgctl> s/RK3188/RK3288

12:03 <rperier> this week-end I plan to continue to work on uboot-mainline for rk3288 and test what you asked Heiko (emmc on my veyron). On the Linux side, do you have other tasks where I can help ? (otherwise I can boot recent kernel like next and try to solve existing bugs :) )

12:03 <rperier> hi btw

12:04 <rperier> anyway, I think find tasks won't be difficult :)

12:31 <stdint> msgctl, you could use the linaro linux

12:31 <stdint> also rockchip release its linux based on linaro you could check the wiki for help

12:52 <msgctl> stdint: kthx!

14:08 <indy> hi all

14:09 <indy> all: anybody with miqi booted upstream kernel?

14:10 <indy> even with loaded dw_mmc-rockchip and its deps, no mmcblk device detected

14:15 <indy> i tried inspect device tree in u-boot using fdt command but can't find offset

17:10 <diego71> ×.

20:55 <ayaka> indy, not need to use ftd

20:56 <ayaka> just send it through the third argument for the bootz command

20:57 <indy> ayaka, i know content of upstream kernel dtb, but i don't know content of u-boot's dtb

20:58 <ayaka> indy, the dtb used in u-boot should be attach by the u-boot build script

20:58 <indy> i know, i would like to know if there is difference, because loading dw_mmc-rockchip is not enough

20:59 <indy> ayaka, i just don't know at which address resides

20:59 <ayaka> it is not important a thing

21:00 <ayaka> you don't need to know how does it be load

21:02 <indy> i want just dump builtin dtb from memory using fdt

21:02 <indy> i don't want to load it

21:03 <vagrantc> if you can access /proc/device-tree, i think you can generate a .dtb from with dtc

21:04 <vagrantc> if you're talking about the running device-tree

21:04 <vagrantc> hrm... maybe dtc doesn't take a directory tree as an argument

21:04 <indy> vagrantc, i'm talking about u-boot and its appended dtb

21:05 <vagrantc> is it in mainline u-boot ?

21:06 <indy> ayaka, i see https://da.gd/sLDt2 with 4.8-rc4 and with rk3288-miqi.dtb and rd.driver.pre=dw_mmc-rockchip,mmci,mmc_block

21:07 <indy> vagrantc, it is from miqi-prebuilt 2016.09-devel

21:07 <ayaka> you could build int dw_mmc or as a module?

21:09 <indy> fedora builds all as modules