Date: Wed, 25 Sep 2024 20:00:33 +0200 From: Emmanuel Vadot <manu@bidouilliste.com> To: Klaus =?ISO-8859-1?Q?K=FCchemann?= <maciphone2@googlemail.com>, freebsd-arm@freebsd.org Subject: Re: Rockchip RK3328 Rock64 HDMI Message-ID: <20240925200033.71f37cd50e1290bdfa98cf22@bidouilliste.com> In-Reply-To: <20240925192116.860d73712f620c2fd77685a4@bidouilliste.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> <20240925185607.8fc021905b94c98c002d3dec@bidouilliste.com> <9361258C-6C87-4F67-892F-30AE593FF436@googlemail.com> <20240925192116.860d73712f620c2fd77685a4@bidouilliste.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 25 Sep 2024 19:21:16 +0200 Emmanuel Vadot <manu@bidouilliste.com> wrote: > On Wed, 25 Sep 2024 19:19:57 +0200 > Klaus K=FCchemann <maciphone2@googlemail.com> wrote: >=20 > > this time even without specific hack, just a config : > >=20 > > CONFIG_PHY_ROCKCHIP_INNO_HDMI=3Dy > > CONFIG_VIDEO=3Dy > > CONFIG_DISPLAY=3Dy > > CONFIG_VIDEO_ROCKCHIP=3Dy > > CONFIG_DISPLAY_ROCKCHIP_HDMI=3Dy >=20 > Thanks, just found the same settings messing with make menuconfig, > will test on my board tonight. >=20 > >=20 > > U-boot 2024.07( I think also 2024.04) then enables the inno hdmi_phy d= river > > 2024.10-rc5 even shows the u-boot logo,=20 > > t...hey seem to still maintain the RK3328 hdmi.... I'm on rc5 and by default it's not enabled. > > -?I will look into that GOP- thing?. > > If you have instructions or hints for that, plz let me know > >=20 So I kinda see what's going on. For some reason the video isn't considered as a valid console, setting stdout to be serial,vidconsole doesn't work. I couldn't find why or if there is some way to enable this for the rock64 but I think that this is why efifb doesn't work, since this is not a valid console for u-boot I think that the u-boot drivers de-init the hdmi and all when we get into the kernel (even if loader sees the GOP as valid). I don't think that I have enought motivation to look further. Cheers, > > > Am 25.09.2024 um 18:56 schrieb Emmanuel Vadot <manu@bidouilliste.com>: > > >=20 > > > On Wed, 25 Sep 2024 17:29:11 +0200 > > > Klaus K=FCchemann <maciphone2@googlemail.com> wrote: > > >=20 > > >> Needed 5 minutes to hack u-boot`s current version to get HDMI - out= put on the RK3328/ Rock64.. > > >=20 > > > What's the hack ? > > >=20 > >=20 > >=20 > > > Am 25.09.2024 um 18:56 schrieb Emmanuel Vadot <manu@bidouilliste.com>: > > >=20 > > > On Wed, 25 Sep 2024 17:29:11 +0200 > > > Klaus K=FCchemann <maciphone2@googlemail.com> wrote: > > >=20 > > >> 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 can= not be handed over to FreeBSD=20 > > >> because it`s not implemented FreeBSD (as Manu said) . > > >=20 > > > That's not what I said, if u-boot setup a GOP interface FreeBSD loader > > > and kernel will be able to use it. >=20 >=20 > --=20 > Emmanuel Vadot <manu@bidouilliste.com> <manu@freebsd.org> >=20 --=20 Emmanuel Vadot <manu@bidouilliste.com> <manu@freebsd.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20240925200033.71f37cd50e1290bdfa98cf22>