10:20 <eballetbo> mmind00: Hi, how are you? I'm wondering if you know the current status of display on kevin, I just tried to boot recent mainline and I see that display is not working, I suspect is already known, is that right?

10:23 <mmind00> eballetbo: correct ... While Jeffy submitted the edp devicetree changes, but the edp won't really emit anything right now. Sean Paul was on this a while back ... see https://www.spinics.net/lists/linux-renesas-soc/msg19767.html

10:24 <mmind00> eballetbo: So there is the PSR bug right now and the edp not outputting anything on kevin when the display gets enabled to solve

10:27 <eballetbo> mmind00: many thanks for the info, as usual really helpful :)

10:28 <mmind00> eballetbo: :-D

10:36 <Ke> mmind00: and however was the other person, I get [ 0.029390] CPU: All CPU(s) started in SVC mode.

10:36 <Ke> on libreboot/C201/rk3288

10:38 <mmind00> Ke: and?

10:39 <Ke> and that's why the Hyp mode does not work for me

10:39 <mmind00> obviously

10:40 <Ke> quite

10:41 <Ke> kind of interesting, if it works on blobbed coreboot but not on deblobbed libreboot

10:41 <Ke> paulk-gagarine any comments?

10:42 <Ke> mmind00: assuming you think that it should work for rk3288

10:42 <mmind00> Ke: I don't think coreboot does contains blobs for Rockchip platforms ... and no, I think I remember coreboot also starting the kernel in svc mode

10:42 <Ke> ok, I guess I had recollection that someone mentioned it worked on coreboot

10:42 <mmind00> at least the version, from the veyron timeframe

10:42 <Esmil> mmind00: What do you mean "the edp won't really emit anything right now"? Do you mean the built-in screen won't show anything?

10:43 <Ke> I should probably start logging this irc

10:43 <mmind00> Esmil: see the mail I linked above ... mainline analogix driver still has some issues with Kevin's display

10:43 <Ke> paulk-gagarine: nvm, sorry

10:44 <Esmil> mmind00: But my display has been working for a month at least

10:44 <Esmil> I even posted a patch to fix the lock warning spam

10:44 <Ke> mmind00: the dynamic frequency scaling thing is a blob on all armv8 platforms afaik

10:44 <mmind00> Esmil: that is interesting

10:45 <Esmil> https://github.com/esmil/linux/commits/kevin

10:45 <Esmil> I haven't updated it for rc8 yet, but this tree works for me

10:45 <Ke> mmind00: on rk3399 it was a inlined hex string in ATF IIRC

10:49 <mmind00> Ke: you probably mean the ddr frequency scaling ... which gets loaded into the M0 ... https://github.com/ARM-software/arm-trusted-firmware/tree/master/plat/rockchip/rk3399/drivers/m0/src ?

10:51 <mmind00> Esmil: cool ... need to take a look then :-)

10:51 <Esmil> But my patch just changes the spinlock to a mutex. I'm sure Sean fixes it properly

10:52 <Esmil> didn't get around to trying his patches yet though

10:52 <Ke> mmind00: I guess I'll need to check it out, I believe it's the thing corresponding to SCP_BL2 in Armada 8040

10:53 <Ke> which is also a blob for a72 cores

10:53 <mmind00> Esmil: yeah, the interesting thing is that it didn't work for him somehow

10:54 <Esmil> yeah, my best guess is that maybe it's because I didn't change the chrome bootloader, or I just happen to stumble upon a working .config

15:27 <eballetbo> Esmil: can you share your defconfig :) ?

15:40 <eballetbo> Esmil: doesn't work for me neither, using Esmil kernel I only see a black screen, all drm modules seems ok though

16:15 <ayaka> oh, in my memory, the dvfs can be disabled at the linux kernel

16:22 <susedv> Hi, I have built an image from rk3288-sdk for a device without LAN-Port, but "ip addr show" outputs "eth0" anyway. Does anybody know where to remove it, BoardConfig? kernel-config?

19:48 <susedv> Does anybody know how to remove the ethernet interface (board without LAN port) from a RK3288 sdk build target?

20:07 <Esmil> eballetbo: http://sprunge.us/GRKd

20:07 <Esmil> eballetbo: You might want to run through make nconfig to enable the filesystems you need and such. It's probably too specific for my use

20:14 <phh> susedv: well just &ethernet { status = "disabled"; };

20:15 <beeble> if i had to guess i would say sdk kernel will not be dts enabled?

20:15 <susedv> phh: in the DTS file? I extracted the original DTS file from resources.img, from the original image that "doesn't see eth0".

20:15 <beeble> ah, so it is. sorry for the noise :)

20:16 <phh> what does "doesn't see eth0" mean?

20:16 <beeble> eth0 name will be generated for a ethernet device

20:16 <phh> susedv: if you're in de-compiled dts, the node is ethernet@ff290000

20:16 <phh> it should have status = "okay";, change it to "disabled"

20:18 <susedv> with teh original stock firmwhere: when I do "ip addr show" it shows lo, wlan0 but no "eth0". It's OK so because there's no LAN port. But my image with the same DTS file (extracted from resources.img of the original image) does show "eth0". The problem is that when I use an USB-Ethernet adapter it appers as eth1 and other things like DHCP don't work. So eth0 is wrong here and I want to remove it.

20:19 <susedv> phh: I will try.

20:20 <susedv> Thank you, I will try tomorrow but I just wonder why it's in the DTS file if I use the original DTS file with no "eht0"

20:21 <phh> susedv: dts is stored at two places in the firmware

20:21 <phh> resource.img, and boot.img

20:21 <susedv> However I know that ethernet@ff290000 is there, I saw it.

20:21 <phh> boot.img's "second" section may contain another resource.img

20:22 <susedv> ah ok

20:22 <phh> (second meaning third section, first ones being kernel and initramfs)

20:23 <susedv> Ah this is probably the reason for many things I didn't understand

23:04 <vagrantc> hrm. somewhere between linux 4.14-rc3 and 4.14-rc7 pine64_plus appears to have lost microSD support

23:04 <vagrantc> anyone else experiencing this?