05:20 <PhoenixMage> Anyone know if mainline uboot should be able to detect an NVMe drive on a rock pi 4?

09:44 <obbardc> here's a better view of the rk3328 drm jumpy HDMI issue, if anyone can shed any light: https://www.youtube.com/watch?v=bO46C6bgsN8

09:44 <damex> hi, i am definitely missing something (armbian works) - i take last known good uboot (works with armbian) install idbloader.img with seek=64 and u-boot.itb with seek=16384, known good extlinux config (works with armbian), use single partition starting from 32768, bootstrap debian buster to that single partition and take either stable (4.19.x) or their last 5.5.0.x mainline kernel. nothing happens although i see that ethernet card gets initialized

09:44 <damex> and then reinintizalied (uboot -> kernel?) again. display have no output and networking is not available. uboot have no output too (sorry i don't have cables for serial) - is there anything i could try? same thing works with armbian armbian rootfs+same upstream uboot+custom simple extlinux conf

09:45 <obbardc> damex: get a serial lead, otherwise you're kind of looking blind

09:45 <damex> obbardc: well, it will take 2-3 months

09:45 <obbardc> ouch

09:45 <obbardc> where are you ?

09:45 <damex> Kazakhstan

09:45 <damex> (although temporarily)

09:49 <damex> obbardc: maybe there is a way to get hdmi framebuffer ?

09:49 <damex> like simplefb or something very primitive

09:50 <obbardc> if you can boot armbian then start replacing parts of their image with your own u-boot for instance

09:53 <damex> i can boot armbian with mainline/upstream uboot and then tried swapping boot.{cmd,scr} with simple extlinux config -> works.

09:54 <damex> if i try to boot debian kernel on armbian rootfs - does not boot. if i try to boot armbian kernel on debian rootfs - does not boot.

09:54 <damex> i am definitely missing something on the way

09:56 <damex> https://gist.github.com/damex/7093c7ef31bff77d4a11b7db2df071a9 that is the extlinux.conf

09:57 <obbardc> is your root really mmcblk1p1 ?

09:58 <obbardc> my rock64 running linux-next mmcblk0 is SD and mmcblk1 is eMMC

09:58 <obbardc> but vendor kernel is opposite...

10:01 <damex> obbardc: yeah, mmcblk0 is mmc module (empty) and mmcblk1 is microsd card reader. i tried using UUID/PARTID in place.

10:02 <damex> https://gist.github.com/damex/e413adef6e7597906a14c79ec9b20c56

10:06 <obbardc> hm, for me on linux-next on rock64 mmcblk0 is uSD

11:39 <robmur01> PhoenixMage: I don't think RK3399 PCIe support is in mainline yet, but there are patches currently on the list

12:24 <PhoenixMage> robmur01: Thanks, where could I find those patches?

15:56 <nomis> Hi all. Can anybody tell me, where I do get the "proper" brcmfmac43455-sdio.txt nvram-File for an AP6255 module?

17:05 <robmur01> PhoenixMage: er, on the U-Boot mailing list, of course

17:05 <robmur01> I think this is the most recent version - https://patchwork.ozlabs.org/project/uboot/list/?series=175880

17:08 <robmur01> nomis: arguably the best bet is to grovel it out of the original Android firmware - IIRC it's somewhere under /vendor

17:09 <nomis> robmur01: yeah, that is what I've done now. Not really satisfactory. :)

17:09 <robmur01> the filenames are all different of course, but at least for Broadcom-based chips the kernel log shows the filenames it's using

17:09 <robmur01> chances are, it's _probably_ the same stuff as kept here: https://github.com/rockchip-linux/rkwifibt

17:10 <robmur01> note that the actual firmware binaries might be different to the ones in linux-firmware (e.g. different IRQ setups), so you may need those as well as just the NVRAM

17:11 <robmur01> Alternatively, I think LibreELEC has a slightly more "upstreamified" collection of such module firmwares somewhere

17:28 <nomis> robmur01: the firmware from linux-firmware seems to work. I was just missing the nvram file. Not sure what information is in there :-/

17:30 <nomis> yeah, the file in the rkwifibt repository is the same that I found in my original firmware.