Date: Wed, 25 Sep 2024 11:25:29 -0500 From: Jason Bacon <bacon4000@gmail.com> To: =?UTF-8?Q?Klaus_K=C3=BCchemann?= <maciphone2@googlemail.com>, Emmanuel Vadot <manu@bidouilliste.com>, freebsd-arm@freebsd.org Subject: Re: Rockchip RK3328 Rock64 HDMI Message-ID: <dbe88f3b-e23b-4a90-8be2-d5a9b713c7c2@gmail.com> In-Reply-To: <577A672D-E92B-446D-9C81-428FC2121E09@googlemail.com> References: <5kADboXE-OUia2ncm13XjDesvDmjB3tjWSyr3ytCpa5XYof9xOrL9AbRownQoRG9eJcJpYswqjbMt0P0XiZfs7KNNfiNF7vQ93m72mm_Fyk=@protonmail.com> <4F94C5BF-B5D8-4EA0-8B4E-695BBC28D693@googlemail.com> <20240921132533.8b8cf0229a38275128ef0ccc@bidouilliste.com> <D2B71952-7F81-4B19-A47A-252C4797D1E9@googlemail.com> <20240921193608.d88ec27b1da889a52c1f6e3e@bidouilliste.com> <577A672D-E92B-446D-9C81-428FC2121E09@googlemail.com>
index | next in thread | previous in thread | raw e-mail
I also have a Rock64 3328, and while I would like to have a working HDMI, I can't say that I need it. I run it headless and use it to test smallish ports on aarch64. If HDMI did work, I would make sure sysutils/desktop-installer works smoothly on this unit, in case that motivates anyone. Given the cost of a Pro, though, I'm not sure how many people would even care. On 9/25/24 10:29, Klaus Küchemann wrote: > 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. > > -- Life is a game. Play hard. Play fair. Have fun.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?dbe88f3b-e23b-4a90-8be2-d5a9b713c7c2>