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> [Discord] <amazingfate> You can try it.
DC-IRC has quit [Remote host closed the connection]
DC-IRC has joined #armbian-rockchip
<DC-IRC> [Discord] <amazingfate> This patch will cause `rockchip-vop2 fdd90000.vop: [drm:vop2_bind [rockchipdrm]] *ERROR* failed to get hdmi0_phy_pll source`, strange: https://gitlab.collabora.com/hardware-enablement/rockchip-3588/linux/-/commit/9add2e547ad19b5953271eaaa5a5c56e6aa3fc25
<DC-IRC> [Discord] <Tonymac32> ?
<DC-IRC> [Discord] <amazingfate> This is already applied:
<DC-IRC> [Discord] <amazingfate> ```
<DC-IRC> [Discord] <amazingfate> $ ls -l /sys/firmware/devicetree/base/phy@fed60000/#clock-cells
<DC-IRC> [Discord] <amazingfate> -r--r--r-- 1 root root 4 3月 18 11:51 /sys/firmware/devicetree/base/phy@fed60000/#clock-cells
<DC-IRC> [Discord] <amazingfate> ```
<DC-IRC> [Discord] <amazingfate> A wip pr: https://github.com/armbian/build/pull/6405
<DC-IRC> [Discord] <amazingfate> We have to rewrite all these hdmi related patches.
<DC-IRC> [Discord] <Tonymac32> I was opposed to having patches in Edge, but got overruled 🙂
<DC-IRC> [Discord] <Tonymac32> That was also the point I quit messing with it, a lot of exhausting bugchasing for no good reason
<DC-IRC> [Discord] <efectn> Do you have a dmesg output after the PR is applied?
<DC-IRC> [Discord] <amazingfate> https://paste.armbian.com/uralutazog.yaml
<DC-IRC> [Discord] <narga_64> I usually love the latest and greatest features and improvements. But in this case honestly, I'm not sure it's worth the effort.
<DC-IRC> [Discord] <narga_64> Patches with bugfixes are cool. I appreciate the effort for the latest rk hardware features before they get to mainline, but I wouldn't want to have to go through these hassles for every new release myself to be honest.
<DC-IRC> [Discord] <narga_64> Wouldn't it make more sense or be easier to maintain the `collabora` branch for rk3588 instead of trying to extract patches from it to `edge`?
<DC-IRC> [Discord] <Tonymac32> That was my proposal 🤣. But everyone wants to delete it from the build system 😉
<DC-IRC> [Discord] <amazingfate> collabora branch only supports a few boards. You still have to patch it. And its code is unstable, can be rebased at any time. As a user you can always use collabora branch, but I would not want to add any patches on it. And finnaly one day we will get rid of the collabora branch, then why not just start from edge?
<DC-IRC> [Discord] <Tonymac32> Because I've done this 3 times with different kernels, and it is always just exhausting and isn't at all worth the effort. 🤷‍♂️. Rockchip64 is still an abomination 🤣, and Meson64 is turning into one
<DC-IRC> [Discord] <Tonymac32> But, I was expressing my opinion of how the kernels should be aligned. There are no documented rules, so there is no "right" way
<DC-IRC> [Discord] <efectn> And most patches will be mainlined soon. Probably we will not need so much patches like current situation
<DC-IRC> [Discord] <shivansps> if i may say something here, i think the whole point of going mainline is panthor, what is not avalible anyway, so... whats the point of mainline if there is no panthor
<DC-IRC> [Discord] <Tonymac32> the RK kernel is gross
<DC-IRC> [Discord] <Tonymac32> I won't deploy *anything* using it
<DC-IRC> [Discord] <narga_64> Arguments can be made for both sides, there isn't a definite correct way I believe.
<DC-IRC> [Discord] <narga_64> If @amazingfate wants to put his work into patching `rk3588-edge` to add hardware features from collabora, that's nice.
<DC-IRC> [Discord] <narga_64> If noone else wants to put in their work since vanilla edge kernel would be totally fine, that's okay as well.
<DC-IRC> [Discord] <narga_64> I just worry that at some point when people update their edge kernel on their rk3588 device, something unrelated to e.g. HDMI, is broken. But maybe my worries are completely unfounded 😄
<DC-IRC> [Discord] <narga_64> For me personally, the point of using an `edge` kernel is simply to stay up to date on the latest Linux improvements and features, like bcachefs and stuff.
<DC-IRC> [Discord] <narga_64> You could say that using Armbian (Debian/Ubuntu) is bad if you want to use the latest stuff since their packages are always out of date from upstream. But then, there isn't really any other way to use newer devices like Rockchip rk35xx.
<DC-IRC> [Discord] <narga_64> Honestly, I would instantly use a rolling release distro, like Arch or one of the many others, on my SBCs if it was possible 😅
<DC-IRC> [Discord] <narga_64> Kinda, yeah 😂 It's also not even regularly updated by Rockchip with the latest upstream bugfixes and security updates
<DC-IRC> [Discord] <Tonymac32> I gave up on the Rockchip kernel when it was still "4.4"
<DC-IRC> [Discord] <Tonymac32> I put all RK versioning in quotes because it's BS 🤷‍♂️🤣
<DC-IRC> [Discord] <Tonymac32> But yeah I agree, there's no "correct" way, AI just know too many people with too many ideas tweaking Pat he's in a single folder means trouble, it has every other time it's been done
<DC-IRC> [Discord] <Tonymac32> But yeah I agree, there's no "correct" way, I just know too many people with too many ideas tweaking patches in a single folder means trouble, it has every other time it's been done
<DC-IRC> [Discord] <Tonymac32> As an example I use these devices headless, so Panthor is of literally 0 value to me, and the HDMI is purely a once a quarter convenience if something breaks. My cherry-picking of patches will be fundamentally different from some others
<DC-IRC> [Discord] <lanefu> As a headless system user.... What those guys said addresses my feelings about why using mainline