From nobody Sat Sep 21 17:36:08 2024 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4X9xKJ75gSz5XhCh for ; Sat, 21 Sep 2024 17:37:24 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mx.blih.net (mx.blih.net [212.83.155.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4X9xKJ2Gp9z3xD4 for ; Sat, 21 Sep 2024 17:37:24 +0000 (UTC) (envelope-from manu@bidouilliste.com) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bidouilliste.com; s=mx; t=1726940242; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=1+wjBcyU/KFvszC90hTbqCwQr2iHU18MwECJbh7+NgE=; b=PErRKnBTsp4hmMNnXJ0bXT92QhqBcTvJDuj39nF8kf80SUrxCI9DcbKRLDByTXY/D5CrLP HSHJ/hkBfiHiDpA4gBhDk/+3a1/L84HhyAAYdCksqImiWgV3vi/7g4FP7lIbDvoCD11z3/ 60F8xki8CteixPpCsdO5youFx6CENc4= Received: from skull.home.blih.net (lfbn-lyo-1-2174-135.w90-66.abo.wanadoo.fr [90.66.97.135]) by mx.blih.net (OpenSMTPD) with ESMTPSA id b27b48a8 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Sat, 21 Sep 2024 17:37:22 +0000 (UTC) Date: Sat, 21 Sep 2024 19:36:08 +0200 From: Emmanuel Vadot To: Klaus =?ISO-8859-1?Q?K=FCchemann?= Cc: freebsd-arm@freebsd.org Subject: Re: Rockchip RK3328 Rock64 HDMI Message-Id: <20240921193608.d88ec27b1da889a52c1f6e3e@bidouilliste.com> In-Reply-To: References: <5kADboXE-OUia2ncm13XjDesvDmjB3tjWSyr3ytCpa5XYof9xOrL9AbRownQoRG9eJcJpYswqjbMt0P0XiZfs7KNNfiNF7vQ93m72mm_Fyk=@protonmail.com> <4F94C5BF-B5D8-4EA0-8B4E-695BBC28D693@googlemail.com> <20240921132533.8b8cf0229a38275128ef0ccc@bidouilliste.com> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd15.0) List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:12876, ipnet:212.83.128.0/19, country:FR] X-Rspamd-Queue-Id: 4X9xKJ2Gp9z3xD4 X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated On Sat, 21 Sep 2024 15:49:51 +0200 Klaus K=FCchemann wrote: > Hi Manu, >=20 > 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 necessar= y=20 > 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=20 > to get any HDMI-output.u-boot or firmware or your drm-subtree, or is ther= e a specific Rockchip bug somewhere???=20 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. > Regards > K. >=20 >=20 > > Am 21.09.2024 um 13:25 schrieb Emmanuel Vadot : > >=20 > >=20 > > Hi Klaus, > >=20 > > On Sat, 21 Sep 2024 01:06:21 +0200 > > Klaus K=FCchemann 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 > >> You can attach dmesg there (or what I would prefer: send dmesg to htt= ps://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 : > >>>=20 > >>> Hello! > >>>=20 > >>> I recently switched to FreeBSD on my Rock64 due to appearing kernel p= anics when running the board with Linux. So far I enjoy the operating syste= m. 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 miss= ing parts. My next step was looking into the drivers itself and as the Linu= x drivers sources are available here https://github.com/torvalds/linux/tree= /master/drivers/gpu/drm/rockchip I got some idea how the corresponding driv= er should look like. > >>>=20 > >>> However, I am unsure how I should proceed getting HDMI to work. Accod= ring to https://wiki.freebsd.org/arm/RockChip HDMI works for the rockchip r= k3399 but I could not find any drivers neither in the freebsd-src or drm-k= mod (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 H= DMI 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 >=20 >=20 >=20 --=20 Emmanuel Vadot