From nobody Wed Sep 25 15:29:11 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 4XDLHp58BTz5XMSC for ; Wed, 25 Sep 2024 15:29:26 +0000 (UTC) (envelope-from maciphone2@googlemail.com) Received: from mail-lf1-x129.google.com (mail-lf1-x129.google.com [IPv6:2a00:1450:4864:20::129]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XDLHn5Z63z4Qpv for ; Wed, 25 Sep 2024 15:29:25 +0000 (UTC) (envelope-from maciphone2@googlemail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=googlemail.com header.s=20230601 header.b="XEk0/Ew0"; spf=pass (mx1.freebsd.org: domain of maciphone2@googlemail.com designates 2a00:1450:4864:20::129 as permitted sender) smtp.mailfrom=maciphone2@googlemail.com; dmarc=pass (policy=quarantine) header.from=googlemail.com Received: by mail-lf1-x129.google.com with SMTP id 2adb3069b0e04-53655b9bbcdso8374100e87.2 for ; Wed, 25 Sep 2024 08:29:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20230601; t=1727278164; x=1727882964; darn=freebsd.org; h=message-id:in-reply-to:to:references:date:subject:mime-version :content-transfer-encoding:from:from:to:cc:subject:date:message-id :reply-to; bh=RhLrljbFA2887KdGm87xMvmgQEj8IJpzqfkHx266uqU=; b=XEk0/Ew0QpedaINMfRkjyNqRa8T3ZCWz2bZv7IJOPbDZV/WO0X6gVwKDy8dh4YQTf0 zd8haemhAuUEmHbL0FDT3apDEcXbtteyKLlt+lV0iwBMhCrgJzDEQxgxdy3VtvfKxW5s qiSYm+otqsJsMZoB5BaQAaUKcrjgJfe1GbccDiz4QYQBJoz+HbLNtNsMKDX1cu6qGhB0 THXqyFW1SKbZCRM9zxMClN5SQE3pj5xa3/VkfhTpOyIN2mfWIO2dBH14/CM1vhvOrCQi cRLDlslqpopBMptF9HungQpFU33JLme8eYNxtmLcjbAA8jz1mpG/Xp1lK7fHxVpbcqyV U8fA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1727278164; x=1727882964; h=message-id:in-reply-to:to:references:date:subject:mime-version :content-transfer-encoding:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=RhLrljbFA2887KdGm87xMvmgQEj8IJpzqfkHx266uqU=; b=qvwZRCVA06CmEbJjtVeFte2LWnuD0q/kXmmM0ofOQ14/+11lU1MVRMv8UHXFxtnIBC PEp3AH+ABoivZU+PgnRylxbAip9/vBRY/BDvMoupUHt9h/6be9E16EwAQn8VnKEz39rM YYA7B744aYIgyAO5Rd1c4VkJiilymSQxDg9CTjEwQMBtA8s3viYfc6RFo5a+Uhvk19Jg MkJT4tRoJVBMMgDGRWL7OjUJUYD6xMVcWKHjQRIEb3XLBKhdxzkU7TzgZFLuGIF/AUqV FJbibgeRCqbGlqPaewsRonFGhV3oy29sAdrjp8efO53fV3ChE60IgwZq2Jw+iRiTtuGx lFTQ== X-Forwarded-Encrypted: i=1; AJvYcCV0N2z0E/VlSjMBLkcCMbZGn2qHGI466AGob9woYIC93fzuEF4gOOIFExKew+ds52onRqeYKxr0KN0ywg==@freebsd.org X-Gm-Message-State: AOJu0YxKEUlXJSJcHVuUN0cXaXFm0EOhh4NMI0tpzPGaLz+fKb710GNE d9skdfm8Anb1AEE13lIWMbhVGUSqH50Tt6JVUqBZddBOGQKkqucFfYtQHXeJ X-Google-Smtp-Source: AGHT+IGZX6sbAGdGVo+Cp4P1bLenfUYlMqe3PftGCYJtD2T31+QkIMUBjZeve8OWkKe1ajpYlp27MA== X-Received: by 2002:a05:6512:b1a:b0:530:daeb:c1d4 with SMTP id 2adb3069b0e04-5387048aeecmr2135180e87.12.1727278163294; Wed, 25 Sep 2024 08:29:23 -0700 (PDT) Received: from smtpclient.apple (dynamic-046-114-020-130.46.114.pool.telefonica.de. [46.114.20.130]) by smtp.googlemail.com with ESMTPSA id a640c23a62f3a-a9392f5485asm221991566b.88.2024.09.25.08.29.22 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 25 Sep 2024 08:29:22 -0700 (PDT) From: =?utf-8?Q?Klaus_K=C3=BCchemann?= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable 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 (Mac OS X Mail 16.0 \(3818.100.11.1.3\)) Subject: Re: Rockchip RK3328 Rock64 HDMI Date: Wed, 25 Sep 2024 17:29:11 +0200 References: <5kADboXE-OUia2ncm13XjDesvDmjB3tjWSyr3ytCpa5XYof9xOrL9AbRownQoRG9eJcJpYswqjbMt0P0XiZfs7KNNfiNF7vQ93m72mm_Fyk=@protonmail.com> <4F94C5BF-B5D8-4EA0-8B4E-695BBC28D693@googlemail.com> <20240921132533.8b8cf0229a38275128ef0ccc@bidouilliste.com> <20240921193608.d88ec27b1da889a52c1f6e3e@bidouilliste.com> To: Emmanuel Vadot , freebsd-arm@freebsd.org In-Reply-To: <20240921193608.d88ec27b1da889a52c1f6e3e@bidouilliste.com> Message-Id: <577A672D-E92B-446D-9C81-428FC2121E09@googlemail.com> X-Mailer: Apple Mail (2.3818.100.11.1.3) X-Spamd-Result: default: False [-2.73 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.86)[-0.859]; R_MIXED_CHARSET(0.63)[subject]; DMARC_POLICY_ALLOW(-0.50)[googlemail.com,quarantine]; MV_CASE(0.50)[]; R_DKIM_ALLOW(-0.20)[googlemail.com:s=20230601]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; TO_DN_SOME(0.00)[]; FREEMAIL_ENVFROM(0.00)[googlemail.com]; ARC_NA(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; FREEMAIL_FROM(0.00)[googlemail.com]; FROM_HAS_DN(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[googlemail.com:+]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; DWL_DNSWL_NONE(0.00)[googlemail.com:dkim]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::129:from] X-Rspamd-Queue-Id: 4XDLHn5Z63z4Qpv X-Spamd-Bar: -- Well, =E2=80=A6 estimation ..., To say it in short: While RK3399 HDMI even worked with fbsd-efifb on an old installation on = my Rock960(which is the same gpu as the RockPro64) , this will not happen for the RK3328/ Rock64. In longer but simple words : Needed 5 minutes to hack u-boot`s current version to get HDMI - output = on the RK3328/ Rock64.. 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=E2=80=99s framebuffer based on this driver while it = cannot be handed over to FreeBSD=20 because it`s not implemented FreeBSD (as Manu said) . So from u-boot`s framebuffer(or whatever hdmi-output) the screen turns = back 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 = exactly 1 person(not me) is known to need the glass console for that = Soc...but you never know=E2=80=A6. > Am 21.09.2024 um 19:36 schrieb Emmanuel Vadot : >=20 > On Sat, 21 Sep 2024 15:49:51 +0200 > Klaus K=C3=BCchemann wrote: >=20 >> 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 = necessary=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) >=20 >> 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???=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.