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
<Armbian-Discord> <C​older> ty again for your help...i have edit overlay but with the last armbian 5.15 kernel don't work...always black screen. /dts-v1/;
<Armbian-Discord> <C​older> /plugin/;
<Armbian-Discord> <C​older> / {
<Armbian-Discord> <C​older> metadata {
<Armbian-Discord> <C​older> title = "Enable Raspberry Pi 7-inch Touchscreen";
<Armbian-Discord> <C​older> compatible = "radxa,rock-4c-plus";
<Armbian-Discord> <C​older> category = "display";
<Armbian-Discord> <C​older> description = "Enable Raspberry Pi 7-inch Touchscreen";
<Armbian-Discord> <C​older> };
<Armbian-Discord> <C​older> fragment@0 {
<Armbian-Discord> <C​older> target = <&mipi_dsi>;
<Armbian-Discord> <C​older> overlay {
<Armbian-Discord> <C​older> status = "okay";
<Armbian-Discord> <C​older> #address-cells = <1>;
<Armbian-Discord> <C​older> #size-cells = <0>;
<Armbian-Discord> <C​older> rockchip,lane-rate = <696>;
<Armbian-Discord> <C​older> ports {
<Armbian-Discord> <C​older> #address-cells = <1>;
<Armbian-Discord> <C​older> #size-cells = <0>;
<Armbian-Discord> <C​older> port@1 {
Armbian-Discord has quit [Remote host closed the connection]
Armbian-Discord has joined #armbian-rockchip
<Armbian-Discord> <s​tvhay> different kernel i think? https://github.com/armbian/build/blob/main/patch/kernel/rockchip-rk3588-legacy/2002-OrangePi5-Motorcomm-stuff-extracted-from-Xun.patch <- this patch for opi5 adds an older Motorcomm driver, which overrides the one in rockchip-linux-5.10-rkr3.6
<Armbian-Discord> <s​tvhay> its where i got that table from
<Armbian-Discord> <s​tvhay> The opi one is older, and seems to support older PHYs
<Armbian-Discord> <s​tvhay> Hmm looking closer, maybe the OPI5 just doesn't have a complete description in Config.in
<Armbian-Discord> <s​tvhay> It seems to support more than the description indicates, if we assume this matching logic reflects what is supported:
<Armbian-Discord> <s​tvhay> ```
<Armbian-Discord> <s​tvhay> 1281: .phy_id = PHY_ID_YT8010,
<Armbian-Discord> <s​tvhay> 1296: .phy_id = PHY_ID_YT8510,
<Armbian-Discord> <s​tvhay> 1311: .phy_id = PHY_ID_YT8511,
<Armbian-Discord> <s​tvhay> 1332: .phy_id = PHY_ID_YT8512,
<Armbian-Discord> <s​tvhay> 1345: .phy_id = PHY_ID_YT8512B,
<Armbian-Discord> <s​tvhay> 1358: .phy_id = PHY_ID_YT8521,
<Armbian-Discord> <s​tvhay> 1383: .phy_id = PHY_ID_YT8531S,
<Armbian-Discord> <s​tvhay> 1408: .phy_id = PHY_ID_YT8531,
<Armbian-Discord> <s​tvhay> 1429: .phy_id = PHY_ID_YT8618,
<Armbian-Discord> <s​tvhay> 1449: .phy_id = PHY_ID_YT8614,
<Armbian-Discord> <s​tvhay> ```
<Armbian-Discord> <a​mazingfate> I wonder where xunlong gets this driver. I gonna drop this patch because it seems that driver in rkr3.6 kernel can already support opi5.
<Armbian-Discord> <s​tvhay> https://gitlab.com/linux-kernel/stable/-/blob/v6.2/drivers/net/phy/motorcomm.c Not the same but Peter Geis is co-author
<Armbian-Discord> <a​mazingfate> Rockchip uses upstream code from Peter, while xunlong uses the vendor code.
<Armbian-Discord> <s​tvhay> yeah you're right i had it backwards
<Armbian-Discord> <s​tvhay> i wonder what phy the qp64 has
<Armbian-Discord> <r​pardini> Yeah I initially added all (or mostly...) non-essential Xunlong patches as .disabled. The Motorcomm was necessary back in rk3.4 I think, for the OPi5 -- feel free to disable again if rk3.6 provides enough
<Armbian-Discord> <s​tvhay> I found a "new" realtek driver in some random BSP kernel that, the kernel itself, didn't even build.
<Armbian-Discord> <s​tvhay> but I guess its from realtek--couldn't really verify that against another github
<Armbian-Discord> <s​tvhay> and this fun fix I had to make to avoid kernel panics https://github.com/stvhay/kernel/commit/fe45c1db9671a29855ed323d6c5d44f130b49d83
<Armbian-Discord> <s​tvhay> anyways, I guess that's a reason to trust code closer to mainline over vendor--even if it seems to support more hardware
<Armbian-Discord> <R​iskyBusiness> hello everyone,
<Armbian-Discord> <R​iskyBusiness> we are trying to bring up windows on our RK3399 Custom Board. I would like to know if it is possible to do this ? i did not found any useful guide for this , and i don't know where to start, i would be thankful if you guys help me
<Armbian-Discord> <R​iskyBusiness> Thank you
<Armbian-Discord> <W​erner> We do not deal with Windows whatsoever. So no idea.
freejke has quit [Ping timeout: 256 seconds]
freejke has joined #armbian-rockchip
<Armbian-Discord> <T​onymac32> I spent about 00:00:30 trying to boot an efi windows image on rockpro64, no luck