Re: Rockchip RK3328 Rock64 HDMI

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üchemann <maciphone2@googlemail.com> wrote:
> 
> > this time even without specific hack, just a config :
> > 
> > CONFIG_PHY_ROCKCHIP_INNO_HDMI=y
> > CONFIG_VIDEO=y
> > CONFIG_DISPLAY=y
> > CONFIG_VIDEO_ROCKCHIP=y
> > CONFIG_DISPLAY_ROCKCHIP_HDMI=y
> 
>  Thanks, just found the same settings messing with make menuconfig,
> will test on my board tonight.
> 
> > 
> > U-boot 2024.07( I think also 2024.04) then enables the inno  hdmi_phy driver
> > 2024.10-rc5 even shows the u-boot logo, 
> > 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
> > 

 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>:
> > > 
> > > On Wed, 25 Sep 2024 17:29:11 +0200
> > > Klaus Küchemann <maciphone2@googlemail.com> wrote:
> > > 
> > >> Needed 5 minutes to hack u-boot`s current version  to get HDMI - output on the RK3328/ Rock64..
> > > 
> > > What's the hack ?
> > > 
> > 
> > 
> > > Am 25.09.2024 um 18:56 schrieb Emmanuel Vadot <manu@bidouilliste.com>:
> > > 
> > > On Wed, 25 Sep 2024 17:29:11 +0200
> > > Klaus Küchemann <maciphone2@googlemail.com> wrote:
> > > 
> > >> 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) .
> > > 
> > > That's not what I said, if u-boot setup a GOP interface FreeBSD loader
> > > and kernel will be able to use it.
> 
> 
> -- 
> Emmanuel Vadot <manu@bidouilliste.com> <manu@freebsd.org>
> 


-- 
Emmanuel Vadot <manu@bidouilliste.com> <manu@freebsd.org>