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
<phh> well wayland has been working for a long time, what's new is mali with it
<phh> ARM doc says "Note: The ASUS C201 Chromebook only supports Wayland with fbdev backend due to a kernel display driver issue when starting Weston with DRM back-end."
<phh> that's weird.
<mmind00> they could've just fixed the display driver instead :-)
<phh> mmind00: they are using a 4.1 kernel...
<mmind00> *shudder* :-)
<mmind00> that thing is over a year old ... who in his right mind gets the idea to use that as a base for new things
<phh> arm? :D
<phh> anyway, they made nice scripts to generate a bootable usb/sd to directly test their latest drivers on chromebook, so that's nice
<phh> fail
<phh> "Note: X11 is currently not supported on the ASUS C201 Chromebook, this should also get resolved with a future armsoc version."
<naobsd> why ARM uses 4.1 kernel...
<naobsd> anyway all I need is driver and lib ;)
<phh> fwiw, I've updated the code to 4.9-ish and pushed it to https://github.com/phhusson/rockchip_forwardports in midgard
<phh> there is a build.sh with the approximate command to build the module
ayaka has quit [Ping timeout: 256 seconds]
ayaka has joined #linux-rockchip
levd_ has quit [Ping timeout: 250 seconds]
levd has joined #linux-rockchip
leon-anavi has joined #linux-rockchip
<leon-anavi> hi naobsd :)
<leon-anavi> naobsd, thank you for letting me know about the wayland drivers for firefly-rk3288
<leon-anavi> I am building core-image-minimal for firefly-rk3288 right now. If the build is OK my next goal is core-image-weston.
<leon-anavi> what kernel should I use with these drivers?
<leon-anavi> from the log of the chat it seems that I should go for 4.1
<naobsd> I think mainline + phh driver is better
<leon-anavi> ok
<leon-anavi> is there anyone with experience with meta-rockchip for Yocto/OE?
<leon-anavi> rperier, you are the maintainer, right?
<naobsd> about meta-rockchip, you can ask rperier
<naobsd> it seems meta-rockchip is 4.7
<leon-anavi> I checkout branch krogoth
<leon-anavi> of both poky and meta-rockchip
<leon-anavi> this is my first time building Poky with meta-rockchip
<leon-anavi> I don't expect to get wayland working out of the box :) but let's see what will happen
<leon-anavi> may be meta-mali should be used in conjunction with meta-rockchip in this case.
<naobsd> arm meta-mali seems to be for another board?
<naobsd> some tweak might be needed for meta-rockchip and meta-mali
<naobsd> I want to use both too
<naobsd> I have no time in this weekend
<naobsd> (I'm out now)
<leon-anavi> ok, I have just build core-image-minimal
<leon-anavi> now the big question is how to prepare microsd card
<naobsd> there is doc in mainline u-boot
<leon-anavi> meta-rockchip seems to rely on Petitboot
<naobsd> oh
cnxsoft has joined #linux-rockchip
nighty has quit [Ping timeout: 248 seconds]
<naobsd> at home now (for a while)
<naobsd> I don't know well about meta-rockchip and petitboot
<leon-anavi> I am lost in the way to create a bootable microSD card with the rootfs I created with Yocto
<naobsd> current mainline u-boot works fine on rk3288
<naobsd> you can build u-boot independently
<leon-anavi> are there exact steps for using u-boot from microSD card for firefly-rk3288?
<naobsd> then standard procedure can be used for kernel, rootfs, etc
<naobsd> write spl@64, u-boot@256...well, is this still true?
<naobsd> spl@64 is right, it cannot be changed
<leon-anavi> ok
<naobsd> ah I remembered. u-boot@256 ok for firefly
<naobsd> (it's not true only if CONFIG_ROCKCHIP_SPL_BACK_TO_BROM is enabled)
<naobsd> then mainline u-boot understand partition/file system on SD, you can put kernel and rootfs on SD as usual
nighty has joined #linux-rockchip
<leon-anavi> cool
<naobsd> http://rockchip.wikidot.com/partitions you should not use first 4MiB(8192 sectors) for partition/file system
<naobsd> @8192 and after is free(it denepds on OS)
<naobsd> well, on firefly, eMMC is prior than SD
<naobsd> you need to make eMMC unbootable for SD boot
<leon-anavi> I remember that I created a bootable microSD card with Tizen for firefly-rk3288
<leon-anavi> and radxa-rock
<naobsd> ah
<naobsd> then it should work
<leon-anavi> but I used the proprietary bootloader
<leon-anavi> I guess I have to use something different now
<naobsd> it's obsoleted now :)
<leon-anavi> it was 2 years ago :)
<leon-anavi> without wayland/weston there was not much to do with these Tizen imaegs
<naobsd> mainline u-boot support HDMI too
<naobsd> I'm not sure USB host is enabled, but it shouldn't be difficult to use USB keyboard/HDMI display on u-boot :)
<naobsd> anyway you can ask mainline things here :
<naobsd> :)
<naobsd> I have to go out soon
<leon-anavi> it's 4:32 am here so I will go to bed in 20-30 min
<leon-anavi> need some sleep :)
<stdint> the mali in rockchip github is built by rockchip
<stdint> the md5sum won't be same
<stdint> but I don't know whether they have enabled the wayland in libmali
nasuga has quit [Read error: Connection reset by peer]
<leon-anavi> right now I have way more practical question :)
nasuga has joined #linux-rockchip
<leon-anavi> how to prepare bootable microSD card for firefly-rk3288?
<naobsd> please see doc/wiki i wrote
<naobsd> write spl@64 u-boot@256 makes SD bootable
<leon-anavi> which is that document? I had a look at several links and now I am a bit lost.
<naobsd> stdint: about spl, nodtb.is right one now?
<leon-anavi> ok, I have built mainline uboot for firefly
<stdint> naobsd, yes, but currently new u-boot rockhip release is a little different
<naobsd> which is right for mainline? dtb?
<naobsd> well, try both ;)
<stdint> I don't know, I don't have time in u-boot currently
<leon-anavi> I built mainline u-boot v2016.09.01
<stdint> video have made me crazy
<leon-anavi> is this ok?
<stdint> I don't know, but it should work
<leon-anavi> ok
<leon-anavi> naobsd, why should I format the microSD card through u-boot? http://rockchip.wikidot.com/boot-from-sdcard isn't it possible to do it using fdisk?
<naobsd> (I'm out now)
<leon-anavi> ok
<naobsd> no one said it must be done
<naobsd> you can do it, or you can do any other common method
<leon-anavi> ok
<leon-anavi> I cannot see any debug info through "sudo screen /dev/ttyUSB0 115200"
<leon-anavi> is this the baud rate?
<naobsd> it should be ok
<leon-anavi> hm, why I don't see anything with it?
<naobsd> spl must output something
<leon-anavi> I've got nothing
<leon-anavi> on the NAND of my board there is the stock Android that is 2 years old
<leon-anavi> could it be the problem in it?
<naobsd> I cannot try todays u-boot now
<naobsd> you should be able to see something from Android if its bootable
<naobsd> please chech OTG with PC, if you can see device in mask rom mode, spl is not loaded
<leon-anavi> the android boots and I still see nothing in the serial debug
<naobsd> please check uart connection...
<leon-anavi> double checked it already
<naobsd> mmm
<naobsd> if SD is inserted, android doesn't boot,right?
<leon-anavi> yes, if the microSD card is inserted android doesn't boot
<naobsd> ah well, eMMC should be prior
<naobsd> oh
<naobsd> I'm confusing
<leon-anavi> not in my case
<leon-anavi> microSD seems to be prior
nashpa has quit [Quit: Going away]
<leon-anavi> I have booted again my old tizen image from microSD card
<leon-anavi> and linuxium image with ubuntu
<naobsd> I see, then I'm wrong
<naobsd> anyway you can see something on serial console
<naobsd> with any image
<leon-anavi> I don't get anything
<leon-anavi> but this could be related to something in the bootloader
<naobsd> I'll try todays mainline u-boot at night
<naobsd> I cannot answer for now, sorry
<leon-anavi> ok, pls ping me in twitter
<leon-anavi> 5:11 am here so I have to go to bed :) see you and thanks for sharing the news :)
<naobsd> ah proprietary loader on eMMC can read images on SD with proprietary layout
<naobsd> I see, good night :)
<leon-anavi> good night :)
leon-anavi has quit [Quit: Leaving]
cosm has quit [Remote host closed the connection]
cosm has joined #linux-rockchip
nighty has quit [Ping timeout: 268 seconds]
nashpa has joined #linux-rockchip
nighty has joined #linux-rockchip
vagrantc has joined #linux-rockchip
vagrantc has quit [Quit: leaving]
Aussie_matt has joined #linux-rockchip
paulk-collins has quit [Ping timeout: 252 seconds]
zhecka_ has joined #linux-rockchip
Bad_UID has quit [Ping timeout: 256 seconds]
matthias_bgg has joined #linux-rockchip
<stdint> I am really tired of debian cross compiling
<stdint> I think I should move to yocto
matthias_bgg has quit [Ping timeout: 240 seconds]
matthias_bgg has joined #linux-rockchip
matthias_bgg has quit [Remote host closed the connection]
matthias_bgg has joined #linux-rockchip
matthias_bgg has quit [Quit: Leaving]
<phh> I'm using native compiling :)
<ayaka> phh, it would be too slow
<phh> It is fast enough for me, but I reckon we don't have the same requirements
dlezcano has joined #linux-rockchip
premoboss has joined #linux-rockchip
paulk-collins has joined #linux-rockchip
Aussie_matt has quit [Read error: Connection reset by peer]
dlezcano has quit [Ping timeout: 260 seconds]
<rperier> arf, disconnected , I was not on my computer :/
<rperier> ^^
premoboss has quit [Ping timeout: 252 seconds]
cnxsoft has quit [Read error: Connection reset by peer]
cnxsoft has joined #linux-rockchip
paulk-collins has quit [Remote host closed the connection]
paulk-collins has joined #linux-rockchip
<ayaka> phh, when you need to build the whole system, it would be a difficult job
lkcl has quit [Ping timeout: 260 seconds]
cnxsoft has quit [Quit: cnxsoft]
premoboss has joined #linux-rockchip
lkcl has joined #linux-rockchip
<ayaka> lkcl, you may ask me about 2d engineer now
cnxsoft has joined #linux-rockchip
cnxsoft has quit [Quit: cnxsoft]
paulk-collins has quit [Remote host closed the connection]
paulk-collins has joined #linux-rockchip
ayaka_ has joined #linux-rockchip
ayaka has quit [Ping timeout: 268 seconds]
ayaka_ is now known as ayaka
premoboss has quit [Ping timeout: 260 seconds]
<phh> ayaka: may I ask, will there be a rk3288 android tree mainline-ish?
<phh> would be nice to see an Android using standard linux stuff like DRM, iio and such
premoboss has joined #linux-rockchip
nashpa has quit [Ping timeout: 256 seconds]
nashpa has joined #linux-rockchip
premoboss has quit [Ping timeout: 245 seconds]
premoboss has joined #linux-rockchip
lerc has quit [Ping timeout: 260 seconds]
lerc has joined #linux-rockchip
paulk-collins has quit [Quit: Leaving]