08:55 <eballetbo> There is any known issue with display in current linux-next or is something new?

08:55 <eballetbo> https://hastebin.com/uyodisizib.xml

08:56 <eballetbo> It's on a veyron minnie device

09:01 <eballetbo> hmm, seems is a race as is random

09:25 <stdint> eballetbo, the edp?

09:27 <eballetbo> stdint: yes the edp, sometimes works sometimes I get that NULL pointer dereference

09:28 <eballetbo> I just did some reboots

09:28 <stdint> eballetbo, so it happens randomly?

09:29 <stdint> I have not checked the recent next, my next is still in the previous method

09:29 <stdint> s/method/month/

09:29 <eballetbo> seems that

09:30 <stdint> eballetbo, could you confirm whether the kernel at previous month

09:30 <stdint> I think I have give up the update of kernel tonight

09:32 <eballetbo> stdint: I'm currently with next-20170601, do you mean if I can test with next-20170531 ?

09:34 <stdint> eballetbo, I am still at 20170505

10:52 <ayaka> mmind00, one thing I forget, does the upstream u-boot supports boot from emmc?

10:53 <ayaka> rk3288 firefly I mean

10:54 <mmind00> ayaka: I would guess so ... the dw-mmc controllers are supported, so there should be nothing in the way ... you just need to scrap that Rockchip-specific partition stuff and use a regular partition table

10:55 <ayaka> mmind00, I perform the regualar partition table

10:55 <mmind00> ayaka: and then put an extlinux.conf on a partition describing what kernel to boot

10:55 <ayaka> I don't think the rockchip u-boot still use rockchip specific partition

10:55 <mmind00> ayaka: at least on my rk3399-firefly this works like a charm, so I cannot imagine why it wouldn't work on the older socs

10:56 <ayaka> mmind00, I see

10:56 <ayaka> thanks

10:57 <ayaka> I should request a firefly rk3288 next time, the vpu device is more easy to use

10:57 <mmind00> ayaka: http://git.denx.de/?p=u-boot.git;a=blob;f=doc/README.distro is the doc to follow

10:57 <ayaka> mmind00, yes I know, but how does the upstream u-boot is flashed into emmc

10:58 <mmind00> ayaka: when already booted to some linux os, just use dd ... otherwise put the device in maskrom mode (docs on firefly wiki) and use rkflashtool, rkdeveloptool or the old upgrade_tool :-)

10:59 <ayaka> mmind00, I see

12:39 <kloczek> someone knows is it possible to install fedora on firefly rk3399?

14:09 <ayaka> kloczek, yes

14:11 <kloczek> ayaka: it is a bit hard to find any doc about fedora installation on firefly :/

14:11 <ayaka> kloczek, you need to install fedora manually

14:12 <ayaka> install a linux distribution usually can't use the default kernel

14:12 <kloczek> no problem .. only problem is where I can find necessary details :)

16:14 <Myy> mjau

17:54 <Myy> Ok, I'm trying to add support for the Tinkerboard Wifi drivers, due to some demands. It seems that the Wifi driver itself is alread in the 'staging' queue of the 4.12 kernels, however I wonder if the one used on Tinkerboards use the SDIO subsystem

18:33 <Myy> Well, it seems that yeah, it's using the SDIO subsystem. I might be able to get this working today...

19:41 <Myy> Alright, I'll play with my new Mastodon client, some website work and focus on the video codec driver tests, now that I'm having a bit more time to focus on it.

19:41 <Myy> See you later everyone !

21:11 <aura> Hi