lanefu changed the topic of #armbian-rockchip to: Armbian - Linux for ARM development boards | Rockchip SoC | www.armbian.com | This channel is relayed to the equivalent Discord channel | this channel is logged
DC-IRC has quit [Remote host closed the connection]
DC-IRC has joined #armbian-rockchip
<DC-IRC>
[Discord] <mecoblock> hdmi is super new rn it’s like actively being worked on from collabora. I think they sent some stuff upstream
<DC-IRC>
[Discord] <mecoblock> hdmi is super new rn it’s like actively being worked on from collabora. I think they sent some stuff upstream (just the phy so it’s not done yet)
<DC-IRC>
[Discord] <matthewcroughan> I'm on kernel 6.9-rc3, I guess this won't be enough?
<DC-IRC>
[Discord] <matthewcroughan> I'll still need to use the collabora kernel?
<DC-IRC>
[Discord] <Werner> Not everything has been sent upstream if I had to guess. Using collabora directly will give you more stuff they are working on
<DC-IRC>
[Discord] <mecoblock> If you want full hw support/daily drive it, it only makes sense to use RK BSP kernel (even Collabora says so) which is based on upstream 6.1 + downstream patches.
<DC-IRC>
[Discord] <matthewcroughan> hell nawh!
<DC-IRC>
[Discord] <matthewcroughan> I would literally rather die
<DC-IRC>
[Discord] <gospod13337> Try beer before
<DC-IRC>
[Discord] <gospod13337> It opens your perspective
<DC-IRC>
[Discord] <monkablyat> I'm not really sure so far whether this BSP 6 was a marketing joke or meant seriously by Rockchip
<DC-IRC>
[Discord] <mecoblock> I mean 5.10 BSP is still being continued to be developed so I guess nobody knows?
<DC-IRC>
[Discord] <matthewcroughan> @mecoblock what doesn't work on mainline/collabora? It seems basically everything at this point works on collabora.
<DC-IRC>
[Discord] <matthewcroughan> I can't think of a single feature here that isn't working as intended on mainline yet, having constructed the full dts at this point based on the khadas-edge2
<DC-IRC>
[Discord] <Werner> check here for working/not working
<DC-IRC>
[Discord] <matthewcroughan> oh nvm, switching to the collabora kernel did that, maybe I still need a patch or two
<DC-IRC>
[Discord] <mecoblock> It does but HDMI, power management, PCIe and much much more isn't properly in mainline for example
<DC-IRC>
[Discord] <mecoblock> Encode is only via cpu possible, there is AV1 decode via VPU is already upstream
<DC-IRC>
[Discord] <mecoblock> Yeah but not HDMI 2.1
<DC-IRC>
[Discord] <matthewcroughan> What's the advantage of 2.1?
<DC-IRC>
[Discord] <matthewcroughan> I can get ads directly piped through the wire/
<DC-IRC>
[Discord] <matthewcroughan> I can get ads directly piped through the wire?
<DC-IRC>
[Discord] <mecoblock> 4k120/8k
<DC-IRC>
[Discord] <matthewcroughan> ah, overkill for me atm, but yeah eventually mainline will grab that
<DC-IRC>
[Discord] <matthewcroughan> hmm.. on the collabora kernel wifi doesn't seem to work anymore, I wonder what happened
<DC-IRC>
[Discord] <mecoblock> Not sure if all resolutions are in mainline rn, they weren't the last time I checkee. HDMI is really new
<DC-IRC>
[Discord] <mecoblock> Missing patch?
<DC-IRC>
[Discord] <matthewcroughan> maybe.. I thought I included it though, I'll double check
<DC-IRC>
[Discord] <mecoblock> Not sure if all resolutions are in mainline rn, they weren't the last time I checked. HDMI is really new
<DC-IRC>
[Discord] <matthewcroughan> must be
<DC-IRC>
[Discord] <mecoblock> Patch could also not be compatible with whatever Collabora branch you're using and needs to edited
<DC-IRC>
[Discord] <matthewcroughan> it'd fail in that case, not silently
<DC-IRC>
[Discord] <matthewcroughan> Yeah I was simply missing a patch
<DC-IRC>
[Discord] <mecoblock> Are you only gonna do NixOS or also commit support for Armbian for H96-V58?
<DC-IRC>
[Discord] <matthewcroughan> has nothing to do with distribution, it's something I want to put in u-boot's dts
<DC-IRC>
[Discord] <matthewcroughan> but primarily my focus is nixos
Ark74 has quit [Read error: Connection reset by peer]
Ark74 has joined #armbian-rockchip
<DC-IRC>
[Discord] <matthewcroughan> does anybody know why I may be unable to get a usb 2.0 otg port working on my board, but I can get the usb 3.0 one working fine?
<DC-IRC>
[Discord] <matthewcroughan> and why does it require setting `usbdp_phy0` status okay when this should have nothing to do with display port?
<DC-IRC>
[Discord] <mariob> Which one more specifically?
<DC-IRC>
[Discord] <mariob> There are 2 otg ports on rk3588, each connected to a usbdp phy.