perelax

I have a couple Orange Pi's, and the HDMI is broken. I noticed that many believe that it is Armbian, but it is not. Orange Pi's probably won't be where we want them until 2025. I found a couple notes from development teams, one below and one from September. Both say the same thing: essentially it's in the works: "The RK3588 SoC family integrates the newer Synopsys DesignWare HDMI 2.1 Quad-Pixel (QP) TX controller IP and a HDMI/eDP TX Combo PHY based on a Samsung IP block. Add just the basic support for now, i.e. RGB output up to 4K@60Hz, without audio, CEC or any of the HDMI 2.1 specific features." https://patchwork.kernel.org/project/linux-rockchip/patch/20240801-b4-rk3588-bridge-upstream-v2-3-9fa657a4e15b@collabora.com/

I used a different method: 1. Built Armbian myself. 2. Changed /config/boards/orangepi5.conf line 11 to read: BOOT_FDT_FILE="rockchip/rk3588s-orangepi-5b.dtb" This gives me wifi configuration during first boot, and "install to emmc" during first run. Don't forget to fix empty space on SD Card and extend partition. Not sure if it mattered, but I do that every flash. Perelax

I've been looking into streaming on the Orange Pi's, which doesn't work, so I thought I would share my findings. I was first told by customer service people that the problem was HDCP, but have found that it is actually the camera. The tech was kind enough to slip that the camera module doesn't have their hooks. I can still view in the browser, and this leaves me to the conclusion that TV boxes and Smart TVs are using the camera modules to record end users without their permission. If the system has the camera hooks, the app is allowed to play. The browser bypasses this, because it has permissions to access private information on our devices, and they dig the system while we watch a show. Reminds me of multi-link. There must be some kind of stub or JNI for the hooks, right? We should be able to patch something in, provided that we knew what their code is calling. Anyone have input or ideas on this?