Date: Sat, 21 Sep 2024 15:49:51 +0200 From: =?utf-8?Q?Klaus_K=C3=BCchemann?= <maciphone2@googlemail.com> To: Emmanuel Vadot <manu@bidouilliste.com>, freebsd-arm@freebsd.org Subject: Re: Rockchip RK3328 Rock64 HDMI Message-ID: <D2B71952-7F81-4B19-A47A-252C4797D1E9@googlemail.com> In-Reply-To: <20240921132533.8b8cf0229a38275128ef0ccc@bidouilliste.com> References: <5kADboXE-OUia2ncm13XjDesvDmjB3tjWSyr3ytCpa5XYof9xOrL9AbRownQoRG9eJcJpYswqjbMt0P0XiZfs7KNNfiNF7vQ93m72mm_Fyk=@protonmail.com> <4F94C5BF-B5D8-4EA0-8B4E-695BBC28D693@googlemail.com> <20240921132533.8b8cf0229a38275128ef0ccc@bidouilliste.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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=20 to get efifb console output ? 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=20 to get any HDMI-output.u-boot or firmware or your drm-subtree, or is = there a specific Rockchip bug somewhere?=E2=80=A6?=20 Regards K. > Am 21.09.2024 um 13:25 schrieb Emmanuel Vadot <manu@bidouilliste.com>: >=20 >=20 > Hi Klaus, >=20 > On Sat, 21 Sep 2024 01:06:21 +0200 > Klaus K=C3=BCchemann <maciphone2@googlemail.com> wrote: >=20 >> First time since years I switched the dusty Rock64 on :-) >> yes, you?re right, still not fixed : >> dmesg: >> .. >> clknode_link_recalc: Attempt to use unresolved linked clock: hdmi_phy >> Cannot get frequency for clk: hdmi_phy, error: 9 >> ? >> So you can file a bug report to: https://bugs.freebsd.org = <https://bugs.freebsd.org/>; >> You can attach dmesg there (or what I would prefer: send dmesg to = https://dmesgd.nycbug.org<https://dmesgd.nycbug.org/>) >=20 > This isn't a bug, the hdmi_phy clock is supposed to be exported by > the hdmi-phy driver (see the hdmiphy: phy@ff430000 in the DTS), since = we > don't have a driver for this, it's not exported and we warn about = this. >=20 >> I guess you don`t want to port any linux drivers at first attempt :-) = but instead fix the issue=20 >> to get the framebuffer driver working( with it`s restrictions e.g. no = 4K) >>=20 >> Regards >> K. >=20 > Cheers, >=20 >>=20 >>> Am 20.09.2024 um 19:22 schrieb Christoph Pfaller = <pfaller@protonmail.com>: >>>=20 >>> Hello! >>>=20 >>> I recently switched to FreeBSD on my Rock64 due to appearing kernel = panics when running the board with Linux. So far I enjoy the operating = system. However; there is one little annoyance - the integrated HDMI = output does not work. So I want to change that. >>>=20 >>> As we are on ARM my first intention was looking into the device tree = for the rk3328. I compared it to Linux device tree and also found some = missing parts. My next step was looking into the drivers itself and as = the Linux drivers sources are available here = https://github.com/torvalds/linux/tree/master/drivers/gpu/drm/rockchip I = got some idea how the corresponding driver should look like. >>>=20 >>> However, I am unsure how I should proceed getting HDMI to work. = Accodring to https://wiki.freebsd.org/arm/RockChip HDMI works for the = rockchip rk3399 but I could not find any drivers neither in the = freebsd-src or drm-kmod (I am new to FreeBSD so i don't know if this is = even the right place to look for). I hope someone with more technical = knowledge about FreeBSD or HDMI can provide me with some guidance on = where I have to look and work on. >>>=20 >>> Greetings >>> pf0 >>>=20 >>>=20 >>=20 >>=20 >=20 >=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?D2B71952-7F81-4B19-A47A-252C4797D1E9>