07:34 <stdint> naobsd, it is different to android sdk

19:51 <akaizen> Is it now possible to flash a mailine uboot and linux + rootfs directly eMMC? Or do I still need to flash some propritary image and then dd my image to /dev/mmc* ?

19:51 <akaizen> (for rk3288)

19:54 <vagrantc> with firefly-rk3288, i think i dd mainline u-boot to a microSD card.

21:09 <mmind00> akaizen: looking at some flash-writing script, it seems this should be doable simply by entering maskrom and writing the bootloader (https://github.com/rockchip-linux/rkflashtool/blob/master/rkflashloader) ... I've sucessfully used a variant of that on my rk3036 board

21:49 <phh> is it relevant to put linux-rockchip in CC for related threads? I'm thinking of my rc5t619 patches (used on many rk3288 devices), or Hans Verkuil's dw-hdmi-cec driver

21:49 <akaizen> mmind00: thanks. is the bootloader still the proprietary one?

21:50 <akaizen> dont see source for rkbin folder

21:51 <mmind00> akaizen: not sure what you mean with bootloader? Maskrom is of course the same as it's build into the chip, but uboot these days has both spl and 2nd level loader in its sources

21:52 <akaizen> Oh can we finally go from maskrom -> mainline uboot -> kernel ?

21:52 <mmind00> akaizen: yep

21:52 <akaizen> without the propritary rk

21:52 <akaizen> ! thats great news

21:53 <mmind00> akaizen: you would do something like: tools/mkimage -n rk3288 -T rksd -d spl/u-boot-spl.bin ${OUTBIN}; cat u-boot-dtb.bin >> ${OUTBIN} and write that using rkflashtool from maskrom

21:55 <akaizen> awesome is this stuff still necessary for rkflashtool to bootstrap writing in MASK ROM mode? DDRINIT=${ROOTDIR}/rkbin/rk32/32_LPDDR2_200MHz_LPDDR3_200MHz_DDR3_200MHz_20150318.bin

21:55 <akaizen> USBPLUG=${ROOTDIR}/rkbin/rk32/rk32xxusbplug.bin

21:56 <mmind00> akaizen: yep

21:56 <mmind00> as you still need to setup that rkflashtool backend on the board

21:57 <akaizen> ah well, its nice that RK released it.. if I have some extra time I will write a script to make flashing as easy as RPi!

21:57 <akaizen> Then we can show rk how many people want good software support :)

22:01 <mmind00> akaizen: I think looking at the mailing lists and also the mention some days back that the rk3399-android actually uses the drm as graphics backend suggests they don't need much convincing anymore ;-)

22:05 <phh> I wonder to which point they'll be using mainline for rk3399-android, I dream of everything mainline, would make forward-porting as easy as finding updated mali binaries

22:06 <akaizen> thats amazing progress. some of the ODM/OEM manufacturers i work with would disagree - so until I can get a nice linux sdk for some of our boards, making rk more aware to put pressure on their partners is still something to do

22:06 <akaizen> and also what @phh said ^

22:06 <phh> (and then of a mesa mali... who knows)

22:44 <mmind00> akaizen: yes, "market pressure" is always good to keep up, to keep up the momentum

22:49 <phh> damn rk3288.fr is down

23:42 <mmind00> phh: I only know rockchip.fr as some sort of leaking documents ... what did rk3288.fr do?

23:43 <phh> ... I guess I was mistaking both... thanks.

23:43 <phh> (are those really leaks?)

23:49 <mmind00> phh: I'm pretty sure that collection of manuals with confidentiality notices is not authorized :-)