Re: Rockchip RK3328 Rock64 HDMI
- Reply: Jason Bacon : "Re: Rockchip RK3328 Rock64 HDMI"
- Reply: Emmanuel Vadot : "Re: Rockchip RK3328 Rock64 HDMI"
- In reply to: Emmanuel Vadot : "Re: Rockchip RK3328 Rock64 HDMI"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Wed, 25 Sep 2024 15:29:11 UTC
Well, … estimation ..., To say it in short: While RK3399 HDMI even worked with fbsd-efifb on an old installation on my Rock960(which is the same gpu as the RockPro64) , this will not happen for the RK3328/ Rock64. In longer but simple words : Needed 5 minutes to hack u-boot`s current version to get HDMI - output on the RK3328/ Rock64.. It works because u-boot(and linux) has built in driver for the hdmi-inno phy. So the dts devicetree- entries for the hdmi_phy point to that driver ( which is glued in their drm). So u-boot sets up it’s framebuffer based on this driver while it cannot be handed over to FreeBSD because it`s not implemented FreeBSD (as Manu said) . So from u-boot`s framebuffer(or whatever hdmi-output) the screen turns back to dark black exactly in the moment of the handover to fbsd kernel, no automatically efifb. I don`t assume that a dedicated developer will port/write the necessary hdmi-drivers for the outdated RK3328/Rock64 because (e.g in this thread) currently exactly 1 person(not me) is known to need the glass console for that Soc...but you never know…. > Am 21.09.2024 um 19:36 schrieb Emmanuel Vadot <manu@bidouilliste.com>: > > On Sat, 21 Sep 2024 15:49:51 +0200 > Klaus Küchemann <maciphone2@googlemail.com> wrote: > >> Hi Manu, >> >> thanks for letting me know. It`s the first time I looked deeper into this issue. >> So you mean that adding RK3328 codes to your DRM-subtree is even necessary >> to get efifb console output ? > No, efifb will automagically works if u-boot setup the display (which > it should and did iirc but it's been a while) > >> The current state of (at least my) Rock64 is a complete HDMI blank screen without any electrical reaction at boot . >> Can`t find any specific Rockchip frame buffer code at first view, so for now I`m a bit confused where to start >> to get any HDMI-output.u-boot or firmware or your drm-subtree, or is there a specific Rockchip bug somewhere??? > > As said above for efifb u-boot needs to setup hdmi etc ... If it's not > done right now maybe some config is needed. > drm-subtree is needed if one wants 2D accel (but needs code), for 3D we > will need lima ported as this GPU isn't supported by panfrost iirc.