Re: Rockchip RK3328 Rock64 HDMI

> Am 25.09.2024 um 20:00 schrieb Emmanuel Vadot <[email protected]>:
> 
> 
> I'm on rc5 and by default it's not enabled.
> 

Yes,  not by default, but I guess yo`ve seen the u-boot logo now on rc5 


> Am 25.09.2024 um 20:00 schrieb Emmanuel Vadot <[email protected]>:


> 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.

Yes, serial/vidconsole (in that order) is the default for quite all defconfigs in u-boot.
I know where to hack/change that in u-boot but I also think that a massive u-boot hack is not what we want.
U-boot hands over to the dw- linux driver(which contains inno hdmi) in the dts-source and we fail to handle the dts/driver.
while I also think the GOP nevertheless  should persist visible for bsd.
Normally I would say that they don`t expose the frame buffer address by default, but then why does it work on RK3399 , puuuhh..
Also don`t know if my motivation for looking further is big enough :-) 
but thanks to point to the GOP-issue and vidconsole stuff,

Regards
K.