From nobody Fri Sep 20 23:16:58 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 4X9SwK40d3z5XnKh for ; Fri, 20 Sep 2024 23:17:37 +0000 (UTC) (envelope-from marietto2008@gmail.com) Received: from mail-pg1-x52b.google.com (mail-pg1-x52b.google.com [IPv6:2607:f8b0:4864:20::52b]) (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 4X9SwJ6fSPz43G4 for ; Fri, 20 Sep 2024 23:17:36 +0000 (UTC) (envelope-from marietto2008@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pg1-x52b.google.com with SMTP id 41be03b00d2f7-70b2421471aso1688880a12.0 for ; Fri, 20 Sep 2024 16:17:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1726874255; x=1727479055; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=hpWzNGzCoiJ4Yn5jPpJys3tIYQLPxj/JWylcPAd6yGc=; b=GCjIsouS+RoRjO6PMu8vrjt022gUVwNyCIXDvpFqraEa6MbkD5rldRV9eYsqQ1nHTk rFIokWpZiMfa1SP8QQecRrzgzR/GU0+AbnPaBLcN9RrAL+BYs4e0ASQA6+LwvAg4Mxjg tqNzn4UcIgZ1ekaCAzKSATTo4xv4dURCNF53p1CNjYtUle9Gufyr9w7Fl3LaHc6PklZh L1/SASxKdsF1ejdgnE7VMWgrx1PMcPwV5O+gJEWUDWgYFQrVDuDJDrUAEKHLJrDytMu9 ZBpuomCFPiUZcKyltdqk6A2MzXZavKAr8aB6teLhDbfLD9zw0Po460NfzNOsskfQGFPH snLA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1726874255; x=1727479055; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=hpWzNGzCoiJ4Yn5jPpJys3tIYQLPxj/JWylcPAd6yGc=; b=cbgvC0nTvPm4tH1W1knI8krkd0/qN4+MllyXQFjFm637N4IwmEmi9X81d+E09JXbVD ZwUWlbJOWAqRts3vsTRyurGkvIJoEfEQBJeL+tZf0ZTEOGqQw3Y+5aSdvNn3zsaWLfMe qYH2X3bVH+cf/qJnYOigzcEmdJsdZZDHImL4wE8chEeaidAa2VfQzESwmjuRjfh4CzsB wLMIEAM42kDWUJ+fIDwz6GGi0HjdPHi7jSCce9KesBmv9HrU4IaUV7Ou6F0rQxATVvBe u2htpT3L7JU1RaBdGSWX71JFCOYS+KZZ15S3/PadhAZndFrADqG2CYinjxaJ+RVNLudj HXqQ== X-Gm-Message-State: AOJu0YzRBCwHLncQHsaHXaEtnqiIH8/ZUZlLAXuwUNQJ4dUineLbFvjO RyNIVl9PHBk4iNJbTeqKRefH5KY1jnyzW9UtA8vyVfDv03MJcfUSv0i0naHq7NvmCCrNLSdEvYh nzKox/iqbLK84Xp5WXHjh3kgIM1k= X-Google-Smtp-Source: AGHT+IEwD/yooSFNgJHREkDKSe1MZdeChgVUttZR95dGTCzzrMfNUZ1xYRoSHcymWc3XEY3Zk1CZQ8jix5ptOf+eIpQ= X-Received: by 2002:a17:90b:4c07:b0:2d8:cd04:c8f0 with SMTP id 98e67ed59e1d1-2dd7f763a86mr5953674a91.39.1726874255316; Fri, 20 Sep 2024 16:17:35 -0700 (PDT) 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 References: <5kADboXE-OUia2ncm13XjDesvDmjB3tjWSyr3ytCpa5XYof9xOrL9AbRownQoRG9eJcJpYswqjbMt0P0XiZfs7KNNfiNF7vQ93m72mm_Fyk=@protonmail.com> <4F94C5BF-B5D8-4EA0-8B4E-695BBC28D693@googlemail.com> In-Reply-To: <4F94C5BF-B5D8-4EA0-8B4E-695BBC28D693@googlemail.com> From: Mario Marietto Date: Sat, 21 Sep 2024 01:16:58 +0200 Message-ID: Subject: Re: Rockchip RK3328 Rock64 HDMI To: =?UTF-8?Q?Klaus_K=C3=BCchemann?= Cc: freebsd-arm@freebsd.org Content-Type: multipart/alternative; boundary="0000000000008f61da0622953e90" X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4X9SwJ6fSPz43G4 X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated --0000000000008f61da0622953e90 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello to everyone. Recently I've bought the RockPro64 with the RockChip RK3399,this one : https://pine64.org/devices/rockpro64/ I would like to know if FreeBSD is affected by the same bug,please. I can't use it if the HDMI doesn't work. On Sat, Sep 21, 2024 at 1:11=E2=80=AFAM Klaus K=C3=BCchemann wrote: > First time since years I switched the dusty Rock64 on :-) > yes, you=E2=80=99re 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 > =E2=80=A6 > 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) > > I guess you don`t want to port any linux drivers at first attempt :-) but > instead fix the issue > to get the framebuffer driver working( with it`s restrictions e.g. no 4K) > > Regards > K. > > > > Am 20.09.2024 um 19:22 schrieb Christoph Pfaller >: > > > > Hello! > > > > 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 outp= ut > does not work. So I want to change that. > > > > As we are on ARM my first intention was looking into the device tree fo= r > the rk3328. I compared it to Linux device tree and also found some missin= g > 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. > > > > 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 wher= e > I have to look and work on. > > > > Greetings > > pf0 > > > > > > > --=20 Mario. --0000000000008f61da0622953e90 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello to everyone.

Recently I've bought the RockPro64 with the RockChip RK3399= ,this one :


<= div>I would like to know if FreeBSD is affected by the same bug,please. I c= an't use it if the HDMI doesn't work.

On Sat, Sep 21, 202= 4 at 1:11=E2=80=AFAM Klaus K=C3=BCchemann <maciphone2@googlemail.com> wrote:
First time since years I switched = the dusty Rock64 on :-)
yes, you=E2=80=99re 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
=E2=80=A6
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:=C2=A0 send dmesg to htt= ps://dmesgd.nycbug.org<https://dmesgd.nycbug.org/>)

I guess you don`t want to port any linux drivers at first attempt :-) but i= nstead fix the issue
to get the framebuffer driver working( with it`s restrictions e.g. no 4K)
Regards
K.


> Am 20.09.2024 um 19:22 schrieb Christoph Pfaller <pfaller@protonmail.com>:<= br> >
> Hello!
>
> I recently switched to FreeBSD on my Rock64 due to appearing kernel pa= nics 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.
>
> As we are on ARM my first intention was looking into the device tree f= or the rk3328. I compared it to Linux device tree and also found some missi= ng 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/rockchi= p I got some idea how the corresponding driver should look like.
>
> However, I am unsure how I should proceed getting HDMI to work. Accodr= ing to https://wiki.freebsd.org/arm/RockChip HDMI works for= the rockchip rk3399 but I could not find any drivers=C2=A0 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 know= ledge about FreeBSD or HDMI can provide me with some guidance on where I ha= ve to look and work on.
>
> Greetings
> pf0
>
>




--
Mario.
--0000000000008f61da0622953e90--