From nobody Wed Sep 25 16:56:07 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 4XDNFW0nRsz5XS65 for ; Wed, 25 Sep 2024 16:57:35 +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 4XDNFV3kH0z4ZPc for ; Wed, 25 Sep 2024 16:57:34 +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=1727283447; 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=GD/hnrvkY0drUz0t2L7tsqPNzoFSO9LM5tRklemB3Ws=; b=LG4Yh0qaHczbw9RiRFg/2o27HmoR+oQ0L59m+En6bOzKHlGOX0Kr4NnYZSnyL/yweDjW4M 2xrqKS857Jci2hXRNsOBml5baSwOWOzQlOMlk9I+5sAjwOEnb8IlHueMzaVcJRJZoBBGHh jgz9/T3+aEjR5Ov7fqhrqZ7IrGx6p/w= 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 2996929c (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Wed, 25 Sep 2024 16:57:27 +0000 (UTC) Date: Wed, 25 Sep 2024 18:56:07 +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: <20240925185607.8fc021905b94c98c002d3dec@bidouilliste.com> In-Reply-To: <577A672D-E92B-446D-9C81-428FC2121E09@googlemail.com> References: <5kADboXE-OUia2ncm13XjDesvDmjB3tjWSyr3ytCpa5XYof9xOrL9AbRownQoRG9eJcJpYswqjbMt0P0XiZfs7KNNfiNF7vQ93m72mm_Fyk=@protonmail.com> <4F94C5BF-B5D8-4EA0-8B4E-695BBC28D693@googlemail.com> <20240921132533.8b8cf0229a38275128ef0ccc@bidouilliste.com> <20240921193608.d88ec27b1da889a52c1f6e3e@bidouilliste.com> <577A672D-E92B-446D-9C81-428FC2121E09@googlemail.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-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated 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: 4XDNFV3kH0z4ZPc X-Spamd-Bar: ---- On Wed, 25 Sep 2024 17:29:11 +0200 Klaus K=FCchemann wrote: > Well, ? estimation ..., > To say it in short: > While RK3399 HDMI even worked with fbsd-efifb on an old installation on m= y Rock960(which is the same gpu as the RockPro64) , > this will not happen for the RK3328/ Rock64. >=20 > In longer but simple words : > Needed 5 minutes to hack u-boot`s current version to get HDMI - output o= n the RK3328/ Rock64.. What's the hack ? > 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 ( wh= ich is glued in their drm). > So u-boot sets up it?s framebuffer based on this driver while it cannot b= e handed over to FreeBSD=20 > 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. > So from u-boot`s framebuffer(or whatever hdmi-output) the screen turns ba= ck to dark black exactly in the moment of the=20 > handover to fbsd kernel, no automatically efifb. > I don`t assume that a dedicated developer will port/write the necessary = hdmi-drivers=20 > for the outdated RK3328/Rock64 because (e.g in this thread) currently exa= ctly 1 person(not me) is known to need the glass console for that Soc...but= you never know?. >=20 >=20 >=20 > > Am 21.09.2024 um 19:36 schrieb Emmanuel Vadot : > >=20 > > On Sat, 21 Sep 2024 15:49:51 +0200 > > Klaus K=FCchemann wrote: > >=20 > >> Hi Manu, > >>=20 > >> thanks for letting me know. It`s the first time I looked deeper into t= his issue. > >> So you mean that adding RK3328 codes to your DRM-subtree is even neces= sary=20 > >> to get efifb console output ? >=20 > > No, efifb will automagically works if u-boot setup the display (which > > it should and did iirc but it's been a while) > >=20 > >> The current state of (at least my) Rock64 is a complete HDMI blank scr= een 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 t= here a specific Rockchip bug somewhere???=20 > >=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. >=20 >=20 --=20 Emmanuel Vadot