05:59 <junari> warpme: Thanks, I'll take a look at the weekend

10:02 <maz> apritzel: the 2w has finally landed. I'll try and bug you at some point...

10:04 <apritzel> maz: ah, yeah, we made good progress with respect to U-Boot's AXP313 and LPDDR4 support, I think I will just merge those patches in the next days

10:04 <apritzel> and I made a DT, from the schematics

10:05 <apritzel> also I think warpme and junari either have the board or are about to get it

10:05 <apritzel> maz: do you also have that expansion board, with the Ethernet jack?

10:06 <maz> yeah, I bought that as well. seem silly not to.

10:08 <warpme> apritzel maz: as you have 2w - i'm curious about cec on 2w. On my 2w is not working. cec works well on zero3 - so it look like: 1\my board and sch are different or 2\my board has missing something. May any of you do test of cec?

10:09 <apritzel> indeed. Just be warned that the internal PHY is not supported in mainline yet, and it will require a bunch of patches in various subsystems (PWM, MFD, PHY) to make this happen. They are patches somewhere, but little has been posted yet.

10:11 <warpme> btw: 2w dts i'm using: https://github.com/warpme/minimyth2/blob/master/script/kernel/linux-6.5/files/0638-arm64-dts-allwinner-h618-add-opi-2w.patch

10:11 <apritzel> warpme: I wish this would have been a link to a mailing list archive ;-)

10:12 <warpme> ah yes. me too :-p Simply lack of time currently :-(

10:14 <apritzel> warpme: please put at least a Signed-off-by: line in your patches. Then others can pick them up and post them.

10:15 <warpme> ah ok - forgot that!. sure will do...

10:17 <warpme> btw: it looks i posted old ver ofmy 2w dts. https://github.com/warpme/minimyth2/blob/aad7970c9e274dafde952ace0eb88105bb41ad06/script/kernel/linux-6.5/files/0638-arm64-dts-allwinner-h618-add-opi-2w.patch#L253 and https://github.com/warpme/minimyth2/blob/aad7970c9e274dafde952ace0eb88105bb41ad06/script/kernel/linux-6.5/files/0638-arm64-dts-allwinner-h618-add-opi-2w.patch#L269 both should be "okay"....

10:18 <maz> warpme: probably not. I make a point in not having any screen, and my world is solely based on serial consoles...

10:19 <warpme> maz : maybe this might be helpful: https://github.com/warpme/minimyth2/blob/master/script/kernel/linux-6.5/files/0607-drivers-drm-wip-add-h616-hdmi-xulong.patch

10:29 <apritzel> warpme: maz meant he doesn't use or even need a screen ;-)

10:31 <apritzel> warpme: the key point is that patches need to be reviewed. No one writes perfect code (or DTs), and another pair of eyes is always needed to ensure quality.

10:32 <apritzel> warpme: I immediately see two or three issues with your DT patch. If you would post it, we could iterate over this and get it fixed

10:32 <maz> apritzel: well, I have exactly *one* monitor, and it has my laptop plugged on it. everything else is on the console server.

10:32 <apritzel> warpme: even if you don't have time, the feedback would be public and other people - like me;-) - could pick it up

10:33 <maz> +1 on stuff being on the ML instead of a git tree. I wouldn't know where to look the first place.

10:34 <apritzel> maz: one monitor: similar here. I have a second 20 year old LCD just for *testing* HDMI output on boards ;-)

10:36 <maz> apritzel: I made a point in having serial ports on everything, including stuff that isn't supposed to have one (https://git.kernel.org/pub/scm/linux/kernel/git/maz/cs-hw.git)

10:37 <maz> (but that's getting OT)

11:23 <karlp> how's the support for that 20u5622 module?

11:54 <warpme> log distant from kernel standards&quality); 2)5Ghz band has issues for me (not investigated yet)

11:54 <warpme> karlp : i played a bit with code and have it working quite well on mainline. My test was: 24h continuous hd livetv playback on zero2w via wifi. No issues with data transfer nor any errors in dmesg. Currently issues i see: 1)kernel reporting hung tasks when 5622 is probed but not touched by userspace. launching iwd daemon (without any wifi connection) stops issue - so 5622 drives is almost ready to use (despite code is horrible and

11:57 <warpme> (despite code is horrible and long distant from kernel standards&quality); 2)5Ghz band has issues for me (not investigated yet)

12:49 <karlp> which driver is this?

12:50 <karlp> does bluetooth work(at all)?

14:16 <jernej> note that UART connection on 5622 wifi+bt combo doesn't matter at all. Vendor BT driver creates virtual tty port and routes all data through SDIO.

14:17 <jernej> I wonder if generic SDIO BT driver would work

14:19 <jernej> warpme: to answer your question from yesterday, my priority is to make all display features work first and only then I'll play with aw5622

14:20 <warpme> jernej : having h616 hdmi working with your's recent 10bit h6 workings would be wonderful....

14:20 <jernej> exactly, h616 will be based on top of that and a bit hacky at first

14:21 <jernej> but priority is to understand HW first and then make cleaner code

14:22 <warpme> and i have big hopes also for fixing drm planes on h616....

14:22 <jernej> that's part of it

14:22 <warpme> :-)))))

14:23 <jernej> drm planes already work, but YUV formats doesn't work yet. I think there is a bug in CSC

14:24 <warpme> yes. in my case playback works, osd is ok - but picture is very dark

14:25 <warpme> interesting is that it was working ok at times of very early playings with h616 (5.15 times or so...)

14:47 <karlp> jernej: ooh, cute with tty over sdio, is that common at all? I've always seen the uart routed as well.

14:47 <jernej> tbh, I don't know

16:27 <junari> there is difference in boards with version opizero3 v1.2 and v1.3

16:27 <junari> But I don't which

16:31 <junari> my openwrt image works on v1.2 and don't work in v1.3

16:43 <jernej> warpme: I think I fixed most of of the display engine issues. Only AFBC is untested.

16:43 <jernej> so maybe I'll have some very early LE image over the weekend

16:44 <jernej> CSC issue was very dumb - wrong base address

16:44 <jernej> but there were few others