From nobody Tue Sep 17 20:19:15 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 4X7Y693vn5z5VrFY for ; Tue, 17 Sep 2024 20:19:29 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-pl1-x632.google.com (mail-pl1-x632.google.com [IPv6:2607:f8b0:4864:20::632]) (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 4X7Y685t0yz47XZ for ; Tue, 17 Sep 2024 20:19:28 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bsdimp-com.20230601.gappssmtp.com header.s=20230601 header.b=QgB3joEK; dmarc=none; spf=none (mx1.freebsd.org: domain of wlosh@bsdimp.com has no SPF policy when checking 2607:f8b0:4864:20::632) smtp.mailfrom=wlosh@bsdimp.com Received: by mail-pl1-x632.google.com with SMTP id d9443c01a7336-2068acc8a4fso46666885ad.1 for ; Tue, 17 Sep 2024 13:19:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1726604367; x=1727209167; 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=om76sWyPw5EaJSeOBtO6ZWhprLkJFz/le7KcA9CLqJE=; b=QgB3joEK+W1zczRML+Jzzpk2YsPB48i2+TdVCU7g6u3V3Rgvi5iRb4Ypk0WAGLf8H1 FKYO7tTWX/oKy82g05qrFX12WMPB6d+luM+uWw6wm6WKwIofhJTiKx+HASkPmmL7xsDo q/WARTxWV1tualvTSvpi62MN9hTpVvnUvc5CVO/FJu/EOi2QHjPzXKXhIuexcuY8h+0p MXwBu/QUIERvQUyNkAuqdywFgLQ2htYE8Nh1kC2S7+UaV9TtRS9+QqM4rXrWsg2HOra2 nx5vGS2ccu9B1zEU3khi8R8t6KnJ4SmuZu9BTXpkBuOP4wesaW93Py8wiOzR27wCC7nn 7bdQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1726604367; x=1727209167; 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=om76sWyPw5EaJSeOBtO6ZWhprLkJFz/le7KcA9CLqJE=; b=C7OWysO8751UkLPP2k4a9NiwL9CiHpsjfptyPmuxgI+oVdfxThfFH6IEA7XhlRihx+ q2kPf+lOZVrsyCbX+sAW+v04bOqwug2yQ2KnBBGM7dvk2z1CVfCBajxj+WbJGwR6Y309 iJnQiMTMRGNu2EgqjlanqpBbExJo/enGAh2Y9AAW5+lf1iuAKm7097F66+AP/jVJMimT zI7PhAesN2DvvbgELtRW5DXbyN0vwPb70hhwu8Zm2xvhv9oqSeuT3z/ueM2w1bieRnNU t6K2MyLP7PSks8bYRgTe2X8q4n0W9nBNo2jpYQMVnAxZklxE+tOqWVajtDRIB4uM1A2y wleg== X-Gm-Message-State: AOJu0YzWarcl3IeOCH9aAQgUKzWXjrs1lzxu+9+YIdWcWj23kCo5ovPd NrEl2KQENhRNR9Jjx9q0G+8t3yaGFlYOZ2rFn0OQhs+Pk7EWq/qFK4cNWIfDSpjmnGugvvVDLUj 6ksxpz/D1MKz3+0sR+zUzD2txhLTEv9CuNCJVgw== X-Google-Smtp-Source: AGHT+IHbx3omiIb3/M74B3lnR+pvA+cp/tNGNaHE7Ablaa2Zbsd8kEbnwoBs0DGud5N+9YsaGlQcBQaT/wvWfo3QIjw= X-Received: by 2002:a17:90b:3a8f:b0:2c9:9643:98f4 with SMTP id 98e67ed59e1d1-2dbb9dbd708mr22423184a91.5.1726604367317; Tue, 17 Sep 2024 13:19:27 -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: <276f57f2-5194-cad1-d859-e49b2bce2580@pobox.com> <69E08B38-7388-46A6-8864-20074BFFF8F4@yahoo.com> <88d2cc76-f980-600e-0da4-2fa1070d76ba@pobox.com> <6b848423-bdd1-b215-889a-1f07e5064412@pobox.com> In-Reply-To: <6b848423-bdd1-b215-889a-1f07e5064412@pobox.com> From: Warner Losh Date: Tue, 17 Sep 2024 21:19:15 +0100 Message-ID: Subject: Re: Beaglebone Black/Green/Blue support (volunteering) To: Zach Metzinger Cc: freebsd-arm@freebsd.org Content-Type: multipart/alternative; boundary="000000000000fb6d1d062256674a" X-Spamd-Bar: -- X-Spamd-Result: default: False [-3.00 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.999]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20230601.gappssmtp.com:s=20230601]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ARC_NA(0.00)[]; TO_DN_SOME(0.00)[]; MISSING_XM_UA(0.00)[]; R_SPF_NA(0.00)[no SPF record]; DMARC_NA(0.00)[bsdimp.com]; RCPT_COUNT_TWO(0.00)[2]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; FROM_HAS_DN(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::632:from]; TO_MATCH_ENVRCPT_SOME(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; RCVD_TLS_LAST(0.00)[]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; DKIM_TRACE(0.00)[bsdimp-com.20230601.gappssmtp.com:+] X-Rspamd-Queue-Id: 4X7Y685t0yz47XZ --000000000000fb6d1d062256674a Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sat, Sep 14, 2024 at 3:45=E2=80=AFPM Zach Metzinger = wrote: > On 9/13/24 17:06, Warner Losh wrote: > > Yea, the TI support isn't in GENERIC, but you can still build a the > > TI kernel you need for this. > > > > It's broken on -current (which is why it isn't in GENERIC) due to DTS > > changes in Linux (there's a lot of churn there, and we need someone > > that can help us keep up as we import new DTS from Linux). > > > > armv7 will be in 15, so if you get it working, and plan on sticking > > around to keep it working, we should get that into main. > I've been able to boot 13.4 on my BBG, albeit with some complaining from > the kernel and what appears to be horrifically-slow SD card I/O. I've > got a TFTP/NFS server but haven't tried booting/mountroot via that path > just yet. > > I'll take a look at -current and the Linux device tree files for this > board. I'm familiar enough with device trees (having used SunOS and > Solaris on many things sun4c, 4m, .. back in my admin days). > Sounds good. The issues are all that the nodes in the FDT have changed from what they used to be. You might find yourself finding 'stable' points just before DTS imports from Linux you can use to puzzle out what's going wrong. Warner > --- Zach > --000000000000fb6d1d062256674a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Sat, Sep 14, 2024 at 3:45=E2=80=AF= PM Zach Metzinger <zmetzing@pobox.= com> wrote:
On 9/13/24 17:06, Warner Losh wrote:
> Yea, the TI support isn't in GENERIC, but you can still build a th= e
> TI kernel you need for this.
>
> It's broken on -current (which is why it isn't in GENERIC) due= to DTS
>=C2=A0 changes in Linux (there's a lot of churn there, and we need = someone
> that can help us keep up as we import new DTS from Linux).
>
> armv7 will be in 15, so if you get it working, and plan on sticking > around to keep it working, we should get that into main.
I've been able to boot 13.4 on my BBG, albeit with some complaining fro= m
the kernel and what appears to be horrifically-slow SD card I/O. I've <= br> got a TFTP/NFS server but haven't tried booting/mountroot via that path=
just yet.

I'll take a look at -current and the Linux device tree files for this <= br> board. I'm familiar enough with device trees (having used SunOS and Solaris on many things sun4c, 4m, .. back in my admin days).

Sounds good. The issues are all that the nodes in the= FDT have changed
from what they used to be. You might find yours= elf finding 'stable' points just
before DTS imports from = Linux you can use to puzzle out what's going wrong.

Warner
=C2=A0
--- Zach
--000000000000fb6d1d062256674a-- From nobody Wed Sep 18 06:44:06 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 4X7pz8256mz5WLXS for ; Wed, 18 Sep 2024 06:44:20 +0000 (UTC) (envelope-from freebsd-arm-freebsd-org097@ketas.si.pri.ee) Received: from green.sau.si.pri.ee (d004-fea2-0bff-021e-13e8-8437-07d0-2001.dyn.estpak.ee [IPv6:2001:7d0:8437:13e8:21e:bff:fea2:d004]) (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 4X7pz673STz43cb for ; Wed, 18 Sep 2024 06:44:18 +0000 (UTC) (envelope-from freebsd-arm-freebsd-org097@ketas.si.pri.ee) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=ketas.si.pri.ee header.s=ketas-si-pri-ee-20240416002854-4096 header.b=S1i7BH81; dmarc=pass (policy=reject) header.from=ketas.si.pri.ee; spf=pass (mx1.freebsd.org: domain of freebsd-arm-freebsd-org097@ketas.si.pri.ee designates 2001:7d0:8437:13e8:21e:bff:fea2:d004 as permitted sender) smtp.mailfrom=freebsd-arm-freebsd-org097@ketas.si.pri.ee X-Original-To: freebsd-arm@freebsd.org DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=ketas.si.pri.ee; s=ketas-si-pri-ee-20240416002854-4096; t=1726641848; bh=cwQTd8r3IFjFiD7Lmd1xoaNlzDmG0Cy9F/QxeG8VlMI=; h=Date:From:To:Subject:In-Reply-To:References; b=S1i7BH81kjR3fn9ItavuqviYx/LhH8oHKBxV7bZB9mmln4sX4l898DrRwqeVSzANL Vq8VXb/jenRL4iVkg2Xk9mf9bN/CaKBUG4xoTmV8VLL4TfSMCq+gJnyRD+6gdRRE5h fh3BOLm0oGMLVPFU4Sgf4QpLhT2ydSUWF0jwANN4+d/693irGUJVoNWIUABxlYOEk2 KetY0bMZMjn1Oxc1QjT3QemxAe4Zx+sEZBdRwQAHM4dH7+eK8V6A+R9eVTM24f0Hkk r6rHro9HCgoGXOCE7bUBfd8kVyY+oFnhj/paM+VRGz/0meUXOZwLLP9Eu7dgvpw+TA Uk6EO6pUQ58KyqLa3ftj+seq9xEZUj1Gr5yiW4oLkkTT3KB+pepa/0pYJAnDiO7Fo3 doC+NrM9xSC1gYgxJF3FatrkSIlUTaN3//vwc4Tv5cbyfYZcXRS+Rugn0/+QXgvO0d /GgaJJE1iMlwW6vHdupG/N8WwBPNVfL7JdTG8rpL5WfkZbgdwL0Eakyp5cF1oKzwsL vskd2XGK8byWE8blOwB6QQlmmYUZkr2jkvkoKK0vf8mIrqAPjfG06R+Um8RcsJB9sj sgg7n3O8uVJule5V1n3N72syngbFZEaqyAKwHik9np/o6zXEcFZ2ySiWE4GJMB8Yym xMJKZiU3DZxQ9AKE9LhiIMCc= Received: from [IPv6:::1] (0114-0000-0000-0000-13c8-8437-07d0-2001.dyn.estpak.ee [IPv6:2001:7d0:8437:13c8::114]) (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) (No client certificate requested) by forestgreen.jails.green.sau.si.pri.ee (Postfix) with ESMTPSA id C46D6594439 for ; Wed, 18 Sep 2024 09:44:07 +0300 (EEST) Date: Wed, 18 Sep 2024 09:44:06 +0300 From: Sulev-Madis Silber To: freebsd-arm@freebsd.org Subject: Re: Beaglebone Black/Green/Blue support (volunteering) User-Agent: K-9 Mail for Android In-Reply-To: References: <276f57f2-5194-cad1-d859-e49b2bce2580@pobox.com> <69E08B38-7388-46A6-8864-20074BFFF8F4@yahoo.com> <88d2cc76-f980-600e-0da4-2fa1070d76ba@pobox.com> <6b848423-bdd1-b215-889a-1f07e5064412@pobox.com> Message-ID: <4BEC1DC0-7528-4B4B-8FD0-254BD7BF1BD9@ketas.si.pri.ee> 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=utf-8 Content-Transfer-Encoding: quoted-printable X-Spamd-Bar: / X-Spamd-Result: default: False [-0.79 / 15.00]; HFILTER_HOSTNAME_5(3.00)[d004-fea2-0bff-021e-13e8-8437-07d0-2001.dyn.estpak.ee]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.89)[-0.887]; DMARC_POLICY_ALLOW(-0.50)[ketas.si.pri.ee,reject]; R_SPF_ALLOW(-0.20)[+ip6:2001:7d0:8437:1300::/56]; R_DKIM_ALLOW(-0.20)[ketas.si.pri.ee:s=ketas-si-pri-ee-20240416002854-4096]; ONCE_RECEIVED(0.10)[]; MIME_GOOD(-0.10)[text/plain]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:3249, ipnet:2001:7d0::/32, country:EE]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_ONE(0.00)[1]; RCVD_TLS_ALL(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DKIM_TRACE(0.00)[ketas.si.pri.ee:+] X-Rspamd-Queue-Id: 4X7pz673STz43cb i'm looking forward to replace current from 2014 in my one singular bbb wit= h newer one is it only because fdt? i proposed to just use own fdt like earlier but pe= ople told sorry can't do that=2E to that i was like how about i supply my o= wn fdt then? then, why is fdt such a shitshow anyway? or it works in linux as is, or? o= r it changes often? to my still limited knowledge that just defines a hw, w= hy would it change, as hw doesn't? so am i correct, we throw that thing out just because it's super hard to u= se fdt from linux? whole armv7 32bit is bit weird too=2E looks like it's hanging on the edge = of trash can, along with whole 32bit, just to be waiting for to be pushed i= n=2E yet there are armv7 hw being sold=2E maybe even made still, can't be a= ll nos=2E like allwinner h3 i can understand the issues with 32bit but where's like good working 64bit= alternative=2E out of small hw, only raspberry pi? out of big hw, only arm= servers? i have h618 hw here, along with 13=2E* patches i obtained from forum, wait= ing for some tests=2E maybe someone else has interest in tiny recent arm hw= on fbsd while there, how do all the people dev for armv7? i use system qemu, but t= hat fails with any new current now=2E basically old current and old qemu bu= ilds ports=2E old qemu and new current doesn't boot=2E new qemu and new cur= rent doesn't boot=2E new qemu and old current doesn't build half a ports=2E= to be honest, old qemu and old qemu needs multiple tries to build some too= , funnily=2E i suspect mixes issues with qemu, fbsd and clang combination h= ere=2E not to mention that qemu is over 2000 times slower than c2d machine = on some tasks=2E yes, really, 2000 if embedded fbsd goes away, that would be a sad story=2E i'm actually curi= ous about using fbsd professionally=2E i know some others do too, but can't= figure out what hw should i choose where it actually stays supported? mayb= e i should wait for more standardized, less fragile arm platforms in the fu= ture? or maybe embedded is fragile by design? i currently look for hw simil= ar in performance of h3 but there could be others too, bit more powerful, m= aybe with video out, etc sad really, and all that existing hw seems to be supported by like single = person in fbsd=2E if anything happens, that hw is gone too somehow god i wish it would be as easy as with big machines=2E i386 is going but t= hat might be less of an issue (but i'm sure it's used too)=2E as amd64, eve= n old, is everywhere so any opinions with this arm situation? or whole embedded that is=2E fbsd contains lot of non server things=2E or = maybe they are server now=2E like wifi, bt, video=2E i wish it to stay unsure, i can't magically come up with bunch of usera and bunch of devs so= things stay healthy and i can also take and give advantage of this it's also super hard to maintain own code locally, etc=2E and embedded hw = tends to really like to stay=2E for over 10 years easily=2E i've seen many = embedded platforms appearing in fbsd and then quickly going out=2E while bi= g hw stays for, i mean, i've been using fbsd since v4=2E6, not that long, s= ome hw has been in for entire this time unsure what's other option here? use nbsd, use linux? god, some hw has bet= ter support on obsd=2E sad seems like fair bit of armv7 users are still there and i bet they also loo= k for 64bit extended support hw too=2E so how to get devs here too? i bet t= here are humans in this planet that are happy to dev for arm on fbsd enough= for it to work well From nobody Wed Sep 18 08:31:25 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 4X7sM01CnHz5Wd3R for ; Wed, 18 Sep 2024 08:31:40 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic312-23.consmr.mail.gq1.yahoo.com (sonic312-23.consmr.mail.gq1.yahoo.com [98.137.69.204]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4X7sLz456Mz4M28 for ; Wed, 18 Sep 2024 08:31:39 +0000 (UTC) (envelope-from marklmi@yahoo.com) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1726648296; bh=IZ6iIZ8ZQQYq8xmRxTzArdKATcsL/DXTY+Y3Tz0VFDA=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From:Subject:Reply-To; b=tJ6Gpg6LrHIFAeebVhGTFgxv74+B7EzTm/h0LHZrM6SsVkN59ecJh8LxM10KBMYvBU+ru4mL9/ps1CiW8Z7iRFW2c/C0KbumE5qMjo72+7jl6CNE908zXx1FmxW7KRrP5/ibBOnrFl7HKUHNstcL214uwYKu/cFvMvUgEuE0vqR3Gjm2WCW0T5s6tWj+Rgl2PqlBXUI3i4YnGyEr/VuVNxNEYwWIN0eTHNuLYRTa6SdVIlv9tMzNMBFEa62XcgekB7hk4s8umHE4m1r6CHdodvhoDh6VCkcwaoS6N4Z42xRWNy1mUnlJ42CXY2nEPUbrMH4Phe/bW8tqirxZNuP3OA== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1726648296; bh=wpFTo4qYJVCayJKZ7gluFQ/OTmBHfW1XUT4/TgO5sFJ=; h=X-Sonic-MF:Subject:From:Date:To:From:Subject; b=WA6yg7DKks4rcP21NRst+j7IE7ldVavmpxHoyl/NcGvU5dRqSrI5CNcpmqtm5NJAS87KFRM0//1dZ4ePtfSF7QMa76ViyQpk/OpoxEIruMtYON47GXQZ8S72zocpvgVcyb6jfY4rJmCg1Q64lg8GEu5hZjf6z2IGJpdqe6fABttftK+9zj9I5+kXP5p2EYlXTLGA+/0P/kg75I/7APuZUYGz1ar5FvUFu+OsOOARW9dUIni3tG56QOfa77PL9bwyDiTfUWxpIv44kPKK69XKOfBDGnjFy7WkCFig2WUjGk8rzFZIrfKsDD0FoYa8XubuH8cbfFuPOypyXax33GYe/g== X-YMail-OSG: bpYo6GIVM1llRp2h.ZfvvV4ezJSPcFF9BQMqDPJlauDj9crawaBOAmX3UFPkiwP lliyK6D2U7xoeYY5SoR_FOqdEpkWsSI6MCzoiVfh0J9TdThTSjWRzo6dS3eDya0_39iYoYqq6Ygm LcwRTNe4YPn19P5n5ZjTT8oSafz6ifZ82g.v7xhCrM.IKtG5foH5sIAtIHRiqYOTkPd7PjR89epF hNC6.sIO_cpApVtlLmQMGK2H5S44R.XuTF3SCEzPN9WObk_RKqSU70wN4MUnz3sSvrdHrGN8gjr4 lqlevqbrBMSGUJ4RtUCVn7dIkhtgXgfd1cOjwmkl6hJ7xtFfKxYCK96F17EEwM3k_PMGuYmUS8UR pCRqRGdKIM6Ic2kd9Mh4PfPcAesXuv6JwcepBCy4IBxOHV4tuQeBs2S5WxlKTfM8gHcOqCu5Wi9h gjEeh0EWh3GrqORWO5QqRcPRRHPrhg3JLHIdkjNeAY7tUJgMTENnXYQnMOadwcdtlgD9nfVRhysv .WFYeVFDJfYPP5lXRODXmmjpFe03lOQyXsriz9HqdlcfUyxNnBlFhrch6F.VDn5uYXTL5VpQY15I Kp739FO7bNYQKxNs_5_YSoV4YzN5lsFS5M3DPWTG.bqiAjsc3JRmc.9HaUUJ1hIoUBQH2ZiZu5N1 AolGun2xS3wq3mh9pdt8Xrf2Fqy83gHZz77XuHqHqpo17ip1KWEDjG.z2nFP.XsXVTrSFcN3GQF9 fYb7I8u5qZ8SoXIAUXNZ1vCFWt7OXYSHnUlN3qf97sbvTji3B8KDVOIeasxAeCw7Sh_lDRMKGMsC XCDL_IeiiImUuTDl5JyoD8iNKUqHd2DCiZPJ1tBfrA2sJx2b0EWWwEbCXOCa9jnMtl7aFIOlkDpt U6rQXABjcAF1t31.WCTzlYN0nA76zfGmxbt9eS1R2QQwDLiw6yztBnum3gACzLR3zpbiOzYMuP8Q ITQgWkQFbcwMKvbiy62pAk.lqTw4AfYZLYupChTpKgf70bAwDCdxu4q2XJMuBQPGfhnPhR7RvIhe giBaQjjIZ9hZj0i_GpmeWH4Eor13m5d_EgXCdrRKPIzADYHFJ.6SyiS5N6P9I8CYBgKmghpct5FP BRCvWFZPKzv9kyaFY1Fz8Hb5Lj14qDHgr3_63YMbGrj_ccTWq4nH6rpr5kVZwr7IiU611.QpSsy8 riDl3xB75ESXCFVzWBO17jTKJveNJEYUnNRnVGjLJd5G3jvNhXP7ijuP9GvnY0ukdL4dF3hRbxBD 1iac3qaARmrmR86EfA_nCjZJClDll70BSUZPQXIR_TC5E9ZEzUTP.bQjxux512jfOiVQhHn5Uwpq UIPIkvTZ_DXz.uvWG8.UtR2utQ24gU022ggiupdwktslD8njR1tMQTE.WAkeW4GK4PaNIEvTsoR2 6kQamNTEVyGOTzVnJIStUK2q8LZqtwqYjjpb.MB_1SvSds4VvQPmAhWgqKAjtK9I2yp8.aF8klQD gYcbpw9b1rvd_R5Gut3Vn129HHI1F8m5fiv7EMAAfl2VHpPQnWxfxnE8RZV4XHhIUxjk82LnGHza 2M8gu_.WFQWRC9eh2vzz.Lv1LcPKOL.EKtpQ73aW7oYeC8qNF2CZuxuSRxEpPQlPtcOoT9GUaPqP 3YjB8NEqtol_AtSzi35SEOm3j9DCAYO9wIVLZE5b_JAKhKoKW_6hzivvcw7ZBjqCGBsVP2W34uG9 vzJg9HKlxrdeG4Ga3wIIntrEzaxk.m0JGHMZ0Lbnr8EqSWQT5BGSf.br_xYM95FsMJAenfL0AlHj AnjNzXFnE4SFS8yvOUJdGhsTMjfKueDymXI09zqNARTUH1vXV2WQ9nzGnZUbQlVQ2W9SZN2pBvaQ l4qCgnBhJUOS38xKNAXZLR2g8gdTOVLUF9iqRQzXZAopc5dNB3eogSF_DpPBnn20ra0tjtMxvxDQ Nw973srEPRZClFl926uveAbp6aKXhQKHbt1n2OUEhylkk6kklVfw3ms1aND_pMAqLvbYwlBZ3pRm 8ATNhOhVC8tsEaKaM9SWH3mY6wd7famCKAKOMS3YJFeUAtSkh0_lloAdK2qnLFkpjXYloe9wQFNd 6eH_s7MUnlH3I_INuplv2WQdn4i6HfIkCKjHkiop19p9p9k5SdXJ9_YsSB9uhXzB7a0wdHtRlUY1 VyTeYYt4njJho2lyqvHdKw9M8OJLUQucKKcIX10uSCi_knjrRSB888FXgy0KGXkC6TUdgrRikIfH gA3mtkpMz54uc2Mt4ZNCGSJhoyM.U_8p79XnRFRKPGv90dwNIEBxhufmmtRj1IK4E8QNrtCOJmG9 tItXFzSxntvFT5LXJgw-- X-Sonic-MF: X-Sonic-ID: bb62cc86-83a3-46b6-ac3a-40d862db08ea Received: from sonic.gate.mail.ne1.yahoo.com by sonic312.consmr.mail.gq1.yahoo.com with HTTP; Wed, 18 Sep 2024 08:31:36 +0000 Received: by hermes--production-gq1-5d95dc458-rx7kt (Yahoo Inc. Hermes SMTP Server) with ESMTPA ID 9104c5cce45e04e1636bf7bfbb521045; Wed, 18 Sep 2024 08:31:35 +0000 (UTC) Content-Type: text/plain; charset=us-ascii 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 \(3776.700.51\)) Subject: Re: Beaglebone Black/Green/Blue support (volunteering) From: Mark Millard In-Reply-To: <4BEC1DC0-7528-4B4B-8FD0-254BD7BF1BD9@ketas.si.pri.ee> Date: Wed, 18 Sep 2024 01:31:25 -0700 Cc: freebsd-arm@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <8597295C-BC33-4F76-AF45-41753D3E47BA@yahoo.com> References: <276f57f2-5194-cad1-d859-e49b2bce2580@pobox.com> <69E08B38-7388-46A6-8864-20074BFFF8F4@yahoo.com> <88d2cc76-f980-600e-0da4-2fa1070d76ba@pobox.com> <6b848423-bdd1-b215-889a-1f07e5064412@pobox.com> <4BEC1DC0-7528-4B4B-8FD0-254BD7BF1BD9@ketas.si.pri.ee> To: Sulev-Madis Silber X-Mailer: Apple Mail (2.3776.700.51) X-Spamd-Bar: ---- 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:36647, ipnet:98.137.64.0/20, country:US] X-Rspamd-Queue-Id: 4X7sLz456Mz4M28 On Sep 17, 2024, at 23:44, Sulev-Madis Silber = wrote: > i'm looking forward to replace current from 2014 in my one singular = bbb with newer one >=20 > is it only because fdt? i proposed to just use own fdt like earlier = but people told sorry can't do that. to that i was like how about i = supply my own fdt then? >=20 > then, why is fdt such a shitshow anyway? or it works in linux as is, = or? or it changes often? to my still limited knowledge that just defines = a hw, why would it change, as hw doesn't? My understanding of the operating principles here: The FDT provides a mapping between the Linux kernel's way of working and the hardware. When Linux changes how the kernel works the Linux FDT tracks the redesign. The two are not independent. In essence, the FDT is a form of kernel data structure. Multiple distinct FDT's can describe the exact same hardware: the hardware of itself does not uniquely determine the FDT for that hardware. Some contexts have fairly stable Linux kernel designs and, so, fairly stable FDTs; others do not. So, one can get evidence about some of what is being significantly reworked over time in the Linux kernel via the seeing the repeated FDT restructuring over the time frame. This contrasts with other context's FDTs being stable because there is a lack of such Linux kernel driven changes to that FDT. So, when FreeBSD sees the linux FDT has changed and has to adjust for such, it is actually tracking some consequences of the Linux kernel rework activity that changed both the Linux kernel and the FDT. At least, that is my understanding. FreeBSD does not have the resources to develop and use its own FDT's overall and simply chooses to track an upstream source of a context's FDT(s) instead. In the case of RPi*'s, it is not mainline Linux FDT's that are tracked --but the FDT's are from a Linux kernel context. (I'm not sure if RPi*'s have the only non-main-line FDT's used.) > so am i correct, we throw that thing out just because it's super hard = to use fdt from linux? . . . How difficult or messy or frequently FDT tracking is involved varies widely across the various contexts. It is not a uniform global property for all Linux FDTs. . . . > while there, how do all the people dev for armv7? Many aarch64 systems can execute armv7 code and so serve as a means of building armv7 code with armv7 tools (armv7 jail's, armv7 chroot's, possibly even lib32). Such is generally more reliable and less time consuming than use of qemu for "cross-activity" many context that try to use qemu. The official FreeBSD armv7 packages are built on aarch64 systems that can execute armv7 code. This uses armv7 poudriere jails. It works a lot better than the historical qemu use on amd64 before these ampere[123] aarch64 machines were available (or were not yet used this way). Some folks use the likes of Windows Dev Kit 2023's or RPi4B's or RPi5B's for such activities of their own. (Apple M1/M2/M3/M4 do not support armv7 code and so are not example contexts for doing these sorts of things without qemu involved.) =3D=3D=3D Mark Millard marklmi at yahoo.com From nobody Wed Sep 18 09:06:14 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 4X7t783Pq2z5WjsQ for ; Wed, 18 Sep 2024 09:06:28 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-pl1-x62e.google.com (mail-pl1-x62e.google.com [IPv6:2607:f8b0:4864:20::62e]) (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 4X7t775DNWz4TkN for ; Wed, 18 Sep 2024 09:06:27 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pl1-x62e.google.com with SMTP id d9443c01a7336-1fc47abc040so52091895ad.0 for ; Wed, 18 Sep 2024 02:06:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1726650386; x=1727255186; 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=q+tL/X/CQZvvizK/F95AX6XlIRHx75/CrYLNvTM7Flg=; b=PUJr3bx+LQGq4dBKYiNq6kvvvHoSnlJvTJ5r9GXzuU7WWrYAufepwg56tHu0nMi2en UBlHha1aPlM9/7v2mLo3Tau/3NrWjPV3sf0tG6S5qL+Jeo1nwHFPNyE+uSah7asJ9+sz J9YDmyQphMktDB7++bdIy2on4vjH3AaiqvVjgesEL6vb7m4afV0KZvz+AjsqjHc98z2j Dju6PVWKeUkDcd7BdGBpgA/gXNwYNWc5mHjglS0mLI6FOevucXM9X/m+kfcXveWeXKLR zevZLwxutA/91twIzHgMCZp4P18FmvQ9VsJ0A9x+cXsupjnfP4JgZDh5k9Z+9cnCNczv 41VQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1726650386; x=1727255186; 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=q+tL/X/CQZvvizK/F95AX6XlIRHx75/CrYLNvTM7Flg=; b=gME30XgTKotNoXH8rRCXS6nudlCM/e2qjL6BaIycvbDREiemdGG+uobZ+heFnf/aO4 LvAguEwpTB3I0vd7bzWrLlc1MRPXC3Teq0j7NGKcOffXOkIxEZPSJLop3+HUdlw3Mq3H iIrEnjZuuj0wTVXY7hCGotLfKQKlZUnO0kMPM9kvtX4QS1FCmSWZkCS7MPFhiaHUqT0w Dq4ryxR9EKbp0I3dS6jXsDDWxdRcUfhEzDRTXD2B3tPzJeNEKGnI2/CmimT0K1dTNOF6 1jgePvQRStRr0DFDKcnCT9MuTT/J1Ha1zIQ5ztSoHVVaWQp6HW86Aypiz1mVEmSlppbw BK+A== X-Gm-Message-State: AOJu0YxU2oWKuHVoOhHkvdbmSc5xe1wio6cT8hvL97H2mpXrZCGJuRvn 1IdeM63hc8fGdwBOtdykkJa83eHJ5ML/zZI2NLC4zXUfHxzO9abbgNwjDP2a/z7Ed1k07ShwMR6 vztfnXqvHh4ry75+EBxuSFM1cLxzEmH0omNjzeORlCHJMHvK4nSg= X-Google-Smtp-Source: AGHT+IH8ey2Vs9VKKIG6mj+1ebFYmJAHcv423q1ykiBMk7svZhoTPAxHLihrGX1aRuUhlE1BR9vszgd2rzndxvqSjhA= X-Received: by 2002:a17:90a:8814:b0:2d8:94d6:3499 with SMTP id 98e67ed59e1d1-2dba0068106mr21687367a91.37.1726650385962; Wed, 18 Sep 2024 02:06:25 -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: <276f57f2-5194-cad1-d859-e49b2bce2580@pobox.com> <69E08B38-7388-46A6-8864-20074BFFF8F4@yahoo.com> <88d2cc76-f980-600e-0da4-2fa1070d76ba@pobox.com> <6b848423-bdd1-b215-889a-1f07e5064412@pobox.com> <4BEC1DC0-7528-4B4B-8FD0-254BD7BF1BD9@ketas.si.pri.ee> In-Reply-To: <4BEC1DC0-7528-4B4B-8FD0-254BD7BF1BD9@ketas.si.pri.ee> From: Warner Losh Date: Wed, 18 Sep 2024 10:06:14 +0100 Message-ID: Subject: Re: Beaglebone Black/Green/Blue support (volunteering) To: Sulev-Madis Silber Cc: freebsd-arm@freebsd.org Content-Type: multipart/alternative; boundary="000000000000e840ff0622611e7d" X-Spamd-Bar: ---- 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:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4X7t775DNWz4TkN --000000000000e840ff0622611e7d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, Sep 18, 2024 at 7:44=E2=80=AFAM Sulev-Madis Silber < freebsd-arm-freebsd-org097@ketas.si.pri.ee> wrote: > i'm looking forward to replace current from 2014 in my one singular bbb > with newer one > > is it only because fdt? i proposed to just use own fdt like earlier but > people told sorry can't do that. to that i was like how about i supply my > own fdt then? > Yes. It's only because of the FDT, as far as we know. > then, why is fdt such a shitshow anyway? or it works in linux as is, or? > or it changes often? to my still limited knowledge that just defines a hw= , > why would it change, as hw doesn't? > The problem is TI. They maintain the Linux port. Rather than having a stable machine description in the DTS, like the theory states, they are constantly tweaking things so that the old code won't work on the new DTS. Since in Linux, they also update the drivers at the same time and people know the kernel and the DTB is a matched set, it all mostly works out. > so am i correct, we throw that thing out just because it's super hard to > use fdt from linux? > I wouldn't put it that way, but yes. All the other sub-ports on Linux have a basically stable DTB, so we're able to use them w/o problems and only the occasional tweak. Plus, the BBB has been not the primary focus of the developers doing the actual work for a long time, so it's gotten rather far behind. The changes usually aren't that horrible, but sometimes the whole driver model changes and then it's hard. Keeping the old dts around is also hard to maintain since everything else is just imported from Linux. > whole armv7 32bit is bit weird too. looks like it's hanging on the edge o= f > trash can, along with whole 32bit, just to be waiting for to be pushed in= . > yet there are armv7 hw being sold. maybe even made still, can't be all no= s. > like allwinner h3 > There's a lot of FreeBSD use of the 32-bit arm still. But the world is moving to 64-bit systems, and there's already features that we have in 64-bit land we don't have in 32-bit land (EFI runtime, for example). There's also people wanting to do things that will only work on 64-bit kernels, so there's some tension with the 32-bit world in the developer community. Plus the 32-bit use seems to be more using it than developing new things, so very few bug fixes or enhancements to the 32-bit code come in (relative to the 64-bit stuff). > i can understand the issues with 32bit but where's like good working 64bi= t > alternative. out of small hw, only raspberry pi? out of big hw, only arm > servers? > > i have h618 hw here, along with 13.* patches i obtained from forum, > waiting for some tests. maybe someone else has interest in tiny recent ar= m > hw on fbsd > You might make sure Zach has them. > while there, how do all the people dev for armv7? i use system qemu, but > that fails with any new current now. basically old current and old qemu > builds ports. old qemu and new current doesn't boot. new qemu and new > current doesn't boot. new qemu and old current doesn't build half a ports= . > to be honest, old qemu and old qemu needs multiple tries to build some to= o, > funnily. i suspect mixes issues with qemu, fbsd and clang combination her= e. > not to mention that qemu is over 2000 times slower than c2d machine on so= me > tasks. yes, really, 2000 > I've done two or three different things. First, for me armv7 boots with machine type virt in qemu as recently as 9.0 when I fixed problems with virtio-net that caused unaligned access. I do limit what I do in qemu-system-arm since it's good for testing things, but bad at high loads. So no network stress testing, nor package building in it. I also build with bsd-user mode emulation, but that has some problems (I've been slowly working through them, but could use some help). It's quite a bit faster, and works well enough for many things. There's an issue with rust and go, IIRC, that I think is fixed in newer versions. We need to update the port since it's using a 6-year-old fork now (I've updated it to the latest, and several people have contributed improvements, so fingers crossed. I also have a very fast arm64 machine that I run most builds on in a armv7 jail. It works almost as well as native hardware, and is very fast. I have seen a couple of weird edge cases posted where it doesn't work, but I've not hit them personally. I use it also for A/B testing to see if a build hang I see in bsd-user is reproducible on real hardware. > if embedded fbsd goes away, that would be a sad story. i'm actually > curious about using fbsd professionally. i know some others do too, but > can't figure out what hw should i choose where it actually stays supporte= d? > maybe i should wait for more standardized, less fragile arm platforms in > the future? or maybe embedded is fragile by design? i currently look for = hw > similar in performance of h3 but there could be others too, bit more > powerful, maybe with video out, etc > > sad really, and all that existing hw seems to be supported by like single > person in fbsd. if anything happens, that hw is gone too somehow > > god i wish it would be as easy as with big machines. i386 is going but > that might be less of an issue (but i'm sure it's used too). as amd64, ev= en > old, is everywhere > > so any opinions with this arm situation? > > or whole embedded that is. fbsd contains lot of non server things. or > maybe they are server now. like wifi, bt, video. i wish it to stay > > unsure, i can't magically come up with bunch of usera and bunch of devs s= o > things stay healthy and i can also take and give advantage of this > > it's also super hard to maintain own code locally, etc. and embedded hw > tends to really like to stay. for over 10 years easily. i've seen many > embedded platforms appearing in fbsd and then quickly going out. while bi= g > hw stays for, i mean, i've been using fbsd since v4.6, not that long, som= e > hw has been in for entire this time > > unsure what's other option here? use nbsd, use linux? god, some hw has > better support on obsd. sad > > seems like fair bit of armv7 users are still there and i bet they also > look for 64bit extended support hw too. so how to get devs here too? i be= t > there are humans in this planet that are happy to dev for arm on fbsd > enough for it to work well > One reason I've tried to encourage Zach (and others that want to contribute) is that we do have a need to replace the 32-bit arm developers that have retired, passed away, or moved on to other things with newer developers. I'm hoping that even a few will make it better, and that will spur others to contribute since it's less of a lift to get things working, and it's psychologically easier to contribute when you know someone is likely to pick them up. Warner --000000000000e840ff0622611e7d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Wed, Sep 18, 2024 at 7:44=E2=80=AF= AM Sulev-Madis Silber <freebsd-arm-freebsd-org097@ketas.si.pri.ee> wrote:
<= /div>
i'm looking forw= ard to replace current from 2014 in my one singular bbb with newer one

is it only because fdt? i proposed to just use own fdt like earlier but peo= ple told sorry can't do that. to that i was like how about i supply my = own fdt then?

Yes. It's only becaus= e of the FDT, as far as we know.
=C2=A0
then, why is fdt such a shitshow anyway? or it works in linux as is, or? or= it changes often? to my still limited knowledge that just defines a hw, wh= y would it change, as hw doesn't?

T= he problem is TI. They maintain the Linux port. Rather than having a stable= machine description in the DTS, like the theory states, they are constantl= y tweaking things so that the old code won't work on the new DTS. Since= in Linux, they also update the drivers at the same time and people know th= e kernel and the DTB is a matched set, it all mostly works out.
= =C2=A0
so am i correct, we throw that thing out just because it's super hard t= o use fdt from linux?

I wouldn't pu= t it that way, but yes. All the other sub-ports on Linux have a basically s= table DTB, so we're able to use them w/o problems and only the occasion= al tweak. Plus, the BBB has been not the primary focus of the developers do= ing the actual work for a long time, so it's gotten rather far behind. = The changes usually aren't that horrible, but sometimes the whole drive= r model changes and then it's hard. Keeping the old dts around is also = hard to maintain since everything else is just imported from Linux.
=C2=A0
whole armv7 32bit is bit weird too. looks like it's hanging on the edge= of trash can, along with whole 32bit, just to be waiting for to be pushed = in. yet there are armv7 hw being sold. maybe even made still, can't be = all nos. like allwinner h3

There's = a lot of FreeBSD use of the 32-bit arm still. But the world is moving to 64= -bit systems, and there's already features that we have in 64-bit land = we don't have in 32-bit land (EFI runtime, for example). There's al= so people wanting to do things that will only work on 64-bit kernels, so th= ere's some tension with the 32-bit world in the developer community. Pl= us the 32-bit use seems to be more using it than developing new things, so = very few bug fixes or enhancements to the 32-bit code come in (relative to = the 64-bit stuff).
=C2=A0
i can understand the issues with 32bit but where's like good working 64= bit alternative. out of small hw, only raspberry pi? out of big hw, only ar= m servers?

i have h618 hw here, along with 13.* patches i obtained from forum, waiting= for some tests. maybe someone else has interest in tiny recent arm hw on f= bsd

You might make sure Zach has them.<= /div>
=C2=A0
while there, how do all the people dev for armv7? i use system qemu, but th= at fails with any new current now. basically old current and old qemu build= s ports. old qemu and new current doesn't boot. new qemu and new curren= t doesn't boot. new qemu and old current doesn't build half a ports= . to be honest, old qemu and old qemu needs multiple tries to build some to= o, funnily. i suspect mixes issues with qemu, fbsd and clang combination he= re. not to mention that qemu is over 2000 times slower than c2d machine on = some tasks. yes, really, 2000

I've = done two or three different things. First, for me armv7 boots with machine = type virt in qemu as recently as 9.0 when I fixed problems with virtio-net = that caused unaligned access. I do limit what I do in qemu-system-arm since= it's good for testing things, but bad at high loads. So no network str= ess testing, nor package building in it.

I also bu= ild with bsd-user mode emulation, but that has some problems (I've been= slowly working through them, but could use some help). It's quite a bi= t faster, and works well enough for many things. There's an issue with = rust and go, IIRC, that I think is fixed in newer versions. We need to upda= te the port since it's using a 6-year-old fork now (I've updated it= to the latest, and several people have contributed improvements, so finger= s crossed.

I also have a very fast arm64 machine t= hat I run most builds on in a armv7 jail. It works almost as well as native= hardware, and is very fast. I have seen a couple of weird edge cases poste= d where it doesn't work, but I've not hit them personally. I use it= also for A/B testing to see if a build hang I see in bsd-user is reproduci= ble on real hardware.
=C2=A0
if embedded fbsd goes away, that would be a sad story. i'm actually cur= ious about using fbsd professionally. i know some others do too, but can= 9;t figure out what hw should i choose where it actually stays supported? m= aybe i should wait for more standardized, less fragile arm platforms in the= future? or maybe embedded is fragile by design? i currently look for hw si= milar in performance of h3 but there could be others too, bit more powerful= , maybe with video out, etc

sad really, and all that existing hw seems to be supported by like single p= erson in fbsd. if anything happens, that hw is gone too somehow

god i wish it would be as easy as with big machines. i386 is going but that= might be less of an issue (but i'm sure it's used too). as amd64, = even old, is everywhere

so any opinions with this arm situation?

or whole embedded that is. fbsd contains lot of non server things. or maybe= they are server now. like wifi, bt, video. i wish it to stay

unsure, i can't magically come up with bunch of usera and bunch of devs= so things stay healthy and i can also take and give advantage of this

it's also super hard to maintain own code locally, etc. and embedded hw= tends to really like to stay. for over 10 years easily. i've seen many= embedded platforms appearing in fbsd and then quickly going out. while big= hw stays for, i mean, i've been using fbsd since v4.6, not that long, = some hw has been in for entire this time

unsure what's other option here? use nbsd, use linux? god, some hw has = better support on obsd. sad

seems like fair bit of armv7 users are still there and i bet they also look= for 64bit extended support hw too. so how to get devs here too? i bet ther= e are humans in this planet that are happy to dev for arm on fbsd enough fo= r it to work well

One reason I've t= ried to encourage Zach (and others that want to contribute) is that we do h= ave a need to replace the 32-bit arm developers that have retired, passed a= way, or moved on to other things with newer developers. I'm hoping that= even a few will make it better, and that will spur others to contribute si= nce it's less of a lift to get things working, and it's psychologic= ally easier to contribute when you know someone is likely to pick them up.<= /div>

Warner
--000000000000e840ff0622611e7d-- From nobody Wed Sep 18 09:10:06 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 4X7tCb2GWBz5WkRk for ; Wed, 18 Sep 2024 09:10:19 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-pj1-x1030.google.com (mail-pj1-x1030.google.com [IPv6:2607:f8b0:4864:20::1030]) (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 4X7tCZ69BKz4VPc for ; Wed, 18 Sep 2024 09:10:18 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pj1-x1030.google.com with SMTP id 98e67ed59e1d1-2d86f71353dso4688954a91.2 for ; Wed, 18 Sep 2024 02:10:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1726650617; x=1727255417; 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=vYPUOLy0AJXaeBH9mT7/ieTuQ4iwP9PQ0YQPdHHLiis=; b=pTGk7nMbJnqQsOfNsdEm5RckzkuPEvHHeAN3yakQFq/Qyj3TG72K0ZgGzFgTh5Lo3f KKZexaRL5xO0aKMPaJzR/3RJxEuByKpWVV/s9mvVFcdQdsEdcvRvtGdA1mjHb3vpf9wq 9S9RSVmzs+5AhliXemzQTsCArW/+XuT37ZD4EmjJ5ynm+kclOUn9AX9t3PoRYsEVOy5l c/PW9zbzxcZ17rUuQVSRMbF/PUzmxQ7Nn0V0+wR462U3eUzZoTPpBnkUdpVonWsvnVz0 LXWLpmlp2CCbXAxzsd9Sip9jMtwgEbH7e+k3q+LUs0jnYyxq471i/4IEoRZHI+dORFyY jOjA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1726650617; x=1727255417; 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=vYPUOLy0AJXaeBH9mT7/ieTuQ4iwP9PQ0YQPdHHLiis=; b=qTmZbbms/aXt6lueeoyxbXEays2iofe1x58mtLiwvGF8Gl7Ye36Q2rilZRQImLNLd9 JmHvDGfSuhzMlurQb8yajEtIgw6hRfX7I0D+3Y6zVchc2RPBsxK+wYPHIXXt2DHdM8Sr /NWgVC1iHDMmn/DQsoFFmtuEVuPx2olsM8bq9+E/nCLqA75kKW6RB7DwkACA73D29vdI p85D48H8TsVlSaQySM7an64GQNDnP01rtoJQjGVrBzfb1XjAHk+pvT382JxG5kWUHnUc /7rdhyK9YmH3wHs1d1gJvAcyRmfchR5kD6Kf2tOsZRx7ppuGven1q139lDQ1xee90kCY w5KQ== X-Forwarded-Encrypted: i=1; AJvYcCVbalVtlgyQNgx76Ssoqq7tPAiXfvHibV5lcgFxWWdojGhxeDPA/ipxI4bal7qJVBFcGRAnqO44duLepA==@freebsd.org X-Gm-Message-State: AOJu0YxsiuPU5gFfAu9MFBXdAv2HsZKYYeC8kP9VKGmwGnV7cc0i59Cf bHlbeqE8jlHNZwlNDSzhgBbFyhdTpS3kQdrD6vx/EmSTX+kf3ONE5uIlJ1Ugy3JTBdSKc2QuDFF H+Ouh3JksmIMwlWN83bUiADm0AeJ6PWMTFVbDow== X-Google-Smtp-Source: AGHT+IF38T0WaDb2QPGz40jHUZ8X0A1ZW3EwVIgy13cjaS/Jw5zEAZ0vFzOvm2QH+h4Yc1NcRPyTEsBeGDeNfuVSyX0= X-Received: by 2002:a17:90b:815:b0:2d8:7572:4bc1 with SMTP id 98e67ed59e1d1-2db9ff79cfbmr24032029a91.1.1726650617350; Wed, 18 Sep 2024 02:10:17 -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: <276f57f2-5194-cad1-d859-e49b2bce2580@pobox.com> <69E08B38-7388-46A6-8864-20074BFFF8F4@yahoo.com> <88d2cc76-f980-600e-0da4-2fa1070d76ba@pobox.com> <6b848423-bdd1-b215-889a-1f07e5064412@pobox.com> <4BEC1DC0-7528-4B4B-8FD0-254BD7BF1BD9@ketas.si.pri.ee> <8597295C-BC33-4F76-AF45-41753D3E47BA@yahoo.com> In-Reply-To: <8597295C-BC33-4F76-AF45-41753D3E47BA@yahoo.com> From: Warner Losh Date: Wed, 18 Sep 2024 10:10:06 +0100 Message-ID: Subject: Re: Beaglebone Black/Green/Blue support (volunteering) To: Mark Millard Cc: Sulev-Madis Silber , freebsd-arm@freebsd.org Content-Type: multipart/alternative; boundary="000000000000b2f6ba0622612c1c" X-Spamd-Bar: ---- 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:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4X7tCZ69BKz4VPc --000000000000b2f6ba0622612c1c Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, Sep 18, 2024 at 9:31=E2=80=AFAM Mark Millard wr= ote: > On Sep 17, 2024, at 23:44, Sulev-Madis Silber < > freebsd-arm-freebsd-org097@ketas.si.pri.ee> wrote: > > > i'm looking forward to replace current from 2014 in my one singular bbb > with newer one > > > > is it only because fdt? i proposed to just use own fdt like earlier but > people told sorry can't do that. to that i was like how about i supply my > own fdt then? > > > > then, why is fdt such a shitshow anyway? or it works in linux as is, or= ? > or it changes often? to my still limited knowledge that just defines a hw= , > why would it change, as hw doesn't? > > My understanding of the operating principles here: > > The FDT provides a mapping between the Linux kernel's way > of working and the hardware. When Linux changes how the > kernel works the Linux FDT tracks the redesign. The two > are not independent. In essence, the FDT is a form of > kernel data structure. Multiple distinct FDT's can > describe the exact same hardware: the hardware of itself > does not uniquely determine the FDT for that hardware. > > Some contexts have fairly stable Linux kernel designs and, > so, fairly stable FDTs; others do not. > The theory is that DTS is a stable, OS independent description of the hardware. Some hardware vendors and their maintainers really believe this. The practice, though, is that some just have it be whatever is convenient for their drivers, which they change around a lot to get better performance, or when new hardware comes out. > So, one can get evidence about some of what is being > significantly reworked over time in the Linux kernel via > the seeing the repeated FDT restructuring over the time > frame. This contrasts with other context's FDTs being > stable because there is a lack of such Linux kernel > driven changes to that FDT. > > So, when FreeBSD sees the linux FDT has changed and has to > adjust for such, it is actually tracking some consequences > of the Linux kernel rework activity that changed both the > Linux kernel and the FDT. > > At least, that is my understanding. > Close. In reality, the TI DTS are the most unstable. The rest are fairly stable and generally easy enough for us to use. > FreeBSD does not have the resources to develop and use its > own FDT's overall and simply chooses to track an upstream > source of a context's FDT(s) instead. In the case of RPi*'s, > it is not mainline Linux FDT's that are tracked --but the > FDT's are from a Linux kernel context. (I'm not sure if > RPi*'s have the only non-main-line FDT's used.) > RPi do have a bit of churn, but the problems with getting base documentation more than FDT. > > so am i correct, we throw that thing out just because it's super hard t= o > use fdt from linux? > . . . > > How difficult or messy or frequently FDT tracking is > involved varies widely across the various contexts. > It is not a uniform global property for all Linux FDTs. > > . . . > > while there, how do all the people dev for armv7? > > Many aarch64 systems can execute armv7 code and so > serve as a means of building armv7 code with armv7 > tools (armv7 jail's, armv7 chroot's, possibly even > lib32). Such is generally more reliable and less time > consuming than use of qemu for "cross-activity" many > context that try to use qemu. > > The official FreeBSD armv7 packages are built on > aarch64 systems that can execute armv7 code. This > uses armv7 poudriere jails. It works a lot better > than the historical qemu use on amd64 before these > ampere[123] aarch64 machines were available (or > were not yet used this way). > > Some folks use the likes of Windows Dev Kit 2023's > or RPi4B's or RPi5B's for such activities of their > own. (Apple M1/M2/M3/M4 do not support armv7 code > and so are not example contexts for doing these > sorts of things without qemu involved.) > Yea, the Apple M3 I have is where I run much of the armv7 code in a FreeBSD VM... Warner --000000000000b2f6ba0622612c1c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Wed, Sep 18, 2024 at 9:31=E2=80=AF= AM Mark Millard <marklmi@yahoo.com<= /a>> wrote:
O= n Sep 17, 2024, at 23:44, Sulev-Madis Silber <freebsd-arm-freebsd-o= rg097@ketas.si.pri.ee> wrote:

> i'm looking forward to replace current from 2014 in my one singula= r bbb with newer one
>
> is it only because fdt? i proposed to just use own fdt like earlier bu= t people told sorry can't do that. to that i was like how about i suppl= y my own fdt then?
>
> then, why is fdt such a shitshow anyway? or it works in linux as is, o= r? or it changes often? to my still limited knowledge that just defines a h= w, why would it change, as hw doesn't?

My understanding of the operating principles here:

The FDT provides a mapping between the Linux kernel's way
of working and the hardware. When Linux changes how the
kernel works the Linux FDT tracks the redesign. The two
are not independent. In essence, the FDT is a form of
kernel data structure. Multiple distinct FDT's can
describe the exact same hardware: the hardware of itself
does not uniquely determine the FDT for that hardware.

Some contexts have fairly stable Linux kernel designs and,
so, fairly stable FDTs; others do not.

= The theory is that DTS is a stable, OS independent description of the hardw= are. Some hardware vendors and their maintainers really believe this.
=
The practice, though, is that some just have it be whatever is conveni= ent for their drivers, which they change around a lot to get better perform= ance, or when new hardware comes out.
=C2=A0
So, one can get evidence about some of what is being
significantly reworked over time in the Linux kernel via
the seeing the repeated FDT restructuring over the time
frame. This contrasts with other context's FDTs being
stable because there is a lack of such Linux kernel
driven changes to that FDT.

So, when FreeBSD sees the linux FDT has changed and has to
adjust for such, it is actually tracking some consequences
of the Linux kernel rework activity that changed both the
Linux kernel and the FDT.

At least, that is my understanding.

Clo= se. In reality, the TI DTS are the most unstable. The rest are fairly stabl= e and generally easy enough for us to use.
=C2=A0
FreeBSD does not have the resources to develop and use its
own FDT's overall and simply chooses to track an upstream
source of a context's FDT(s) instead. In the case of RPi*'s,
it is not mainline Linux FDT's that are tracked --but the
FDT's are from a Linux kernel context. (I'm not sure if
RPi*'s have the only non-main-line FDT's used.)

RPi do have a bit of churn, but the problems with getting = base documentation more than FDT.
=C2=A0
> so am i correct, we throw that thing out just because it's super h= ard to use fdt from linux?
. . .

How difficult or messy or frequently FDT tracking is
involved varies widely across the various contexts.
It is not a uniform global property for all Linux FDTs.

. . .
> while there, how do all the people dev for armv7?

Many aarch64 systems can execute armv7 code and so
serve as a means of building armv7 code with armv7
tools (armv7 jail's, armv7 chroot's, possibly even
lib32). Such is generally more reliable and less time
consuming than use of qemu for "cross-activity" many
context that try to use qemu.

The official FreeBSD armv7 packages are built on
aarch64 systems that can execute armv7 code. This
uses armv7 poudriere jails. It works a lot better
than the historical qemu use on amd64 before these
ampere[123] aarch64 machines were available (or
were not yet used this way).

Some folks use the likes of Windows Dev Kit 2023's
or RPi4B's or RPi5B's for such activities of their
own. (Apple M1/M2/M3/M4 do not support armv7 code
and so are not example contexts for doing these
sorts of things without qemu involved.)

Yea, the Apple M3 I have is where I run much of the armv7 code in a FreeBS= D VM...

Warner=C2=A0
--000000000000b2f6ba0622612c1c-- From nobody Wed Sep 18 10:07:53 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 4X7vVX1m1tz5VdtD for ; Wed, 18 Sep 2024 10:08:20 +0000 (UTC) (envelope-from freebsd-arm-freebsd-org097@ketas.si.pri.ee) Received: from green.sau.si.pri.ee (d004-fea2-0bff-021e-13e8-8437-07d0-2001.dyn.estpak.ee [IPv6:2001:7d0:8437:13e8:21e:bff:fea2:d004]) (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 4X7vVW19hdz4fT7 for ; Wed, 18 Sep 2024 10:08:18 +0000 (UTC) (envelope-from freebsd-arm-freebsd-org097@ketas.si.pri.ee) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=ketas.si.pri.ee header.s=ketas-si-pri-ee-20240416002854-4096 header.b=bL7b+ODg; dmarc=pass (policy=reject) header.from=ketas.si.pri.ee; spf=pass (mx1.freebsd.org: domain of freebsd-arm-freebsd-org097@ketas.si.pri.ee designates 2001:7d0:8437:13e8:21e:bff:fea2:d004 as permitted sender) smtp.mailfrom=freebsd-arm-freebsd-org097@ketas.si.pri.ee X-Original-To: freebsd-arm@freebsd.org DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=ketas.si.pri.ee; s=ketas-si-pri-ee-20240416002854-4096; t=1726654086; bh=MGSVSCB5S/xU4/Hh15HiPFWSo72vbwNA4JacIymsJ/A=; h=Date:From:To:Subject:In-Reply-To:References; b=bL7b+ODg6KR0TUXJpeGsYkyUm97YD7KCkD9yc1ZrPs1C4DHYq2s10DkN+WCgjGE/0 fnPHw109VEmziVMlqpvHkBjPN2/hA54vbYOXHang8vaqQHVuNLTfsweYxkMQLW6e47 0YrRflXHpD+EJf/fyW/S7AQJE2Xk8V3emTXqLE2+cBmL99KZ25Wd5INI4J5vemeMTO 02EnNUDN6WZ+00s8kROvAveUEJkSntZwtNnbcQlyhbveFcgmy9UCHB9sBL1A3hlJip RsvLxRXEDcrciZxyYUDH9jIJ7aG0hFU2W65qxXnm5RUeEiPE8qqjCYY8NtKcKlsE8z E5mxVG+ETRP2sJeK5ZX+JvyByw9iPwgVfzui/fo6YB2vNkJu9ocIEPdwTTZWaAxu5G YWnSvEIKs70T8dsSsPjzYo6TXghtCGiYvMlZzzMMijerT7UYxuK96p3U56Y99jwVsS A3wNBDdWzR3B+6C7HtL4nkNR9n6z+CWtbAc9cS0lhy70oFGavSWg5YkowNkdWmVWN8 y/5j1EBjR8Rr+3D8XIMJmp1tqQCNaH7PXnnDpDXTTYhQ3vbfmUnPuE9pvBD9lxxJhi wfZenX5xXZjP7PUSWyLK94RlgSpMqh6G59wnMn2Kg4LdDmt00zpi1OeZy72bVwCHzJ D6dGsrWeubZhsuNqvvsU+YCk= Received: from [IPv6:::1] (0114-0000-0000-0000-13c8-8437-07d0-2001.dyn.estpak.ee [IPv6:2001:7d0:8437:13c8::114]) (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) (No client certificate requested) by forestgreen.jails.green.sau.si.pri.ee (Postfix) with ESMTPSA id EE274594E85 for ; Wed, 18 Sep 2024 13:08:04 +0300 (EEST) Date: Wed, 18 Sep 2024 13:07:53 +0300 From: Sulev-Madis Silber To: freebsd-arm@freebsd.org Subject: Re: Beaglebone Black/Green/Blue support (volunteering) User-Agent: K-9 Mail for Android In-Reply-To: References: <276f57f2-5194-cad1-d859-e49b2bce2580@pobox.com> <69E08B38-7388-46A6-8864-20074BFFF8F4@yahoo.com> <88d2cc76-f980-600e-0da4-2fa1070d76ba@pobox.com> <6b848423-bdd1-b215-889a-1f07e5064412@pobox.com> <4BEC1DC0-7528-4B4B-8FD0-254BD7BF1BD9@ketas.si.pri.ee> <8597295C-BC33-4F76-AF45-41753D3E47BA@yahoo.com> Message-ID: 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=utf-8 Content-Transfer-Encoding: quoted-printable X-Spamd-Bar: / X-Spamd-Result: default: False [-0.90 / 15.00]; HFILTER_HOSTNAME_5(3.00)[d004-fea2-0bff-021e-13e8-8437-07d0-2001.dyn.estpak.ee]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[ketas.si.pri.ee,reject]; R_SPF_ALLOW(-0.20)[+ip6:2001:7d0:8437:1300::/56]; R_DKIM_ALLOW(-0.20)[ketas.si.pri.ee:s=ketas-si-pri-ee-20240416002854-4096]; ONCE_RECEIVED(0.10)[]; MIME_GOOD(-0.10)[text/plain]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:3249, ipnet:2001:7d0::/32, country:EE]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_ONE(0.00)[1]; RCVD_TLS_ALL(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DKIM_TRACE(0.00)[ketas.si.pri.ee:+] X-Rspamd-Queue-Id: 4X7vVW19hdz4fT7 hmm=2E=2E=2E ok i see=2E i don't still see myself writing much kernel code = still (and even less, doing it alone) but i could test stuff=2E i have done= it before for bbb https://forums=2Efreebsd=2Eorg/threads/orange-pi-zero2-and-freebsd-13-2=2E= 89267/page-3#post-621499 here's the half a meg diff=2E=2E=2E i suggested getting it into current as fast as possible=2E but who actuall= y knows how to do this? also i realize it's hard to track current hotness and cheap crap=2E unsure= what way to go here=2E i hope there's more nice open options here i had plan to try to port it over but hell=2E i mean=2E i hope there are m= ore people like me going just only rpi way seems bad too besides it seems that the allwinner presence is quite good already too i even thought of giving some (home)lab access away for free if problem is= in getting hw physically present at ones workbench or otherwise procrastin= ation reasons From nobody Wed Sep 18 13:32:36 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 4X802J1R5Dz5WNp6 for ; Wed, 18 Sep 2024 13:32:40 +0000 (UTC) (envelope-from void@f-m.fm) Received: from fout4-smtp.messagingengine.com (fout4-smtp.messagingengine.com [103.168.172.147]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4X802H4SPvz43bs for ; Wed, 18 Sep 2024 13:32:39 +0000 (UTC) (envelope-from void@f-m.fm) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=f-m.fm header.s=fm1 header.b="Fapq8Ds/"; dkim=pass header.d=messagingengine.com header.s=fm1 header.b=Ix+I6ycT; dmarc=pass (policy=none) header.from=f-m.fm; spf=pass (mx1.freebsd.org: domain of void@f-m.fm designates 103.168.172.147 as permitted sender) smtp.mailfrom=void@f-m.fm Received: from phl-compute-11.internal (phl-compute-11.phl.internal [10.202.2.51]) by mailfout.phl.internal (Postfix) with ESMTP id 6F6B713802AA for ; Wed, 18 Sep 2024 09:32:38 -0400 (EDT) Received: from phl-mailfrontend-01 ([10.202.2.162]) by phl-compute-11.internal (MEProxy); Wed, 18 Sep 2024 09:32:38 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=f-m.fm; h=cc :content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:subject :subject:to:to; s=fm1; t=1726666358; x=1726752758; bh=p7tugiIK0Z 0D8pFMsJDHc3/Q7eN8Ff95M8YIT/IypJQ=; b=Fapq8Ds/6S8FqKSNSrbSnpNIlv JQZJHsI/75DoPB2ywhOlnT6os2EMf9kmIvqlrfDc+RbV23vJd34BVr4DgsA6lDGC /AHMjbz2uehg6aHVj64X20z+/yt/ab9IxGA4B8gvQmP22wdBHDTLEsX7E1xzcKJU 4keAS/APaDP+3+oVHwsnqEQK/2zWpzS5KH/1eK+hznxiM6OY1WesenP99XKzBI7T IN6pIeeLIBP2rNJ/8AtcxQfGhGDvAguh5uOL3b9SLIjTQ7jyrMMlzYuwn/K6+LuJ GbpDCy1GPPmrLioECmQpAH4fxlx6yhjkAXxL8Eyz5ZgHRuh/yDyf7A6bqmEA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:subject:subject:to :to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; t=1726666358; x=1726752758; bh=p7tugiIK0Z0D8pFMsJDHc3/Q7eN8 Ff95M8YIT/IypJQ=; b=Ix+I6ycT82BPDVnpXAHkzLH4xpAiJ41qx0QlOKtXA12r 6YcAhLkAiyaHpDhQU2IStCIWCVs/d2FvNBTvGrsvtYYDGqtylRTvfVJLwUYjtL1K JKhd49dZ/Xi38oQ5Dn+VuGhKgqrmMVIdFl0f/3SsyvrzCc0GBx0cuhVuAPFdzeyN a+yqT6jQlIohWEizojlt8TM995NVR5VH/605MeIDn2ZaZYd6z/FtBtDigJmmwRsB QcwrqLcCZFjN/Hd8m6yCDX2QqKM+Z4/AdHW27B6P8tU3rbpfL7CdZd2dydugbVzq cBc3leOesD5uWu6dTEgE9v2GMtkpZeWHEFoCLLke6Q== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeftddrudekledgieehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdggtfgfnhhsuhgsshgtrhhisggvpdfu rfetoffkrfgpnffqhgenuceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuf fkfhggtggujgesthdtredttddtvdenucfhrhhomhepvhhoihguuceovhhoihgusehfqdhm rdhfmheqnecuggftrfgrthhtvghrnhepkeeluddvlefhieelfefggffhffektdehleelgf dugfdvgeekjeejuddtheehgfeunecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghm pehmrghilhhfrhhomhepvhhoihgusehfqdhmrdhfmhdpnhgspghrtghpthhtohepuddpmh houggvpehsmhhtphhouhhtpdhrtghpthhtohepfhhrvggvsghsugdqrghrmhesfhhrvggv sghsugdrohhrgh X-ME-Proxy: Feedback-ID: i2541463c:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Wed, 18 Sep 2024 09:32:37 -0400 (EDT) Date: Wed, 18 Sep 2024 14:32:36 +0100 From: void To: freebsd-arm@freebsd.org Subject: Re: Beaglebone Black/Green/Blue support (volunteering) Message-ID: Mail-Followup-To: freebsd-arm@freebsd.org References: <276f57f2-5194-cad1-d859-e49b2bce2580@pobox.com> <69E08B38-7388-46A6-8864-20074BFFF8F4@yahoo.com> <88d2cc76-f980-600e-0da4-2fa1070d76ba@pobox.com> <6b848423-bdd1-b215-889a-1f07e5064412@pobox.com> <4BEC1DC0-7528-4B4B-8FD0-254BD7BF1BD9@ketas.si.pri.ee> 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=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <4BEC1DC0-7528-4B4B-8FD0-254BD7BF1BD9@ketas.si.pri.ee> X-Spamd-Result: default: False [-1.48 / 15.00]; NEURAL_HAM_SHORT(-0.88)[-0.884]; MID_RHS_NOT_FQDN(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[f-m.fm,none]; R_DKIM_ALLOW(-0.20)[f-m.fm:s=fm1,messagingengine.com:s=fm1]; R_SPF_ALLOW(-0.20)[+ip4:103.168.172.128/27:c]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[103.168.172.147:from]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; FREEMAIL_FROM(0.00)[f-m.fm]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[f-m.fm]; DWL_DNSWL_NONE(0.00)[messagingengine.com:dkim]; MISSING_XM_UA(0.00)[]; ASN(0.00)[asn:209242, ipnet:103.168.172.0/24, country:US]; RCPT_COUNT_ONE(0.00)[1]; RCVD_COUNT_THREE(0.00)[3]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_LAST(0.00)[]; DKIM_TRACE(0.00)[f-m.fm:+,messagingengine.com:+] X-Rspamd-Queue-Id: 4X802H4SPvz43bs X-Spamd-Bar: - On Wed, Sep 18, 2024 at 09:44:06AM +0300, Sulev-Madis Silber wrote: >so any opinions with this arm situation? The way I'm addressing it is to install netbsd on arm6 and arm7 devices. Part of their focus is to have netbsd work on any device within reason. My observation is that this is not freebsd's primary focus. I still have arm6 and arm7 machines in perfect working order which I don't want or need to dispose of, and where the OS should be kept current. So, in my case, it'll be netbsd for them. -- From nobody Wed Sep 18 16:50:25 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 4X84QV0X7Jz5WnPg for ; Wed, 18 Sep 2024 16:50:26 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (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-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4X84QT5b0fz4TqF for ; Wed, 18 Sep 2024 16:50:25 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1726678225; a=rsa-sha256; cv=none; b=voalJu67j4Dz/C6+wVVHtFf+47POD6xlVGldlWNNymYA5J2q9ey1p1Sjsydzq+WhI85w+v QvCdlhj/vQ9COKuvJyG4HuPrbuuFErgKv4KdveEZ6uUFh8oidYjkr2EqSnltWWJEpj/ST4 1GOc3Oj4lOH0zPUV3Mu/LVzaWuict5+QGlVFzU1yUH3iGwe0zrwDMvJjud292j02/PH2cg zpqoyJAF1w63eeJShlIjTdvIOvW4pWp6yZwrI5RRzChHgnWdNd0MWjdCHYDysVKJW/NjtN VSVtFs/NdSzVi8vcYEF4w7C4VFLzhVm4c+9VEbpWyZUWbScWU2gEFEpa895ZrA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1726678225; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=irc/0NHr0YuCRsDZYZnJC8jsnFxy7Aivv6gVuG7WZmc=; b=JrJ2cps6N43xpV3EKxMKME3mquhKJEXPx41mRo/Fi76S5KEgepQkWqL7I/Q1nQDedCrleZ 7+w56KAw/BAjpv2H9adwydM41kLlDtQYLdZ2ZObiQ3AsVeve5cSgW9GadzbxYAClGVgfBE suRyFHWMChq57F6k6miyRpuBZipQfyad2VIph2g0BmytbItbAIo1QUyNHocv5ijPUTsPZM VK7bfCdHTtuiX+OkoWoWe4rTmRvwcqC6Fzs9IuupVgUQlW1Hd2Y1wwyoQ1kgeidFOfKWtv 4V9h7PIoJ2lVbyFmL+pkTJZn9gf/zTJOfIovKayTUn2dMHPfiWHs2EH7IOCG6g== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (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 mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4X84QT5BQ2zV9x for ; Wed, 18 Sep 2024 16:50:25 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 48IGoPvH077057 for ; Wed, 18 Sep 2024 16:50:25 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 48IGoPaM077056 for freebsd-arm@FreeBSD.org; Wed, 18 Sep 2024 16:50:25 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-arm@FreeBSD.org Subject: [Bug 281574] bc(1) runs in endless loop Date: Wed, 18 Sep 2024 16:50:25 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: arm X-Bugzilla-Version: 14.1-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: wosch@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-arm@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated 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 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D281574 Bug ID: 281574 Summary: bc(1) runs in endless loop Product: Base System Version: 14.1-STABLE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: arm Assignee: freebsd-arm@FreeBSD.org Reporter: wosch@FreeBSD.org I killed a terminal with a running bc command. The terminal is gone, but bc= (1) runs in an endless loop now: top(1) output: 40325 wosch 1 135 0 13M 3332K CPU0 0 1:14 99.86% bc ktrace -p 40325 kdump 40325 bc CALL read(0,0x217008d92da8,0x1) 40325 bc GIO fd 0 read 0 bytes "" 40325 bc RET read 0 40325 bc CALL ioctl(0,TIOCSETAW,0x3821a3c5b238) 40325 bc RET ioctl -1 errno 25 Inappropriate ioctl for device 40325 bc CALL sigprocmask(SIG_BLOCK,0x217008d92e58,0x217008d92e68) 40325 bc RET sigprocmask 0 40325 bc CALL ioctl(0,TIOCGWINSZ,0x217008d92e10) 40325 bc RET ioctl -1 errno 25 Inappropriate ioctl for device 40325 bc CALL sigprocmask(SIG_SETMASK,0x217008d92e68,0) 40325 bc RET sigprocmask 0 40325 bc CALL read(0,0x217008d92da8,0x1) 40325 bc GIO fd 0 read 0 bytes "" 40325 bc RET read 0 40325 bc CALL ioctl(0,TIOCSETAW,0x3821a3c5b238) 40325 bc RET ioctl -1 errno 25 Inappropriate ioctl for device 40325 bc CALL sigprocmask(SIG_BLOCK,0x217008d92e58,0x217008d92e68) 40325 bc RET sigprocmask 0 40325 bc CALL ioctl(0,TIOCGWINSZ,0x217008d92e10) 40325 bc RET ioctl -1 errno 25 Inappropriate ioctl for device 40325 bc CALL sigprocmask(SIG_SETMASK,0x217008d92e68,0) 40325 bc RET sigprocmask 0 40325 bc CALL read(0,0x217008d92da8,0x1) 40325 bc GIO fd 0 read 0 bytes I tried to kill the process, but it worked only with SIGKILL and not SIGTERM/SIGHUP kill -9 40325 --=20 You are receiving this mail because: You are the assignee for the bug.= From nobody Thu Sep 19 14:36:32 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 4X8dPk5jTrz5Wl6M for ; Thu, 19 Sep 2024 14:36:42 +0000 (UTC) (envelope-from zmetzing@pobox.com) Received: from pb-smtp2.pobox.com (pb-smtp2.pobox.com [64.147.108.71]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4X8dPj6Jznz4HkC for ; Thu, 19 Sep 2024 14:36:41 +0000 (UTC) (envelope-from zmetzing@pobox.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=pobox.com header.s=sasl header.b="ZiFjs6/q"; dmarc=pass (policy=none) header.from=pobox.com; spf=pass (mx1.freebsd.org: domain of zmetzing@pobox.com designates 64.147.108.71 as permitted sender) smtp.mailfrom=zmetzing@pobox.com Received: from pb-smtp2.pobox.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id 3752B2661F for ; Thu, 19 Sep 2024 10:36:41 -0400 (EDT) (envelope-from zmetzing@pobox.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=pobox.com; h=message-id :date:mime-version:subject:to:references:from:in-reply-to :content-type:content-transfer-encoding; s=sasl; bh=o/3FMjzfte3R 1LDWyx0t2qOnljrkeM0hMhBa/o9RDFY=; b=ZiFjs6/qA6gE6Uh0vx4ZqbREpFeR CUiyTt0vAs79nZiuVilpZl/S3g9OiTuLxdMObF2OVPwtOfAzC1BJJbGgHSQe/fhu alXXN75qgxpe3paxXU9hZJcGWLoPdBgc/JwDwxj3NxzlAw96cDh4coML99do23KI M4IcbFnztr9FY0c= Received: from pb-smtp2.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id 2EA0D2661E for ; Thu, 19 Sep 2024 10:36:41 -0400 (EDT) (envelope-from zmetzing@pobox.com) Received: from [192.168.1.11] (unknown [47.185.113.8]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pb-smtp2.pobox.com (Postfix) with ESMTPSA id 8EFF12661D for ; Thu, 19 Sep 2024 10:36:40 -0400 (EDT) (envelope-from zmetzing@pobox.com) Message-ID: Date: Thu, 19 Sep 2024 09:36:32 -0500 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 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:102.0) Gecko/20100101 Thunderbird/102.9.0 Subject: Re: Beaglebone Black/Green/Blue support (volunteering) Content-Language: en-US To: freebsd-arm@freebsd.org References: <276f57f2-5194-cad1-d859-e49b2bce2580@pobox.com> <69E08B38-7388-46A6-8864-20074BFFF8F4@yahoo.com> <88d2cc76-f980-600e-0da4-2fa1070d76ba@pobox.com> <6b848423-bdd1-b215-889a-1f07e5064412@pobox.com> <4BEC1DC0-7528-4B4B-8FD0-254BD7BF1BD9@ketas.si.pri.ee> From: Zach Metzinger In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Pobox-Relay-ID: 9574EDD4-7694-11EF-9E8F-9B0F950A682E-19366360!pb-smtp2.pobox.com X-Spamd-Result: default: False [-4.10 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.998]; DMARC_POLICY_ALLOW(-0.50)[pobox.com,none]; R_DKIM_ALLOW(-0.20)[pobox.com:s=sasl]; R_SPF_ALLOW(-0.20)[+ip4:64.147.108.0/24]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[64.147.108.71:from]; RCVD_VIA_SMTP_AUTH(0.00)[]; MIME_TRACE(0.00)[0:+]; ARC_NA(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:19151, ipnet:64.147.108.0/24, country:US]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; DWL_DNSWL_NONE(0.00)[pobox.com:dkim]; TO_DN_NONE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_LAST(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[pobox.com:+] X-Rspamd-Queue-Id: 4X8dPj6Jznz4HkC X-Spamd-Bar: ---- On 9/18/24 08:32, void wrote: > On Wed, Sep 18, 2024 at 09:44:06AM +0300, Sulev-Madis Silber wrote: > >> so any opinions with this arm situation? > > The way I'm addressing it is to install netbsd on arm6 and arm7 devices. Hello Suley-Madis, The way I'm addressing it is to help convert the new device tree file to something FreeBSD can use. Spare cycles are rare, but it is progressing. Ranting about lack of support is not likely to improve the situation. Putting your valuable personal time on the line just might. --- Zach From nobody Thu Sep 19 15:07: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 4X8f6b5z3Gz5X4dP for ; Thu, 19 Sep 2024 15:08:39 +0000 (UTC) (envelope-from void@f-m.fm) Received: from fhigh1-smtp.messagingengine.com (fhigh1-smtp.messagingengine.com [103.168.172.152]) (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 4X8f6b0yNtz4L6h for ; Thu, 19 Sep 2024 15:08:39 +0000 (UTC) (envelope-from void@f-m.fm) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=f-m.fm header.s=fm2 header.b=JalEUAum; dkim=pass header.d=messagingengine.com header.s=fm2 header.b="e WFCpOc"; dmarc=pass (policy=none) header.from=f-m.fm; spf=pass (mx1.freebsd.org: domain of void@f-m.fm designates 103.168.172.152 as permitted sender) smtp.mailfrom=void@f-m.fm Received: from phl-compute-04.internal (phl-compute-04.phl.internal [10.202.2.44]) by mailfhigh.phl.internal (Postfix) with ESMTP id 6410D1140123 for ; Thu, 19 Sep 2024 11:08:38 -0400 (EDT) Received: from phl-imap-04 ([10.202.2.82]) by phl-compute-04.internal (MEProxy); Thu, 19 Sep 2024 11:08:38 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=f-m.fm; h=cc :content-transfer-encoding:content-type:content-type:date:date :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm2; t=1726758518; x=1726844918; bh=Mlk+CIcydcgb59Kwr6bChnm2AFcvi2RGYCQHy5XqYrw=; b= JalEUAumTG87lm1sBQP/GLMPYZuSxNXmzZichj6S8iBdVjMc2IzZXurXFCMXxGI8 O3g/yDwjFak4LW46nM7U4dPztIF3Plv3ZaUTVRkyXii2PDN8WelREVI44itfOlHi KzIw/sFEjU6B4Qn/RmwpG/8mqSru4TlQqGaWUXDTP0tQjmtOA/y5LDS4HXYhNaRd P9n0R9UghUCPEvxyMGoN1BcUiooBJufzix95a35Gqb2mp95PJx+0+WHki1XvHcbr 4irH0Mym7IsouhxrIV+G6yKUv4esJ3RB9Tqgckx82R0HXllPYByUK/MAm/f1Uc1Y MApBphJx7+3R2GdDfN+VPw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t=1726758518; x= 1726844918; bh=Mlk+CIcydcgb59Kwr6bChnm2AFcvi2RGYCQHy5XqYrw=; b=e WFCpOctyrYvNwstHww2k6r0bRm+tF0HBlsDpqZHYJdRcn/c4hbXI6NeR28DzPi+Y +EHTOxJeSr2MKZB5RBQJRqjfMcUa/4daeMm33TgMxo/paO3M4F2GaqTgLTqG0hny MWHE3tq/o18h6wBRzKe+4zjILHRmG1yU3ssFTmInQbnIIHcVVrnvFzPUky0HGyVb 7O89+S3cfQo09Tjxvj2r0QBTUdVTjt1zbgSLx8gRxfGLqGZN5Sk/1A9Mc5mfsZM+ vK03qRnLCDgtQbai8fvRAoKDY6U90GowL6L45Q1m5JMXBxtLlfrrr8MvE9K1V8s8 R5CASjJDjR9UTMKFlWQ5A== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeftddrudeluddgkeehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdggtfgfnhhsuhgsshgtrhhisggvpdfu rfetoffkrfgpnffqhgenuceurghilhhouhhtmecufedttdenucenucfjughrpefoggffhf fvkfgjfhfutgfgsehtjeertdertddtnecuhfhrohhmpehvohhiugcuoehvohhiugesfhdq mhdrfhhmqeenucggtffrrghtthgvrhhnpeeitdefieefteeiffeffefgjeeuveffledthe ffgedtfffhfeeugffguefhkefgvdenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgr mhepmhgrihhlfhhrohhmpehvohhiugesfhdqmhdrfhhmpdhnsggprhgtphhtthhopedupd hmohguvgepshhmthhpohhuthdprhgtphhtthhopehfrhgvvggsshguqdgrrhhmsehfrhgv vggsshgurdhorhhg X-ME-Proxy: Feedback-ID: i2541463c:Fastmail Received: by mailuser.phl.internal (Postfix, from userid 501) id 0F6F12E60075; Thu, 19 Sep 2024 11:08:38 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface 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 Date: Thu, 19 Sep 2024 16:07:58 +0100 From: void To: freebsd-arm Message-Id: In-Reply-To: References: <276f57f2-5194-cad1-d859-e49b2bce2580@pobox.com> <69E08B38-7388-46A6-8864-20074BFFF8F4@yahoo.com> <88d2cc76-f980-600e-0da4-2fa1070d76ba@pobox.com> <6b848423-bdd1-b215-889a-1f07e5064412@pobox.com> <4BEC1DC0-7528-4B4B-8FD0-254BD7BF1BD9@ketas.si.pri.ee> Subject: Re: Beaglebone Black/Green/Blue support (volunteering) Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [-3.92 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-0.99)[-0.995]; NEURAL_HAM_SHORT(-0.84)[-0.835]; DMARC_POLICY_ALLOW(-0.50)[f-m.fm,none]; R_SPF_ALLOW(-0.20)[+ip4:103.168.172.128/27]; R_DKIM_ALLOW(-0.20)[f-m.fm:s=fm2,messagingengine.com:s=fm2]; RCVD_IN_DNSWL_LOW(-0.10)[103.168.172.152:from]; MIME_GOOD(-0.10)[text/plain]; XM_UA_NO_VERSION(0.01)[]; MIME_TRACE(0.00)[0:+]; DWL_DNSWL_NONE(0.00)[messagingengine.com:dkim]; RCPT_COUNT_ONE(0.00)[1]; FREEMAIL_ENVFROM(0.00)[f-m.fm]; FREEMAIL_FROM(0.00)[f-m.fm]; ASN(0.00)[asn:209242, ipnet:103.168.172.0/24, country:US]; ARC_NA(0.00)[]; TO_DN_ALL(0.00)[]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; DKIM_TRACE(0.00)[f-m.fm:+,messagingengine.com:+] X-Rspamd-Queue-Id: 4X8f6b0yNtz4L6h X-Spamd-Bar: --- On Thu, 19 Sep 2024, at 15:36, Zach Metzinger wrote: > On 9/18/24 08:32, void wrote: >> On Wed, Sep 18, 2024 at 09:44:06AM +0300, Sulev-Madis Silber wrote: >> >>> so any opinions with this arm situation? >> >> The way I'm addressing it is to install netbsd on arm6 and arm7 devices. > > Hello Suley-Madis, > > The way I'm addressing it is to help convert the new device tree file to > something FreeBSD can use. Spare cycles are rare, but it is progressing. > > Ranting about lack of support is not likely to improve the situation. > Putting your valuable personal time on the line just might. I thought there were issues concerning src for (at least armv6) that armv6 was 'stale'? I'm sure I've seen it mentioned if not on this list, then on others. Part or the main reason for it being dropped. In case your "ranting" comment is addressed to me: I can't C/C++ , so if I want these devices to remain on a BSD os then straightforwardly I need one that currently supports the hardware. So, NetBSD. That's not a rant. It's an acknowledgement of the way things are. Nobody is obliged to make things work on my hardware. I just have to go with an OS that supports it. My previous response to the OP was to make them aware of alternatives, that's all. From nobody Thu Sep 19 15:12:43 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 4X8fCM38m6z5X4sf for ; Thu, 19 Sep 2024 15:12:47 +0000 (UTC) (envelope-from zmetzing@pobox.com) Received: from pb-smtp1.pobox.com (pb-smtp1.pobox.com [64.147.108.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4X8fCL54nPz4M1w for ; Thu, 19 Sep 2024 15:12:46 +0000 (UTC) (envelope-from zmetzing@pobox.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=pobox.com header.s=sasl header.b=aEYBuhfL; dmarc=pass (policy=none) header.from=pobox.com; spf=pass (mx1.freebsd.org: domain of zmetzing@pobox.com designates 64.147.108.70 as permitted sender) smtp.mailfrom=zmetzing@pobox.com Received: from pb-smtp1.pobox.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id 033C820F76 for ; Thu, 19 Sep 2024 11:12:46 -0400 (EDT) (envelope-from zmetzing@pobox.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=pobox.com; h=message-id :date:mime-version:subject:to:references:from:in-reply-to :content-type:content-transfer-encoding; s=sasl; bh=PB+qDgRNvvz5 6Nl8RSPXFk7D5slTVQv9ITFVa+9ZjZc=; b=aEYBuhfLeiHqKVA3V196NpSkKLko P4/h7qgO1yABCx1QeZKepCxLwdYJNwSPggs7a2cYyTMOm326qwYjuDoMRlZFZJX1 UNpdrJopU4XZl/KQyaEPAcNA+hcdoGjJoCm7F8crWcEbTCFH2Al/7bcR7TaCtb9p xPm2HNLtOwC+n00= Received: from pb-smtp1.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id F07A120F75 for ; Thu, 19 Sep 2024 11:12:45 -0400 (EDT) (envelope-from zmetzing@pobox.com) Received: from [192.168.1.5] (unknown [47.185.113.8]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pb-smtp1.pobox.com (Postfix) with ESMTPSA id 384F720F74 for ; Thu, 19 Sep 2024 11:12:45 -0400 (EDT) (envelope-from zmetzing@pobox.com) Message-ID: Date: Thu, 19 Sep 2024 10:12:43 -0500 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 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:102.0) Gecko/20100101 Thunderbird/102.9.0 Subject: Re: Beaglebone Black/Green/Blue support (volunteering) Content-Language: en-US To: freebsd-arm@freebsd.org References: <276f57f2-5194-cad1-d859-e49b2bce2580@pobox.com> <69E08B38-7388-46A6-8864-20074BFFF8F4@yahoo.com> <88d2cc76-f980-600e-0da4-2fa1070d76ba@pobox.com> <6b848423-bdd1-b215-889a-1f07e5064412@pobox.com> <4BEC1DC0-7528-4B4B-8FD0-254BD7BF1BD9@ketas.si.pri.ee> From: Zach Metzinger In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Pobox-Relay-ID: 9FAFAC30-7699-11EF-A7CD-2BAEEB2EC81B-19366360!pb-smtp1.pobox.com X-Spamd-Result: default: False [-4.10 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.999]; DMARC_POLICY_ALLOW(-0.50)[pobox.com,none]; R_DKIM_ALLOW(-0.20)[pobox.com:s=sasl]; R_SPF_ALLOW(-0.20)[+ip4:64.147.108.0/24]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[64.147.108.70:from]; RCVD_VIA_SMTP_AUTH(0.00)[]; MIME_TRACE(0.00)[0:+]; ARC_NA(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:19151, ipnet:64.147.108.0/24, country:US]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; DWL_DNSWL_NONE(0.00)[pobox.com:dkim]; TO_DN_NONE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_LAST(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[pobox.com:+] X-Rspamd-Queue-Id: 4X8fCL54nPz4M1w X-Spamd-Bar: ---- On 9/19/24 10:07, void wrote: > In case your "ranting" comment is addressed to me: It was not, no. Thank you for pointing out NetBSD's support. I have several older machines (sun4u and alpha) loaded with NetBSD, which I also enjoy using. --- Zach From nobody Thu Sep 19 17:21:10 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 4X8j3r19kBz5WdNq for ; Thu, 19 Sep 2024 17:21:28 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic313-20.consmr.mail.gq1.yahoo.com (sonic313-20.consmr.mail.gq1.yahoo.com [98.137.65.83]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4X8j3q5L4gz43T4 for ; Thu, 19 Sep 2024 17:21:27 +0000 (UTC) (envelope-from marklmi@yahoo.com) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1726766485; bh=SdXotCza3itfP+KggL5loxfhmUH+2Z1ZbXuWoQ5HleM=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From:Subject:Reply-To; b=X3vVBHME8ofoal5viTTDzQPK9d2PrBqnhIF0dDx4+JAg0JRY9qkh/AluMFzwdx5WIWND8nYGoV7Wv1QmC6eWpoSkQiByRywbqLRh8Bf2MQMY9B7cOxs66Vuv8vjSPgNsunCNoryxdlxGUvO8dicg52oH4XhsfVZ6ry5jUsfUTydYxFNJy+i4unDEjJ3TZrK6DsLiflARcuLJCRzhK2hxX3g+njuFT4nS6ivjrIsrCbH2r2YcvOFi70KzQtxvdvVqMqVVWhBA9XOwl50sitQ0reBjX5KRCggexLOaUZgtbf+dYsZxav8qI81mCPPIx3GUVFs/jpoiEkyLfq17bJbdLw== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1726766485; bh=CI1Y+spo7wdsXa5qRwkIszlsOBIDHggmznJS8N5vs14=; h=X-Sonic-MF:Subject:From:Date:To:From:Subject; b=MroIKTVtN4Difg37i0pRJXPihXJM4AkpN2V+VBQwtteUiFIv/oA7PbrW/fezTm+h2Qcwl9Rumgtj9bwPRfXgNPSjEDja7pNopSNMet5EfXfDKCuVwlCErBuvCuCuATKiADnkLy6ITvaYH480LYPMYjeTrHvjdPjqvg/gV4yX9OfH8lFqbTZ7SkP8SZ+6m2bFs1pA36wpqtyK/g0obFgpFTTjyOYkPHWlkcHhS9xVhthZ1XjDrgsRTGEL06lMbK5sjEqYy2GoD5zrXtBaNd6a2T2GH3yFPpjgc3tXE3abkMib+Z3+sAbRtaoWRG0dcWFteYs+ZT7Cnf2oqgqrCM5fSQ== X-YMail-OSG: Tm_UJekVM1kvqIUSKt.tiuDBp8gL9uz8jkPUBJqHyFTAEx8PQSOcxGvjc2DEZA5 pgitQVVUP07lTbeURmDvxMC2MU86d61Ir8CNMzejO.Snd4vz0v3UrymisdiJ7j4tqOQJgGc_QRyW 1Io6qzOECgaTsQFi40ZzeZMz4vcxzV7qUyWq51nxlKfHWSLXVHbKeo2UKybuWlC67M0tXb8W4naW Q8weNJwotWdXTk.71v26tZqeGZ7k5NO1jQE_tJ1ZRzkWAQtnI7VyD7fmPJl_dT7etGj_mUxSWuN9 W4lVE76ODlvJnw2RT5VG3D45iOv3zlezMwhYJT8.XUs1CC01mNQqJwMiwVwTmZKgbYTioQY8YSDB nVoqJsLrOQWjLF4deiI.DRPBIms8wVTWuBrkF5CAyf8D0CYf6cHyG8VtYeFgz2tw.q9Ot51CHHnC xU2k.sgAlhGqagDxCus1Gy1wAYm7uGOBmSpQI88gBA1yId8x7_Gzr80aOh9fdB9c4wzQTZM2z4dW 4hFbOpiENUpy328R__H6pMjykJltaxsZQCILynY0G.VroCyB1KXC2GpYTSteHzk6AFcHtX4gtqyh kdbb0_pR3X4u0_u44ifAw471t_0B25kbmqW6fp2SyypnqS8GNPF19D7waKqHlfn8e_MDfPsNtgrS tVb2gY88qLBtg0074Ops1JTBrrQ8.N_quM.qFrJ7L92yPF.acjXq7i2vWooXW84uPSHtqRXist14 uOcLI_LX4fgLwjN6P7ujt2tTPK1WD3VkB9fHfKMUAKAGVR6CrReGacR4DvxXdrSrUOHrL90aE032 xBnwBu6Ggk1mko7wvWN5oe0KXWexOtf6i02rK3b.oOCjY7PM68QCxmMCeUu.GuQssk2kBaKd9AMB 6kzP2pImCSWiRLtqbGbn.eg4jFnCN.Xt_JbtND50ES9cbBv388f9DcQPi0VMLFdNxZOuFkgtNZ2h REeU2AZTKqAdcODTMgBaXPchENkx7NW9APOIwgP67L5edXj.v9EFEI_br7CQVmSaUlCVn.qK53xy 19myq6I5OwuCc6LXlktV3lkZqeAUZ53KE_uYAwgqtEB4tO4Kzy4v7.O6GQpz87DssL0uYXarxUzH YxAHMOziHJYdAti1f5.DH6ZTFJLT0txLidZpxdlJM70eNjQF3Z5LCHDK70KmQ3MoWimERKrz5Cl0 _EN9zvXTtn5bXlbBuSMuVlNS9j6LK9K2jJ9ovPUqDRaFEGKpO364ZZFlz8vu5ArFOMMUg9oUoplv W3QLzo0Ts05T4_DXwJydbDiS8DI8fDXkuQ07Yyx7SMevHCtlMP5CvnG1_fodFooAPl2xFi3sM.ia BUi4fWxdqhyuK66fryRdeSHKnAF.RZW_PI24kKIgLu9.epymgxlxnCYNyxw7k93jEIxcdBv3QsOC 5DOUKVwOZaTBOIrKpujniXGNTmzjRydFEIbi4ifQlSR5glIzxT_IVKSxwT3KFHoNKM_fgjfbWCMT RCft50KD8mfEcChIB8F5YB7Vq.EQXUHPLXUOiFFIXSn.g6r0GMUniYslDGTMBU4_SJQnEj_YniCL ZrpIZGILWiNbD95SbQX1kTcaiYNXSC7lDC8W2BwTqzqScxiFCvVNVkwxzxZE9PJfDYZfzwqC3j0p K2PmBey_8LR2G08FW5XJ7bJdaChQaGX57yT0F8q54va6rhFr6Qg.qQO4oASkP8RbriEU459A3cNV iDI7lFjzpE3iZzxrJWKPIVQU6AV7t3uQQHXPWqlL0mDzX5TwoqygYHOb5nwrzt5fiEMyrxzGt9ql H5jTWKSa2PKAChPeLxSpbWs5ufmQT_lPdA.t4IXO9vTjS2LlhvBk6ugHm7gdDDc8xSVruv8OCaJs yTUM2iHS00Hab5LJ82.jC1CJtayS.Y.oFvbHnHG8riDdum56qBarNM2W.ahUwDKIw.NOTp8h4HRD xAC4Z5upy_5eSqWrZc2LMPZnihXwkRMVHmUQtN7eWOvvaN1qcJ9eGzZ6SXZibAy8.NhoupN6T0Nr y_9AzqjHEPHrDB3.uj3S.BDEM2jftG4514uJ3WP59BM9A01TMbUGuhbjxvJcCOm1UIxpdKS6V3KZ qY8tltR_jU1E58kbG8snoCiHzYevkEFXzDPYrtfgk_LVm8vRqcPdRblBuSuW.pMJg_UH0KBrVQib gig46tRuUFuAp6y7RqCckU9PKDQtAHiMh2Xew76Z6LdT4toPF.nMjDHplCjG6AERHzJvi4ldPQOS URP2JaIB7iNWA1Axmuv1Ff6RfCw3tCCCSnc6G X-Sonic-MF: X-Sonic-ID: cc55d399-485f-486a-b7a5-14464ca7275e Received: from sonic.gate.mail.ne1.yahoo.com by sonic313.consmr.mail.gq1.yahoo.com with HTTP; Thu, 19 Sep 2024 17:21:25 +0000 Received: by hermes--production-gq1-5d95dc458-dxlpk (Yahoo Inc. Hermes SMTP Server) with ESMTPA ID 5e994dab1800d5e9fad054e7c8ee1b1a; Thu, 19 Sep 2024 17:21:21 +0000 (UTC) Content-Type: text/plain; charset=us-ascii 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 \(3776.700.51\)) Subject: Re: Beaglebone Black/Green/Blue support (volunteering) From: Mark Millard In-Reply-To: Date: Thu, 19 Sep 2024 10:21:10 -0700 Cc: freebsd-arm@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <7B680499-8260-4C42-97EB-248EA6AC5BC8@yahoo.com> References: <276f57f2-5194-cad1-d859-e49b2bce2580@pobox.com> <69E08B38-7388-46A6-8864-20074BFFF8F4@yahoo.com> <88d2cc76-f980-600e-0da4-2fa1070d76ba@pobox.com> <6b848423-bdd1-b215-889a-1f07e5064412@pobox.com> <4BEC1DC0-7528-4B4B-8FD0-254BD7BF1BD9@ketas.si.pri.ee> To: Zach Metzinger X-Mailer: Apple Mail (2.3776.700.51) X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/20, country:US] X-Rspamd-Queue-Id: 4X8j3q5L4gz43T4 X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated On Sep 19, 2024, at 07:36, Zach Metzinger wrote: > On 9/18/24 08:32, void wrote: >> On Wed, Sep 18, 2024 at 09:44:06AM +0300, Sulev-Madis Silber wrote: >>> so any opinions with this arm situation? >> The way I'm addressing it is to install netbsd on arm6 and arm7 = devices. >=20 > Hello Suley-Madis, >=20 > The way I'm addressing it is to help convert the new device tree file = to something FreeBSD can use. Spare cycles are rare, but it is = progressing. As I understand things, FreeBSD does not have examples of FreeBSD specific Device Tree sources and is not currently set up to support such of itself. The general expectation is to have the kernel updated to track the imported mainline Linux device trees. There is the example of using device trees from a different Linux for the RPi*'s (unmodified binary *.dtb files). That is handled via involving a port: sysutils/rpi-firmware . But the RPi*'s tend to work differently for what needs to be done as well. If you are planning on FreeBSD specific source files for some device trees, you might want to ask about how that should fit into FreeBSD and you might have to provide the changes to allow such unless involving a new port can cover the issue. > Ranting about lack of support is not likely to improve the situation. = Putting your valuable personal time on the line just might. It looked to me to be just a note that NetBSD is an alternative that folks can use. =3D=3D=3D Mark Millard marklmi at yahoo.com From nobody Fri Sep 20 03:36:04 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 4X8yjp0w1bz5Wht6 for ; Fri, 20 Sep 2024 03:36:46 +0000 (UTC) (envelope-from freebsd-arm-freebsd-org097@ketas.si.pri.ee) Received: from green.sau.si.pri.ee (d004-fea2-0bff-021e-13e8-8437-07d0-2001.dyn.estpak.ee [IPv6:2001:7d0:8437:13e8:21e:bff:fea2:d004]) (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 4X8yjm3qq0z4PX0 for ; Fri, 20 Sep 2024 03:36:43 +0000 (UTC) (envelope-from freebsd-arm-freebsd-org097@ketas.si.pri.ee) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=ketas.si.pri.ee header.s=ketas-si-pri-ee-20240416002854-4096 header.b=SAEHPpwt; dmarc=pass (policy=reject) header.from=ketas.si.pri.ee; spf=pass (mx1.freebsd.org: domain of freebsd-arm-freebsd-org097@ketas.si.pri.ee designates 2001:7d0:8437:13e8:21e:bff:fea2:d004 as permitted sender) smtp.mailfrom=freebsd-arm-freebsd-org097@ketas.si.pri.ee X-Original-To: freebsd-arm@freebsd.org DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=ketas.si.pri.ee; s=ketas-si-pri-ee-20240416002854-4096; t=1726803388; bh=Bf1vVpFEQgKWdjtAa0RUhFyTfmIuvukGAfbuofcGAgw=; h=Date:From:To:Subject:In-Reply-To:References; b=SAEHPpwt/2qxL5Z/GYQlcMLJmFTUYWFDh/JaQ2TyL26N817FVF56CGSnv4J0Y0oTZ ZkCPhRW7tLyzbNKZn/UFSRqLLUF/mX/aj+NG06zcoq32cY1oc5ZYibBoWyB0ofaowI WpbjjPAsbf/lR6YRBoEYhLC/UQ6LSMFMm4bK60GFRmjMk1DuQVpqHTqlvhFXYcdURZ sVTuTBE/aEe4sldhJ6ww62pMKwI8vuTi7Ah2rE0sqrrR6wWqf2jZsiWlycK+Jw8ldU SmJKC5+VkvyKgRytlpggYWMmwg/8jSh7oNelUgjMdr96nf3b7GhBCGmVdUQvUua4rw w4wQOuHez/d18BNgauOq7hOVtHqm5zxwAXn2LE3ggQEgnbx7cIfnaVQUVuqWFZQG6H 0TzvvmVuUKVgdCVGuqmoyzOURlLj1whdayGNXij2bmyOaayJ3iBHxPytZfTgvcYnLk JI73kUX9gL7228Dcz3ibDYG/rDe0Ja5Oiz9QOd1LEu0PLJk7ackfwfe9tnpldzm8ju E6dUDsnF0X6NrcbDKmIUTqne4ZuW2anF3UuQh0aYAG3IUwl44foiHnGhNAlIigIcAJ zdteT+j9pzeFuoSyznMZ8vFh8Ci9WZwsQwDNMsW+Oz+KrIwMAj+wDn8nLB+XZ8QDtw lJuKgbS7eC7vLGzy+fYqWJ8I= Received: from [IPv6:::1] (0114-0000-0000-0000-13c8-8437-07d0-2001.dyn.estpak.ee [IPv6:2001:7d0:8437:13c8::114]) (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) (No client certificate requested) by forestgreen.jails.green.sau.si.pri.ee (Postfix) with ESMTPSA id 41D5459BDEA for ; Fri, 20 Sep 2024 06:36:26 +0300 (EEST) Date: Fri, 20 Sep 2024 06:36:04 +0300 From: Sulev-Madis Silber To: freebsd-arm@freebsd.org Subject: Re: Beaglebone Black/Green/Blue support (volunteering) User-Agent: K-9 Mail for Android In-Reply-To: <7B680499-8260-4C42-97EB-248EA6AC5BC8@yahoo.com> References: <276f57f2-5194-cad1-d859-e49b2bce2580@pobox.com> <69E08B38-7388-46A6-8864-20074BFFF8F4@yahoo.com> <88d2cc76-f980-600e-0da4-2fa1070d76ba@pobox.com> <6b848423-bdd1-b215-889a-1f07e5064412@pobox.com> <4BEC1DC0-7528-4B4B-8FD0-254BD7BF1BD9@ketas.si.pri.ee> <7B680499-8260-4C42-97EB-248EA6AC5BC8@yahoo.com> Message-ID: 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=utf-8 Content-Transfer-Encoding: quoted-printable X-Spamd-Result: default: False [-0.90 / 15.00]; HFILTER_HOSTNAME_5(3.00)[d004-fea2-0bff-021e-13e8-8437-07d0-2001.dyn.estpak.ee]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.999]; DMARC_POLICY_ALLOW(-0.50)[ketas.si.pri.ee,reject]; R_DKIM_ALLOW(-0.20)[ketas.si.pri.ee:s=ketas-si-pri-ee-20240416002854-4096]; R_SPF_ALLOW(-0.20)[+ip6:2001:7d0:8437:1300::/56]; ONCE_RECEIVED(0.10)[]; MIME_GOOD(-0.10)[text/plain]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:3249, ipnet:2001:7d0::/32, country:EE]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_ONE(0.00)[1]; RCVD_TLS_ALL(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DKIM_TRACE(0.00)[ketas.si.pri.ee:+] X-Rspamd-Queue-Id: 4X8yjm3qq0z4PX0 X-Spamd-Bar: / "Suley", that's new! : p yea, nbsd was already mentioned=2E as was obsd=2E as was linux=2E=2E=2E as= possible alternatives=2E but hell eh this is not all about all ancient hw either=2E 486 machines=2E isa cards= =2E pcmcia=2E things like this=2E those indeed go to nbsd but more recent=2E one could argue about recentness of 32bit arm tho it was at least fun to help to push to support all hw in bbb=2E now it's = dead=2E i mean yes, it's old now=2E h3 is blazing fast compared to this=2E = unless it's just code optimizing issue but yeah, i can continue this=2E could still test bbb if needed could do new hw too=2E in my limited knowledge i don't likely become fbsd dev=2E not me=2E as in write c=2E "actually" do= hw=2E but could do other things at least aarch64 embedded hw would be bit longer lived in fbsd, no? right now i have this h618 but need help getting current fit for it so i c= an test and report how it goes=2E boards for that are cheaper than rpi too = sometimes, depending on config then, lot of people have even been confused what i search for, even as a h= obby=2E as somehow, os-independent even, common usage would be home router = or desktop=2E and almost all rpi=2E if it's bigger, it's server, if smaller= , it's uc=2E weird too on the other hand, other type of users arent that hidden either=2E or mayb= e they are? so i can't see myself bringing that h618, like on orange pi zero =2E=2E=2E= something board, into tree on my own, but it's good to to have that or som= ething similarly configd/priced/available with fbsd support hell knows what to think of, of all this anyway of course getting wifi there is like pipe dream too i see=2E sdio doesn't = get anywhere, there is whole one driver there iirc which basically does not= hing? and then there was this linux kernel compat for drivers in hope to extend = hw support=2E maybe affects stability but maybe it's acceptable in some cas= es so yeah fbsd is kiiiiind of difficult isn't it=2E in that area From nobody Fri Sep 20 17:22: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 4X9K3F10nSz5WGxq for ; Fri, 20 Sep 2024 17:23:05 +0000 (UTC) (envelope-from pfaller@protonmail.com) Received: from mail-40133.protonmail.ch (mail-40133.protonmail.ch [185.70.40.133]) (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-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "protonmail.com", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4X9K3C62vPz3x33 for ; Fri, 20 Sep 2024 17:23:03 +0000 (UTC) (envelope-from pfaller@protonmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=protonmail.com header.s=protonmail3 header.b=CBWL6GUy; dmarc=pass (policy=quarantine) header.from=protonmail.com; spf=pass (mx1.freebsd.org: domain of pfaller@protonmail.com designates 185.70.40.133 as permitted sender) smtp.mailfrom=pfaller@protonmail.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1726852981; x=1727112181; bh=l7YBODMEwTgAi8H62AzwxWGOIN0fNrXQM8rJWamxhiQ=; h=Date:To:From:Subject:Message-ID:Feedback-ID:From:To:Cc:Date: Subject:Reply-To:Feedback-ID:Message-ID:BIMI-Selector; b=CBWL6GUyBpyWMRziGnXscycI0pyj931nmBLsDqxcXi5wufi2PxJ5DioZSbA1RorPr 1GAXMRKQpG03yTeSCrqg1/bQnGrDkklHDuk9WNzVg1XGady7QPd8E6CsDs/gn5WvUg nT6zLsqUZVBIBmjFTi5HQS3rstJXKsCEjGjnROHNamu33h9e8/1RHfa3ikuAeRL5Pd bcdFEh3x7m+PLHvr7yPnigjQbh/0nNuH0bdDstg5seaOtv7cvcjq7iq4wUy39Hp8US kAuRKCcdRVihn1AmYG4mLNlRyVjB6sunXYm7WX6yV4XOH1Wrr+mISKUgJT1t1wCYeX T8eQwIaCneBng== Date: Fri, 20 Sep 2024 17:22:58 +0000 To: "freebsd-arm@FreeBSD.org" From: Christoph Pfaller Subject: Rockchip RK3328 Rock64 HDMI Message-ID: <5kADboXE-OUia2ncm13XjDesvDmjB3tjWSyr3ytCpa5XYof9xOrL9AbRownQoRG9eJcJpYswqjbMt0P0XiZfs7KNNfiNF7vQ93m72mm_Fyk=@protonmail.com> Feedback-ID: 1757974:user:proton X-Pm-Message-ID: a212aa0ba1e5d2deb933c9b0901b89ce59353891 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: multipart/alternative; boundary="b1_V7SmNmifUaZUDKgj1VjplrjdEiEo7oQZqOxcsBU8c9Q" X-Spamd-Result: default: False [2.57 / 15.00]; MIME_BASE64_TEXT_BOGUS(1.00)[]; NEURAL_SPAM_MEDIUM(1.00)[0.999]; NEURAL_SPAM_LONG(1.00)[0.998]; NEURAL_SPAM_SHORT(0.68)[0.677]; DMARC_POLICY_ALLOW(-0.50)[protonmail.com,quarantine]; R_DKIM_ALLOW(-0.20)[protonmail.com:s=protonmail3]; R_SPF_ALLOW(-0.20)[+ip4:185.70.40.0/24:c]; RWL_MAILSPIKE_VERYGOOD(-0.20)[185.70.40.133:from]; MIME_BASE64_TEXT(0.10)[]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; MID_RHS_MATCH_FROM(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; ARC_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_FROM(0.00)[protonmail.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_EQ_ADDR_ALL(0.00)[]; MLMMJ_DEST(0.00)[freebsd-arm@FreeBSD.org]; ASN(0.00)[asn:62371, ipnet:185.70.40.0/24, country:CH]; RCVD_COUNT_ZERO(0.00)[0]; HAS_PHPMAILER_SIG(0.00)[]; MISSING_XM_UA(0.00)[]; FREEMAIL_ENVFROM(0.00)[protonmail.com]; DKIM_TRACE(0.00)[protonmail.com:+]; FROM_HAS_DN(0.00)[] X-Rspamd-Queue-Id: 4X9K3C62vPz3x33 X-Spamd-Bar: ++ This is a multi-part message in MIME format. --b1_V7SmNmifUaZUDKgj1VjplrjdEiEo7oQZqOxcsBU8c9Q Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: base64 SGVsbG8hCgpJIHJlY2VudGx5IHN3aXRjaGVkIHRvIEZyZWVCU0Qgb24gbXkgUm9jazY0IGR1ZSB0 byBhcHBlYXJpbmcga2VybmVsIHBhbmljcyB3aGVuIHJ1bm5pbmcgdGhlIGJvYXJkIHdpdGggTGlu dXguIFNvIGZhciBJIGVuam95IHRoZSBvcGVyYXRpbmcgc3lzdGVtLiBIb3dldmVyOyB0aGVyZSBp cyBvbmUgbGl0dGxlIGFubm95YW5jZSAtIHRoZSBpbnRlZ3JhdGVkIEhETUkgb3V0cHV0IGRvZXMg bm90IHdvcmsuIFNvIEkgd2FudCB0byBjaGFuZ2UgdGhhdC4KCkFzIHdlIGFyZSBvbiBBUk0gbXkg Zmlyc3QgaW50ZW50aW9uIHdhcyBsb29raW5nIGludG8gdGhlIGRldmljZSB0cmVlIGZvciB0aGUg cmszMzI4LiBJIGNvbXBhcmVkIGl0IHRvIExpbnV4IGRldmljZSB0cmVlIGFuZCBhbHNvIGZvdW5k IHNvbWUgbWlzc2luZyBwYXJ0cy4gTXkgbmV4dCBzdGVwIHdhcyBsb29raW5nIGludG8gdGhlIGRy aXZlcnMgaXRzZWxmIGFuZCBhcyB0aGUgTGludXggZHJpdmVycyBzb3VyY2VzIGFyZSBhdmFpbGFi bGUgaGVyZSBodHRwczovL2dpdGh1Yi5jb20vdG9ydmFsZHMvbGludXgvdHJlZS9tYXN0ZXIvZHJp dmVycy9ncHUvZHJtL3JvY2tjaGlwIEkgZ290IHNvbWUgaWRlYSBob3cgdGhlIGNvcnJlc3BvbmRp bmcgZHJpdmVyIHNob3VsZCBsb29rIGxpa2UuCgpIb3dldmVyLCBJIGFtIHVuc3VyZSBob3cgSSBz aG91bGQgcHJvY2VlZCBnZXR0aW5nIEhETUkgdG8gd29yay4gQWNjb2RyaW5nIHRvIGh0dHBzOi8v d2lraS5mcmVlYnNkLm9yZy9hcm0vUm9ja0NoaXAgSERNSSB3b3JrcyBmb3IgdGhlIHJvY2tjaGlw IHJrMzM5OSBidXQgSSBjb3VsZCBub3QgZmluZCBhbnkgZHJpdmVycyBuZWl0aGVyIGluIHRoZSBm cmVlYnNkLXNyYyBvciBkcm0ta21vZCAoSSBhbSBuZXcgdG8gRnJlZUJTRCBzbyBpIGRvbid0IGtu b3cgaWYgdGhpcyBpcyBldmVuIHRoZSByaWdodCBwbGFjZSB0byBsb29rIGZvcikuIEkgaG9wZSBz b21lb25lIHdpdGggbW9yZSB0ZWNobmljYWwga25vd2xlZGdlIGFib3V0IEZyZWVCU0Qgb3IgSERN SSBjYW4gcHJvdmlkZSBtZSB3aXRoIHNvbWUgZ3VpZGFuY2Ugb24gd2hlcmUgSSBoYXZlIHRvIGxv b2sgYW5kIHdvcmsgb24uCgpHcmVldGluZ3MKcGYw --b1_V7SmNmifUaZUDKgj1VjplrjdEiEo7oQZqOxcsBU8c9Q Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: base64 PGRpdiBzdHlsZT0iZm9udC1mYW1pbHk6IEFyaWFsLCBzYW5zLXNlcmlmOyBmb250LXNpemU6IDE0 cHg7IGNvbG9yOiByZ2IoMCwgMCwgMCk7IGJhY2tncm91bmQtY29sb3I6IHJnYigyNTUsIDI1NSwg MjU1KTsiPkhlbGxvITxicj48YnI+SSByZWNlbnRseSBzd2l0Y2hlZCB0byBGcmVlQlNEIG9uIG15 IFJvY2s2NCBkdWUgdG8gYXBwZWFyaW5nIGtlcm5lbCBwYW5pY3Mgd2hlbiBydW5uaW5nIHRoZSBi b2FyZCB3aXRoIExpbnV4LiBTbyBmYXIgSSBlbmpveSB0aGUgb3BlcmF0aW5nIHN5c3RlbS4gSG93 ZXZlcjsgdGhlcmUgaXMgb25lIGxpdHRsZSBhbm5veWFuY2UgLSB0aGUgaW50ZWdyYXRlZCBIRE1J IG91dHB1dCBkb2VzIG5vdCB3b3JrLiBTbyBJIHdhbnQgdG8gY2hhbmdlIHRoYXQuPGJyPjxicj5B cyB3ZSBhcmUgb24gQVJNIG15IGZpcnN0IGludGVudGlvbiB3YXMgbG9va2luZyBpbnRvIHRoZSBk ZXZpY2UgdHJlZSBmb3IgdGhlIHJrMzMyOC4gSSBjb21wYXJlZCBpdCB0byBMaW51eCBkZXZpY2Ug dHJlZSBhbmQgYWxzbyBmb3VuZCBzb21lIG1pc3NpbmcgcGFydHMuIE15IG5leHQgc3RlcCB3YXMg bG9va2luZyBpbnRvIHRoZSBkcml2ZXJzIGl0c2VsZiBhbmQgYXMgdGhlIExpbnV4IGRyaXZlcnMg c291cmNlcyBhcmUgYXZhaWxhYmxlIGhlcmUmbmJzcDs8c3Bhbj48YSB0YXJnZXQ9Il9ibGFuayIg cmVsPSJub3JlZmVycmVyIG5vZm9sbG93IG5vb3BlbmVyIiBocmVmPSJodHRwczovL2dpdGh1Yi5j b20vdG9ydmFsZHMvbGludXgvdHJlZS9tYXN0ZXIvZHJpdmVycy9ncHUvZHJtL3JvY2tjaGlwIj5o dHRwczovL2dpdGh1Yi5jb20vdG9ydmFsZHMvbGludXgvdHJlZS9tYXN0ZXIvZHJpdmVycy9ncHUv ZHJtL3JvY2tjaGlwPC9hPjwvc3Bhbj4gSSBnb3Qgc29tZSBpZGVhIGhvdyB0aGUgY29ycmVzcG9u ZGluZyBkcml2ZXIgc2hvdWxkIGxvb2sgbGlrZS48YnI+PGJyPkhvd2V2ZXIsIEkgYW0gdW5zdXJl IGhvdyBJIHNob3VsZCBwcm9jZWVkIGdldHRpbmcgSERNSSB0byB3b3JrLiBBY2NvZHJpbmcgdG8g PHNwYW4+PGEgdGFyZ2V0PSJfYmxhbmsiIHJlbD0ibm9yZWZlcnJlciBub2ZvbGxvdyBub29wZW5l ciIgaHJlZj0iaHR0cHM6Ly93aWtpLmZyZWVic2Qub3JnL2FybS9Sb2NrQ2hpcCI+aHR0cHM6Ly93 aWtpLmZyZWVic2Qub3JnL2FybS9Sb2NrQ2hpcDwvYT48L3NwYW4+IEhETUkgd29ya3MgZm9yIHRo ZSByb2NrY2hpcCByazMzOTkgYnV0IEkgY291bGQgbm90IGZpbmQgYW55IGRyaXZlcnMmbmJzcDsg bmVpdGhlciBpbiB0aGUgZnJlZWJzZC1zcmMgb3IgZHJtLWttb2QgKEkgYW0gbmV3IHRvIEZyZWVC U0Qgc28gaSBkb24ndCBrbm93IGlmIHRoaXMgaXMgZXZlbiB0aGUgcmlnaHQgcGxhY2UgdG8gbG9v ayBmb3IpLiBJIGhvcGUgc29tZW9uZSB3aXRoIG1vcmUgdGVjaG5pY2FsIGtub3dsZWRnZSBhYm91 dCBGcmVlQlNEIG9yIEhETUkgY2FuIHByb3ZpZGUgbWUgd2l0aCBzb21lIGd1aWRhbmNlIG9uIHdo ZXJlIEkgaGF2ZSB0byBsb29rIGFuZCB3b3JrIG9uLjxicj48YnI+R3JlZXRpbmdzPGJyPnBmMDxi cj48YnI+PGJyPjwvZGl2Pg== --b1_V7SmNmifUaZUDKgj1VjplrjdEiEo7oQZqOxcsBU8c9Q-- From nobody Fri Sep 20 18:01: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 4X9KwQ5VcFz5WSMq for ; Fri, 20 Sep 2024 18:02:14 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic310-21.consmr.mail.gq1.yahoo.com (sonic310-21.consmr.mail.gq1.yahoo.com [98.137.69.147]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4X9KwQ12nrz45XG for ; Fri, 20 Sep 2024 18:02:14 +0000 (UTC) (envelope-from marklmi@yahoo.com) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1726855332; bh=0Bua84w36EdlhOH8Wslz2Nim1JocLvp9RNs3J7Opc7w=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From:Subject:Reply-To; b=i8eX67FxrkrRjDiAmHuCKibzZ2ScMxSPtxkxTRxSced6EF5vfA4uc4os90Zh18QPkedx2F7vxxL0+HXRUUfd17gS9rpzWrV2Pu7nOlf6XXdMXFV0lg0pP7N55H+u0zsO2LXDNYcxaUWEI4EMNcPksgsg6Lh+pZlOlb7ELYfiwW2r2rZRh+KK65QPJehAUe5o8WfJxsXgZALI3kTeW7PVN5nDbs411JhaQUwM2+S7S9GrJm8bsgRt/dd7ksond44imGnVc76ZRIp5Nig6Lpnz2IyTHnnZmfnwqSchCxTyOgfnF4q1JX4UKp1ZEIU+TABFtIkRR04bhzkWpD2A0CydFQ== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1726855332; bh=sXHzvgFDI7WRHux7jeAsbCnfzcct4NFc9qINADNfBL3=; h=X-Sonic-MF:Subject:From:Date:To:From:Subject; b=JiYvkklulwZ5SuiRJVUncXXoygvArMQPCPNwPUuvyQHS9WS5DzLlPLUtra2WKccVwtr40rBM1mNTS7x1VZOoXhCI7uYTWGrH/Qo72Lt3SAdH+mKD4ZD7SHWvckLtbycpltDbCwTAW4gYd239Fcn4LHh5+jXxxqMUwVrQ66t0vUTeX40QwKQjTYUaCwisVFONdjw7d+Y+x94BVRi/3RCgOOsfZmC8YZ82k8PTOFS9nwE0UkIYL2ehppgFR8PkHV9hRZd2arXzXOi2eH/mGSlz2r6333pa6TuMp65UKAMVV2rewCT+D1Qw0WlLkdkk+2HY36Hoz5n7aO7r/FbmZcmOxA== X-YMail-OSG: RBHy1.gVM1kmy_1Sz00AVsI_iIKEFjWj5lT4P_JZ.eyJdEuFpFQ2Idm8MBlM0gf URQ4MMbOskfGltokABjOdMtxYzdGx7lMuFMI7ugSg8bWyifUEfb3oI4IYKBiN_DxIlqasRLfkN7L I.5PKsYxUTD89Cv.R5N70ETU6dts2iM7b52rhB6XKxXCRIcF5rasiRHYbuVfJWa573NtabUmgekO wK_zKPSCYMor0WsbPhardWCq57K80wI8sKvfnrboCJ_QmtERSsuDwP5jQl_IUszp5jVTyRDN5dSW NIlL_RDDfzulP1o1ZO9DmQ3YAClLwL4KXBBIbQCfnIgaZlu8mPwwy5XfQa9wUVBgbsHyc7ZDyZZF M.QLwvd3RtiZPBTBVa6.OhbhVULDBCpBBWYKMcn0fPC5GncgwlVOaiX4tEvGDBEiqcia84k4okHw .Yp6uE6.FJfWq448PuhoezAfO.Im2EfRwnuwZ3QEUX3MLcYFtTERTwU1J_9ZsXIbmZ.6I6AmR.IN p5VxXCzdGM5toVSsQZrChbzMfJH71_XFLTmNePr9HW0KnrLf8uO76tuVmOBtEQuReDeCd6OM8bon 854foowD9f8p91mq0dxdZvyRYF1e52jiatsjirmgtujC_lcjNzru4kVhVqohnncuZVYwsXQrT67v SAnCt17jzcEaBSdJA22fUhS0KlQU6Fl7UxL8KUsX7yH0IZNjrG_aDgtIkgpWH.PVI.I6vDOl7oQ2 Qu60pAVgWcE95_dzrDvVMtSpiW9sM3_WoL_pz_Oyeuw1g4wqZUk8J5nljnTU0g6GRPG82Qbjkkit 5vX0T6Pz4gJk8pRMb4ook9Gu6FKh1ahegvMylPummut23EptKU7XZqvOLpC.17N_tsc2uOyeKLfZ kIB4DMUTtgYBNmEGbXld3GmyVWnnB4bZSQCe7F4n9sotl.g8LSo6mj.36c0CiRD44K6u_U5rcAZe da1KC8xUK.nfw3Oh2hsyvB3bl7HeuaghBql_vuD1rJZKUC5IEBbVQVkt2eJxWpS4emDx3eDrz4hT myLAEJh2ob.zLQgFlpU0TXQgzvgEXANQsV.UThnwjPOUBOI_yLm5sMNv0jSYfCMZ_45hnqtUBjiR BOxK04WX2EsGu4yfbYT.hVTkDXILnvdWyYmdrW9sl_8fee_NT2jiUZhVSmflXuJd68JgJ2vHPgk6 GJJaNRLuKda.tL6KyNBl39Vf7h5MLir2TdxS8jR.QVamVVnlqsgRHl4FilXX0p4y24g4i.ak_Ga1 Ex6Ig46p6vbjV7lMaBiFktmnzRJm4z9TvKnJjSwme0pekyyy7CLc6y_hybC8plnNbOmBKewEBaxN 6Xh0R37KEyp_KXrrOw4s9cA080A64XLkTgRcuQL0EMbWnSQDP2oivRNYeHf0Z82bKHs8DiKMFb4H r6kyNZtLJLTCDn6.entwVvRemSa9YVsWsPBdVEvn1x1y9.uiFLZlvDs4rvtTxegIafGJEZMN4g1X ZMJ6ikKB8SIUZejM6dbYS4xmMor8ACK2bmdO2YBOS9ezXKdRL0iXbNUrD.4pCi1LtKIkfiOppCoJ EeLgJH.Lzkciuw0s4ur9rS9O3mcetUIAyDzcWZpHyqVCsb9DurcO4JhaDw_BSlhTH16CYuTI00lX FZsRpDCzYmmsrdlaBQxaaLQ46UudCCuGsM6oOG1msdBeWiEQfo86kezSIgDFzKrmrgkQk76ndnGs UvHxufIN._8s5SkmnFEwnM9OiP.2d.tCGVTtO7uI6rWUuY1qc0P9t7.p.8.3N.ahRmuAb6InFlvW RfDcv5adtIf0yjAm6kpx.JMr9ZMX4p.6Wqo6uonQfVFyiZgrs1QuQqYUhFmTQm6IbVQkrHVjolSa tm0ZmnM2.uuMMoNv3RGsOTzXzeC7pCq_IK9cDyx.x2G8FwTZMhiHKmKv6LrQA7GCLgQJ_6q_1uTC E3MNZlzZXxy6RIQulahxAwCCmYGlnsDYgLfqO70HdQP7uhriOhgKxJW2uPUDcvImEKAgEyZS7TFq 42bsqYuQvcYkkAhNS1OSrSDqiQlQ.iU_gO4i7ExoZ0XT6gaCllYwjJPtM8_4roknfpC.fJwsU52_ vOMetSZ.TZ9UuTMFgtCycRHiao9sa4DIb9DmdnFdzCEZhFskwd_T0t2qRqXU3OPALYpmiqFzTwy9 VHoEut0m408ZpxcW00_aEwh0eqoy.f0rPgHSZM9nFenFy9YhmcgdVkKCHNJ_m5qHEVGglx7OWqH4 1jGDpZMwkeQXY7GbKA.1ad3RyTHOhUD0nx9RsRBPTc5dZYVCOh6Zhl2rRIvxr7d2Pjii2hryjOxt cdmUFvjsTTZeb3OI- X-Sonic-MF: X-Sonic-ID: 74a4662f-dddc-4e30-803b-68e54fde8254 Received: from sonic.gate.mail.ne1.yahoo.com by sonic310.consmr.mail.gq1.yahoo.com with HTTP; Fri, 20 Sep 2024 18:02:12 +0000 Received: by hermes--production-gq1-5d95dc458-dxlpk (Yahoo Inc. Hermes SMTP Server) with ESMTPA ID ab202b41f3253e8f11f5eaf33ad4f8af; Fri, 20 Sep 2024 18:02:09 +0000 (UTC) Content-Type: text/plain; charset=us-ascii 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 \(3776.700.51\)) Subject: Re: Rockchip RK3328 Rock64 HDMI From: Mark Millard In-Reply-To: <5kADboXE-OUia2ncm13XjDesvDmjB3tjWSyr3ytCpa5XYof9xOrL9AbRownQoRG9eJcJpYswqjbMt0P0XiZfs7KNNfiNF7vQ93m72mm_Fyk=@protonmail.com> Date: Fri, 20 Sep 2024 11:01:58 -0700 Cc: "freebsd-arm@FreeBSD.org" Content-Transfer-Encoding: quoted-printable Message-Id: References: <5kADboXE-OUia2ncm13XjDesvDmjB3tjWSyr3ytCpa5XYof9xOrL9AbRownQoRG9eJcJpYswqjbMt0P0XiZfs7KNNfiNF7vQ93m72mm_Fyk=@protonmail.com> To: Christoph Pfaller X-Mailer: Apple Mail (2.3776.700.51) X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/20, country:US] X-Rspamd-Queue-Id: 4X9KwQ12nrz45XG X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated On Sep 20, 2024, at 10:22, Christoph Pfaller = wrote: > 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. What vintage of the Linux materials were you comparing against? https://cgit.freebsd.org/src/log/sys/contrib/device-tree/ shows the most recent import to main [so: 15] was: "Import device-tree files from Linux 6.8" on 2024-05-06. 6.6 and 6.7 were imported earlier that same day, so previously FreeBSD was based on 6.5 . FreeBSD deliberately does not track Linux-version-by-Linux-version, nor at the same time Linux released what FreeBSD synchronizes to. > 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. =3D=3D=3D Mark Millard marklmi at yahoo.com From nobody Fri Sep 20 18:02:25 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 4X9Kwx6zTyz5WSpK for ; Fri, 20 Sep 2024 18:02:41 +0000 (UTC) (envelope-from zmetzing@pobox.com) Received: from pb-smtp2.pobox.com (pb-smtp2.pobox.com [64.147.108.71]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4X9Kwx2F7Gz45hy for ; Fri, 20 Sep 2024 18:02:41 +0000 (UTC) (envelope-from zmetzing@pobox.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=pobox.com header.s=sasl header.b=V4dQsQ1P; dmarc=pass (policy=none) header.from=pobox.com; spf=pass (mx1.freebsd.org: domain of zmetzing@pobox.com designates 64.147.108.71 as permitted sender) smtp.mailfrom=zmetzing@pobox.com Received: from pb-smtp2.pobox.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id 50FCC1CC6A for ; Fri, 20 Sep 2024 14:02:40 -0400 (EDT) (envelope-from zmetzing@pobox.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=pobox.com; h=message-id :date:mime-version:subject:to:references:from:in-reply-to :content-type:content-transfer-encoding; s=sasl; bh=Pa8iNimyoy2Y 5wlasFNid6kIwJyt+BzeTBWki3EWluE=; b=V4dQsQ1PfgkIni+jIkx13/I5bUvp c2jbdJ2ScLRhgAUpkIw4DMo5OSxcEzhh6DP7AJfU7x0cEbta+ERYFainiHYuRZlh 7C1WhQ1VnunJ6Qv3JTZOtQN4kfIEvHMj6Ewh9Fx1XXvKnc0G/5BroHNzRzlw+9tT iP2d/8LZyOYsgOs= Received: from pb-smtp2.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id 4844F1CC69 for ; Fri, 20 Sep 2024 14:02:40 -0400 (EDT) (envelope-from zmetzing@pobox.com) Received: from [192.168.1.11] (unknown [47.185.113.8]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pb-smtp2.pobox.com (Postfix) with ESMTPSA id 920E41CC67 for ; Fri, 20 Sep 2024 14:02:38 -0400 (EDT) (envelope-from zmetzing@pobox.com) Message-ID: <17af25e9-2cd9-6293-deba-df1087a93640@pobox.com> Date: Fri, 20 Sep 2024 13:02:25 -0500 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 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:102.0) Gecko/20100101 Thunderbird/102.9.0 Subject: Re: Beaglebone Black/Green/Blue support (volunteering) Content-Language: en-US To: freebsd-arm@freebsd.org References: <276f57f2-5194-cad1-d859-e49b2bce2580@pobox.com> <69E08B38-7388-46A6-8864-20074BFFF8F4@yahoo.com> <88d2cc76-f980-600e-0da4-2fa1070d76ba@pobox.com> <6b848423-bdd1-b215-889a-1f07e5064412@pobox.com> <4BEC1DC0-7528-4B4B-8FD0-254BD7BF1BD9@ketas.si.pri.ee> <7B680499-8260-4C42-97EB-248EA6AC5BC8@yahoo.com> From: Zach Metzinger In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Pobox-Relay-ID: 85D1AB6A-777A-11EF-BBE7-9B0F950A682E-19366360!pb-smtp2.pobox.com X-Spamd-Result: default: False [-4.10 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.998]; DMARC_POLICY_ALLOW(-0.50)[pobox.com,none]; R_DKIM_ALLOW(-0.20)[pobox.com:s=sasl]; R_SPF_ALLOW(-0.20)[+ip4:64.147.108.0/24]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[64.147.108.71:from]; RCVD_VIA_SMTP_AUTH(0.00)[]; MIME_TRACE(0.00)[0:+]; ARC_NA(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:19151, ipnet:64.147.108.0/24, country:US]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; DWL_DNSWL_NONE(0.00)[pobox.com:dkim]; TO_DN_NONE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_LAST(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[pobox.com:+] X-Rspamd-Queue-Id: 4X9Kwx2F7Gz45hy X-Spamd-Bar: ---- On 9/19/24 22:36, Sulev-Madis Silber wrote: > it was at least fun to help to push to support all hw in bbb. now > it's dead. i mean yes, it's old now. h3 is blazing fast compared to > this. unless it's just code optimizing issue Sometimes, it is not the speed that matters in an application but, rather, the current draw, form factor, or interfaces. In many of my remote-monitoring/control applications, the BBG is nearly ideal for the power profile, I/O capability, and form factor. I'm not using it as a desktop workstation. I also appreciate that the processor isn't just a re-purposed GPU/CPU combo originally designed for a cell phone, with a binary blob controlling the GPU and then FBSD being loaded and executed by the CPU. This information may be outdated, but that was my understanding of the Pi processor architecture. I'm unable to parse some of your other comments, but I will say that I've used 802.11b/g/a/n dongles (Wifi) on the BBG without too many issues. As for SDIO, that is (unfortunately) a closed spec, but there has been a lot of useful reverse-engineering that allows many SDIO peripherals to work fine (perhaps not under FBSD -- however). --- Zach From nobody Fri Sep 20 20:32:50 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 4X9QVZ0cGqz5XB7t for ; Fri, 20 Sep 2024 21:28:38 +0000 (UTC) (envelope-from dsl@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (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-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4X9QVY6KB6z4qpp; Fri, 20 Sep 2024 21:28:37 +0000 (UTC) (envelope-from dsl@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1726867717; 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: in-reply-to:in-reply-to:references:references; bh=DCvR7jMHGxF9BMvLDSFKdcMkBYAMKhsXUvTt+LdIeRo=; b=Vv/AFNrhU2xMzfeBnrb/l180eR+J1GGQA4WqIYGgoB9rNIz0r0tkoOxzpzh7y0/BmED0R7 EyEnsvewM4T+WAtEyci1LeaL5UnqWc24ziHn5r9+BVTTW1uzQ0DaOO/mMNmIWKmB7VDTn0 IpGM3MEevRKzTFdbAdZXhPoG9ss/KgFRcZ+NKgrqlwrOt2VSCUujILRfioye6xMpyPoSe6 bi86m9HlyiiB4DSSKKTQ4bCRkibD9nz4rGx6lbYrWEpsbiM9h/cwb/5hz+1S+J2gjgTU4n Vt60+YUA3eNoLvqQZZF/EH19Xl2MS1z1s6lwbonawaKj/ApVOAjdo8PZyDy7XA== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1726867717; a=rsa-sha256; cv=none; b=mPL/XeaXIKd8IQ26YQ17rznsaR2xH7IAruBCwSki7NIyg7lxo6a3aqtx/6iRmrw+kIcl9C o2cPnJPa9k4MwDbBqPvAGv1JdT7UDnxMm30ajBcCbcyibpiw/dTZTavRQXUcwx5HR3LfsP p15qR+Q8htzfg3nsejEozFh5eAkRX/dUe+fzFBY/Sg4SoOsfoQH8obX/ETScHSd/QyrEFP 7TxqUSnj1/d2uG+eUgpCRmHV9GmuyUNpaB8RL51MS+ydG7JJnJKT9L52zeBI3n4J7GfY+a 8c4KDqQ7jV0j42O4WqvpSshh/DGpA2JdMh64f/8UEb4SoM6u/W1puWKgtxtOgg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1726867717; 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: in-reply-to:in-reply-to:references:references; bh=DCvR7jMHGxF9BMvLDSFKdcMkBYAMKhsXUvTt+LdIeRo=; b=wfJcDi8bPcRAmhjpAPKISSCPhWYs4OHLytcXN3ZBqwQ4kiPmd0o60NCK3gfn/bk79DRgso smzn8hJWmyr3Bel0feUfUilypSEHCCusjQ6Dsqu8CHB7X7pE2dreMqTGangOco0rxOuIQZ ydsR3d8OHiUtXZPSTIoT8y4hCLhriZuUElCaotC2GajNNjQ4h26E7WfYX9hQjTgAayuQJU pIE4l2SRAaSQB39C/M89pU557W6NwIQOCVWb2QkakEYK7+Gwsbrnij5ncJwI7jN4Evf12W X8VHFKcqzHndQT/QpYoPlD2kyPA4a884s5zg6cVtLCxbMLwnWzUODF1J3Q/Kcg== Received: from localhost (unknown [91.226.51.235]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: dsl) by smtp.freebsd.org (Postfix) with ESMTPSA id 4X9QVY3tRHzQZk; Fri, 20 Sep 2024 21:28:37 +0000 (UTC) (envelope-from dsl@FreeBSD.org) References: <5kADboXE-OUia2ncm13XjDesvDmjB3tjWSyr3ytCpa5XYof9xOrL9AbRownQoRG9eJcJpYswqjbMt0P0XiZfs7KNNfiNF7vQ93m72mm_Fyk=@protonmail.com> User-agent: mu4e 1.8.13; emacs 29.4 From: Dmitry Salychev To: Christoph Pfaller Cc: freebsd-arm@freebsd.org Subject: Re: Rockchip RK3328 Rock64 HDMI Date: Fri, 20 Sep 2024 22:32:50 +0200 In-reply-to: <5kADboXE-OUia2ncm13XjDesvDmjB3tjWSyr3ytCpa5XYof9xOrL9AbRownQoRG9eJcJpYswqjbMt0P0XiZfs7KNNfiNF7vQ93m72mm_Fyk=@protonmail.com> Message-ID: <86a5g2ypz1.fsf@peasant.bootbsd.com> 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 Christoph Pfaller writes: > 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 output does not work. So I want to > change that. > > 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. > > 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. > > Greetings > pf0 Hey! I'd start digging into: sys/contrib/device-tree/src/arm64/rockchip/rk3399-rockpro64.dts sys/contrib/device-tree/src/arm64/rockchip/rk3399-rockpro64.dtsi sys/contrib/device-tree/src/arm64/rockchip/rk3399-rockpro64-v2.dts Btw, "hdmi" node is enabled in rk3399-rockpro64.dtsi: #include "rk3399.dtsi" #include "rk3399-opp.dtsi" ... &hdmi { ddc-i2c-bus = <&i2c3>; pinctrl-names = "default"; pinctrl-0 = <&hdmi_cec>; status = "okay"; }; If you take a look at rk3399.dtsi, you'll see: hdmi: hdmi@ff940000 { compatible = "rockchip,rk3399-dw-hdmi"; reg = <0x0 0xff940000 0x0 0x20000>; interrupts = ; clocks = <&cru PCLK_HDMI_CTRL>, <&cru SCLK_HDMI_SFR>, <&cru SCLK_HDMI_CEC>, <&cru PCLK_VIO_GRF>, <&cru PLL_VPLL>; clock-names = "iahb", "isfr", "cec", "grf", "ref"; power-domains = <&power RK3399_PD_HDCP>; reg-io-width = <4>; rockchip,grf = <&grf>; #sound-dai-cells = <0>; status = "disabled"; Try to grep sys/dev, but I don't see any driver on the latest CURRENT which declares compatibility with "rockchip,rk3399-dw-hdmi". drivers/gpu/drm/rockchip/dw_hdmi-rockchip.c from the Linux source tree is only ~600 LoC. You'd try to port it to FreeBSD using LinuxKPI[1], I guess. I'd love to try running it on my PinePhone Pro. Regards, Dmitry [1] https://wiki.freebsd.org/LinuxKPI -- https://wiki.freebsd.org/DmitrySalychev From nobody Fri Sep 20 23:06:21 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 4X9SnH4nzVz5XlhX for ; Fri, 20 Sep 2024 23:11:31 +0000 (UTC) (envelope-from maciphone2@googlemail.com) Received: from mail-wr1-x42d.google.com (mail-wr1-x42d.google.com [IPv6:2a00:1450:4864:20::42d]) (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 4X9SnG3Z9Jz41yr for ; Fri, 20 Sep 2024 23:11:30 +0000 (UTC) (envelope-from maciphone2@googlemail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=googlemail.com header.s=20230601 header.b=b3L1kFTd; dmarc=pass (policy=quarantine) header.from=googlemail.com; spf=pass (mx1.freebsd.org: domain of maciphone2@googlemail.com designates 2a00:1450:4864:20::42d as permitted sender) smtp.mailfrom=maciphone2@googlemail.com Received: by mail-wr1-x42d.google.com with SMTP id ffacd0b85a97d-374bfc395a5so1656472f8f.0 for ; Fri, 20 Sep 2024 16:11:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20230601; t=1726873889; x=1727478689; 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=Eks9w+9J6xkACvoS1L58gx4TkP9EALrAoLv8Yg2kuB4=; b=b3L1kFTdFXID3WeU43md3//UO4QhFPNP3FQJopUoBIh1OUdAszEiKZt3FMNHxsy6rf Fxh9ZefR59uYlfpXIdXuObaehWWN5B9/+33YzJESAUcQuuZla4McFqNjLBXRNLszRYu1 HQROOkXmeAJEvLUiPKcn0h0yuZQrPLBkPUuc+3L14OJtNyTxK/mlyTxzb+inloxfrkMd /WGaMNzW5beOeRqrvPOXIUeGdZV2k1+D7SmUQ7SJUsEfeBTGnW5kRCZOxDNcc7A0tSIQ VecRI6YNfubp6sDMPyEJhbzb/pE5jA9eFYeZYRg3CDYe9PflWbWSk398puT187MR1Ay4 S2Jw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1726873889; x=1727478689; 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=Eks9w+9J6xkACvoS1L58gx4TkP9EALrAoLv8Yg2kuB4=; b=r4IXidVtUfFlFj4lRag3OTNAN7xM+937XGx0SNzAKfFLcFrvbnlK1V3C9paXOydxga 2TmxnXeN1EfMhGkCNvbg/d4+obyMNaEVkNwbVxIkQa18UvjAmoa+bJfp4JR7q7mFAbky 5QzgPV5ZtoQHRtxqKnH1J+snaq5IBOz50tKLUfd+Sgdv32Rbvcmo3f3gc2aoUsfiLhJ1 RnKLRdOYxJsM5WCifOKCbRpY2rIIrRMY5NGWWmYtWBPJIYLEqb19L0AU2IRMBWIJ7S2R dLuUDtlxpf1aHc+77ucpFW0wxdwZC6eaYb31uqWmLFQ03MrkTTs628lU85i2+bTBcWB4 ep2g== X-Gm-Message-State: AOJu0YwkzkKba3nm3dpcPb7/PBhUXqRTuRASLsuy8aa80eG85FG4E7wD rlreM/ZM2MJlNSUJI5EVcNYOz3H4HhUMHBndcIcIhI5kEjKVLWmAbgk8ujR1 X-Google-Smtp-Source: AGHT+IHrZxK+7i3w1va7XpDFWnyNEU/iXC8ZWH9KqvfaHHRNLSykZMk9RuwgkToiYXYnh332ZLIoEw== X-Received: by 2002:a5d:54c7:0:b0:374:bf6b:1021 with SMTP id ffacd0b85a97d-379a860b862mr4999443f8f.27.1726873888680; Fri, 20 Sep 2024 16:11:28 -0700 (PDT) Received: from smtpclient.apple (dynamic-046-114-115-140.46.114.pool.telefonica.de. [46.114.115.140]) by smtp.googlemail.com with ESMTPSA id 5b1f17b1804b1-42e7afbfbfbsm34825695e9.22.2024.09.20.16.11.26 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 20 Sep 2024 16:11:27 -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 \(3776.700.51\)) Subject: Re: Rockchip RK3328 Rock64 HDMI Date: Sat, 21 Sep 2024 01:06:21 +0200 References: <5kADboXE-OUia2ncm13XjDesvDmjB3tjWSyr3ytCpa5XYof9xOrL9AbRownQoRG9eJcJpYswqjbMt0P0XiZfs7KNNfiNF7vQ93m72mm_Fyk=@protonmail.com> To: freebsd-arm@freebsd.org In-Reply-To: <5kADboXE-OUia2ncm13XjDesvDmjB3tjWSyr3ytCpa5XYof9xOrL9AbRownQoRG9eJcJpYswqjbMt0P0XiZfs7KNNfiNF7vQ93m72mm_Fyk=@protonmail.com> Message-Id: <4F94C5BF-B5D8-4EA0-8B4E-695BBC28D693@googlemail.com> X-Mailer: Apple Mail (2.3776.700.51) X-Spamd-Result: default: False [-3.36 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-0.99)[-0.994]; NEURAL_HAM_SHORT(-0.99)[-0.989]; R_MIXED_CHARSET(0.63)[subject]; DMARC_POLICY_ALLOW(-0.50)[googlemail.com,quarantine]; 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]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_LAST(0.00)[]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; RCPT_COUNT_ONE(0.00)[1]; FREEMAIL_ENVFROM(0.00)[googlemail.com]; FREEMAIL_FROM(0.00)[googlemail.com]; DKIM_TRACE(0.00)[googlemail.com:+]; RCVD_VIA_SMTP_AUTH(0.00)[]; DWL_DNSWL_NONE(0.00)[googlemail.com:dkim]; TO_DN_NONE(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; APPLE_MAILER_COMMON(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::42d:from] X-Rspamd-Queue-Id: 4X9SnG3Z9Jz41yr X-Spamd-Bar: --- 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 = 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=20 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 = : >=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 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-- From nobody Fri Sep 20 23:27:46 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 4X9T8L2cMGz5Vccf for ; Fri, 20 Sep 2024 23:28:02 +0000 (UTC) (envelope-from maciphone2@googlemail.com) Received: from mail-wm1-x330.google.com (mail-wm1-x330.google.com [IPv6:2a00:1450:4864:20::330]) (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 4X9T8L0Q4Qz44mk for ; Fri, 20 Sep 2024 23:28:02 +0000 (UTC) (envelope-from maciphone2@googlemail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-wm1-x330.google.com with SMTP id 5b1f17b1804b1-42cb57f8b41so30650925e9.0 for ; Fri, 20 Sep 2024 16:28:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20230601; t=1726874879; x=1727479679; 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=reAYT43ZXcJCBSqSVMPshV0xprBLjybcGx+QIB2tsiw=; b=FvSRHacOunjQyqGXWDHo+bBVs7a/xC9isdI2tLjF5AOzDQcn7vcnKWABh/sCyuQTC1 alcIHxpix+j+OTzZcqwa+v8KqUwzRLiUgam6Ke0rRAXi70yH69Tq58Bk+EkRzPLWK9E/ 2PMzej5VyTAEuEJ3kUha4T9FYEBoL78SPC0j3W1k1pweGEi3H/DYsKFqZ5oOww74Hp9v 2VfbPaq7dhfseKWFqk1WxBOY7Sf7WmqlG4dJXTZSI2m20w1tkFrdtr/p4OOCS2wgtI61 6TYWci0Zq2dYjooZDDW0n+T91NNcALSjoi2U51riub1mgQbOx+AerQRhasDcYYjl3MAu grnw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1726874879; x=1727479679; 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=reAYT43ZXcJCBSqSVMPshV0xprBLjybcGx+QIB2tsiw=; b=l6gUo77oIbBShb2XyKVQNNU+wzUryenNi6yyWB1ev3zqBXbzXczKTBwS474eWD1t1g ts6ZLR2f/VZnWutEjfG08s1YyI850nhDWPywxkl8FTT1b/e6ADyzjC4QAybE5KiMpnHK Olms8GEQ2kIwSzwnOwS4RuqoOjNw1BrQd73sIxLhy75fvrxzD6VCkOGJYTpdT2U+yWgA wE2W2un24Q4KKFc1m4DcXsQknhpi6Yntaw9zANlTEaj8N/16I0xyJ0jIGief13QttT6p nRpazhI6zL+X/Y6g5Vnul8iaxuTDA9wOysHapuOm0bSswO6fA9nCtTMP08kdoxz+JaOD 44Ig== X-Forwarded-Encrypted: i=1; AJvYcCVuY8RttN6nA+CXIqd2MoBq06ChuvQL4xs4/ON8mp0LB/q9bI8rw9KTz4m4ekXVzoql1oZHc5X1tH4A2w==@freebsd.org X-Gm-Message-State: AOJu0YwFOZjENBMQ0HiWvEk0+BnFNpWsw4R4wr2r3q2B+YWQ0AduqryK y/pa+yKeWcm2BHMJzHa3d7LtMFguHlmLLtDApn5MACmB1o9NhCA/ X-Google-Smtp-Source: AGHT+IHpaUEzDIKIB1pydIaN4Mz+StKXlYuO4Ofc0FXGtn7KBinsARZ1rjXy0UYt6RLhKZy7GGH9Iw== X-Received: by 2002:a05:600c:4689:b0:42c:b8c9:16b6 with SMTP id 5b1f17b1804b1-42e7abe38f9mr46290675e9.2.1726874879201; Fri, 20 Sep 2024 16:27:59 -0700 (PDT) Received: from smtpclient.apple (dynamic-046-114-115-140.46.114.pool.telefonica.de. [46.114.115.140]) by smtp.googlemail.com with ESMTPSA id 5b1f17b1804b1-42e7540e32fsm62006435e9.9.2024.09.20.16.27.57 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 20 Sep 2024 16:27:58 -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 \(3776.700.51\)) Subject: Re: Rockchip RK3328 Rock64 HDMI Date: Sat, 21 Sep 2024 01:27:46 +0200 References: <5kADboXE-OUia2ncm13XjDesvDmjB3tjWSyr3ytCpa5XYof9xOrL9AbRownQoRG9eJcJpYswqjbMt0P0XiZfs7KNNfiNF7vQ93m72mm_Fyk=@protonmail.com> <4F94C5BF-B5D8-4EA0-8B4E-695BBC28D693@googlemail.com> To: Mario Marietto , freebsd-arm@freebsd.org In-Reply-To: Message-Id: <66D3A269-3E94-4CD6-8D81-72B4ED174AB9@googlemail.com> X-Mailer: Apple Mail (2.3776.700.51) X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Queue-Id: 4X9T8L0Q4Qz44mk X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated According to https://wiki.freebsd.org/arm/RockChip it works on RockPro64 = , Cannot test it anymore since I have burnt this awful sensitive gadget = by touching it 5 years ago or so :-) > Am 21.09.2024 um 01:16 schrieb Mario Marietto = : >=20 > Hello to everyone. >=20 > Recently I've bought the RockPro64 with the RockChip RK3399,this one : >=20 > https://pine64.org/devices/rockpro64/ >=20 > 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=E2=80=A6. =E2=80=A6.= From nobody Sat Sep 21 04:47:10 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 4X9cDw2V63z5XFSj for ; Sat, 21 Sep 2024 04:47:28 +0000 (UTC) (envelope-from maciphone2@googlemail.com) Received: from mail-wm1-x32c.google.com (mail-wm1-x32c.google.com [IPv6:2a00:1450:4864:20::32c]) (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 4X9cDv6M66z42sZ for ; Sat, 21 Sep 2024 04:47:27 +0000 (UTC) (envelope-from maciphone2@googlemail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-wm1-x32c.google.com with SMTP id 5b1f17b1804b1-42cbe624c59so23045885e9.3 for ; Fri, 20 Sep 2024 21:47:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20230601; t=1726894045; x=1727498845; 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=r+ynMHoZtT4MB6Ra0ZJUXlk6D/qvXf4IxrA7VpH5l5s=; b=dCyxta4fI0Iwx7rdl+l8Csv1r4vvo8Wr7IbDEYkSWqqnC3dU8WEtroXTym2lo/6Hm6 XDSTrp2hx1IF8o6fJKKy5C/l+wdF+vEEfHXibAsvkW/nBzTvXA7jW2ehdEjAuJNvdyHw 2Jpf5B2XMtuHsUYChh62ka2Nyeg/mScMWoHY7H+ucC5zSzq7h5jTU1pzMPTPFztJUaWn EJikyCbpHs5mf800bi/fVMnf9U9dzdBYrwtfYPwRcitvS7e9M90hbfBgczniGPw6sy2Z 33RolhfSCeKP+GroNfz73L7XIrZ5QWRC0Q7zCL95CU9DLnIqoX0UZU7+JfH13q62zyv4 UlVw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1726894045; x=1727498845; 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=r+ynMHoZtT4MB6Ra0ZJUXlk6D/qvXf4IxrA7VpH5l5s=; b=baPG1mrmYf2WB2Q5goo99O5SEr17NsEQCcir/HcKvuorNUOXsGeEe0qh26I62NRniE mapbZ20Fb/PPAzJ+ZS5XZvAiXRU2Kf6HLlWZW2vHybNAYfFJFNobftCpxWm3ohnSU/4b K/ZyCz38O6LNKRr6W5xSC6TGTfx/2g5z3Gq0agCsTxCyCHMPkTaN6jy+c7cvP6S7EmRh uO6HMIILeTHQJwqYXQvhisFEPQNTBUXhLSptFTNuNnbJ1hWVmfSKqXyV3esH3Bl7d7ct VIR29rxszzFnmXwYYd5ZBVyPOQ4AvSKrmI+B4LirQaA4LYXqbKL9Tvw3UePCOfTtjPqN wqgg== X-Forwarded-Encrypted: i=1; AJvYcCX9CRG7eTkGGUXPkoCIVLoP/EMeZ1HTevnV2dnoTQsEwQyazXNcAJZUdtqhJ6EzV1hWIqt2JqovqPuZoQ==@freebsd.org X-Gm-Message-State: AOJu0YzqjJuEbBwqJVdAXOuRWijy44MCj1F9ZYnsTLXtLnuZ3sj0dfy3 pzf8gsEhBRXnBQkGVqlhvZPBaGSaapFbEeaaTGTurzGF0JiZmy7P X-Google-Smtp-Source: AGHT+IF2BaPwBcjLAcgFv2YXOzPihRFUFIEbLrg1wCqEq/KZSLwRpyPzQ13gjqQR/yfeo30b16/auA== X-Received: by 2002:adf:cd0f:0:b0:368:5b0c:7d34 with SMTP id ffacd0b85a97d-37a422781fdmr3072553f8f.22.1726894045078; Fri, 20 Sep 2024 21:47:25 -0700 (PDT) Received: from smtpclient.apple (dynamic-046-114-115-140.46.114.pool.telefonica.de. [46.114.115.140]) by smtp.googlemail.com with ESMTPSA id ffacd0b85a97d-378e78054c3sm19444680f8f.105.2024.09.20.21.47.23 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 20 Sep 2024 21:47:24 -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: Sat, 21 Sep 2024 06:47:10 +0200 References: <5kADboXE-OUia2ncm13XjDesvDmjB3tjWSyr3ytCpa5XYof9xOrL9AbRownQoRG9eJcJpYswqjbMt0P0XiZfs7KNNfiNF7vQ93m72mm_Fyk=@protonmail.com> To: Christoph Pfaller , freebsd-arm@freebsd.org In-Reply-To: <5kADboXE-OUia2ncm13XjDesvDmjB3tjWSyr3ytCpa5XYof9xOrL9AbRownQoRG9eJcJpYswqjbMt0P0XiZfs7KNNfiNF7vQ93m72mm_Fyk=@protonmail.com> Message-Id: X-Mailer: Apple Mail (2.3818.100.11.1.3) X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Queue-Id: 4X9cDv6M66z42sZ X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated > Am 21.09.2024 um 01:06 schrieb Klaus K=C3=BCchemann = : >=20 > .. > clknode_link_recalc: Attempt to use unresolved linked clock: hdmi_phy > Cannot get frequency for clk: hdmi_phy, error: 9 > =E2=80=A6 well, to be a bit more concrete: this is where the clock of hdmi_phy seems to be linked : =20 freebsd-src /sys /dev/clk/rockchip/rk3328_cru.c It seems linux(or u-boot?) have added a function to get the clock-rate = into their drivers : = https://lore.kernel.org/all/20240117075154.58747-11-jagan@amarulasolutions= .com/#Z31drivers:clk:rockchip:clk_rk3328.c So perhaps ask the author of rk3328_cru.c if such a function is missing = in the driver or what else could cause to fail to get the clock frequency Regards K. > 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 = 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 From nobody Sat Sep 21 04:47:10 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 4X9cDx0bGZz5XFQT for ; Sat, 21 Sep 2024 04:47:29 +0000 (UTC) (envelope-from maciphone2@googlemail.com) Received: from mail-wm1-x330.google.com (mail-wm1-x330.google.com [IPv6:2a00:1450:4864:20::330]) (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 4X9cDv6M7Mz42q8 for ; Sat, 21 Sep 2024 04:47:27 +0000 (UTC) (envelope-from maciphone2@googlemail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-wm1-x330.google.com with SMTP id 5b1f17b1804b1-42cd46f3a26so23061385e9.2 for ; Fri, 20 Sep 2024 21:47:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20230601; t=1726894045; x=1727498845; 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=r+ynMHoZtT4MB6Ra0ZJUXlk6D/qvXf4IxrA7VpH5l5s=; b=dCyxta4fI0Iwx7rdl+l8Csv1r4vvo8Wr7IbDEYkSWqqnC3dU8WEtroXTym2lo/6Hm6 XDSTrp2hx1IF8o6fJKKy5C/l+wdF+vEEfHXibAsvkW/nBzTvXA7jW2ehdEjAuJNvdyHw 2Jpf5B2XMtuHsUYChh62ka2Nyeg/mScMWoHY7H+ucC5zSzq7h5jTU1pzMPTPFztJUaWn EJikyCbpHs5mf800bi/fVMnf9U9dzdBYrwtfYPwRcitvS7e9M90hbfBgczniGPw6sy2Z 33RolhfSCeKP+GroNfz73L7XIrZ5QWRC0Q7zCL95CU9DLnIqoX0UZU7+JfH13q62zyv4 UlVw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1726894045; x=1727498845; 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=r+ynMHoZtT4MB6Ra0ZJUXlk6D/qvXf4IxrA7VpH5l5s=; b=vGsbBSdEG0iw/PhN1ovBQVBwM7G2xp4kQ0wp5lWEMGcQrNRt1iEo3GSEupX+yFCQGI dqjEcN86uAWAwdRIxtrnl/XmaRsuj2+5zm8CIJJcLwqqtfChsI4BwD2D89IVs0poYP74 sDe/w/0zVvUB3A2dnfFJiBRSmJHl5UqkYUj/sOKOHTQt5T+LJCU0Jr1sHnjGxytR2ByO dQj96GRb7klmGYmzw85FuHKzylY9YMwG8su2QzttF8fQ5gR8lBggRuILzmQOViVlCser 4hBDvMzGd1Pztmz1FHsFYhZ3z1UJjpRorolxQJ6gMtq1X1h1Ka+yT6smPRXuZMFyvzXJ 7jkw== X-Forwarded-Encrypted: i=1; AJvYcCWIWj2cXcsEOGsmNxxIGkxf3LshmawILCODSbBSv5WZJ2hVJULs1UqfnqMricQsqiDNEOOm5fziZoutng==@freebsd.org X-Gm-Message-State: AOJu0YzjaNjTb7dkwuq0mnAVDQu6/r6DSqcdlkmCSMRInBNAPnXUY7Wg 14Z1+EZaI9TEg/syZEeR+cGmvbjafTvG5ZY9HWxV1g6OgflVQngj X-Google-Smtp-Source: AGHT+IGa4DdI4S2VCbSCBFOxGWkzkh2PM72Km7xX/24aHMdlB0pdRrOeOSDz3BSl1B796/L+zC4NwQ== X-Received: by 2002:a05:6000:144a:b0:368:5a8c:580b with SMTP id ffacd0b85a97d-37a42278050mr3375664f8f.19.1726894044844; Fri, 20 Sep 2024 21:47:24 -0700 (PDT) Received: from smtpclient.apple (dynamic-046-114-115-140.46.114.pool.telefonica.de. [46.114.115.140]) by smtp.googlemail.com with ESMTPSA id ffacd0b85a97d-378e7800313sm19251821f8f.88.2024.09.20.21.47.22 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 20 Sep 2024 21:47:23 -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: Sat, 21 Sep 2024 06:47:10 +0200 References: <5kADboXE-OUia2ncm13XjDesvDmjB3tjWSyr3ytCpa5XYof9xOrL9AbRownQoRG9eJcJpYswqjbMt0P0XiZfs7KNNfiNF7vQ93m72mm_Fyk=@protonmail.com> To: Christoph Pfaller , freebsd-arm@freebsd.org In-Reply-To: <5kADboXE-OUia2ncm13XjDesvDmjB3tjWSyr3ytCpa5XYof9xOrL9AbRownQoRG9eJcJpYswqjbMt0P0XiZfs7KNNfiNF7vQ93m72mm_Fyk=@protonmail.com> Message-Id: X-Mailer: Apple Mail (2.3818.100.11.1.3) X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Queue-Id: 4X9cDv6M7Mz42q8 X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated > Am 21.09.2024 um 01:06 schrieb Klaus K=C3=BCchemann = : >=20 > .. > clknode_link_recalc: Attempt to use unresolved linked clock: hdmi_phy > Cannot get frequency for clk: hdmi_phy, error: 9 > =E2=80=A6 well, to be a bit more concrete: this is where the clock of hdmi_phy seems to be linked : =20 freebsd-src /sys /dev/clk/rockchip/rk3328_cru.c It seems linux(or u-boot?) have added a function to get the clock-rate = into their drivers : = https://lore.kernel.org/all/20240117075154.58747-11-jagan@amarulasolutions= .com/#Z31drivers:clk:rockchip:clk_rk3328.c So perhaps ask the author of rk3328_cru.c if such a function is missing = in the driver or what else could cause to fail to get the clock frequency Regards K. > 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 = 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 From nobody Sat Sep 21 05:46:06 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 4X9dXt4LF7z5XLMV for ; Sat, 21 Sep 2024 05:46:22 +0000 (UTC) (envelope-from maciphone2@googlemail.com) Received: from mail-wr1-x433.google.com (mail-wr1-x433.google.com [IPv6:2a00:1450:4864:20::433]) (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 4X9dXs4mzQz46xb for ; Sat, 21 Sep 2024 05:46:21 +0000 (UTC) (envelope-from maciphone2@googlemail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=googlemail.com header.s=20230601 header.b=cv08H3la; dmarc=pass (policy=quarantine) header.from=googlemail.com; spf=pass (mx1.freebsd.org: domain of maciphone2@googlemail.com designates 2a00:1450:4864:20::433 as permitted sender) smtp.mailfrom=maciphone2@googlemail.com Received: by mail-wr1-x433.google.com with SMTP id ffacd0b85a97d-374c326c638so1485952f8f.2 for ; Fri, 20 Sep 2024 22:46:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20230601; t=1726897580; x=1727502380; 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=EOXCcC2lvRG/5tZ+rIK5OtYsHS6TElVzx0jTYKVBW7c=; b=cv08H3laEWQ5pCt9JTBGAalUrHPjt37G1gmjM5X5MqCllwjEFfPV6S0XqNfdnScIbf Evmsv+lBBj9Sy38YcXql1JmZM6y4sbmq/zXTIhr2pqCscgD6UsI3V+t/4JCFp7Q1ljWO zgsAF4h1eYgK16nVaMjmikYF+fDmAfHJ3bXcTiTtyIOQBEMX4q3rh9sd9m59Yz4OCXwk Q5TZqCUa60r6zUZRUEcPxCXarVYxRDEfmFeM2VSCECvs8RxM0ed3I/W+iY7gVh+yNO0/ s5BA9NIDPUNDmIpc8OIF/taoMUOiZMttMX/LGoiICWBhI2YCKSrEEIoUFuHdZ8PYACWS 8bMw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1726897580; x=1727502380; 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=EOXCcC2lvRG/5tZ+rIK5OtYsHS6TElVzx0jTYKVBW7c=; b=T/zYqc6Uc67BVkvYW0GBbShohuKXo5A8kkhng/9NWhsigMQWwLbOw90Mhl3+ws880B Kn7NnSpNzMp1QA5jq/R4fR9+fAk9L4CHU6sJSs9GMsFS9ug+fMN0aeUMmivpKH+vviod F78750gSvZ3zLFKok59Pm5E9Sa3XsBAIOQZahrMwxuYayexWzEq6UyoVvOA3Bkjyd4kR I0L5oHlecb8TkxlA+oTItO6Io2SJ5BYscrht+YbQWkv7YPbtZC5T+XyXk0c1k9/PysL6 rnKpgMlW0aieIcEOpK0AlGV8/1LbbuG1HNGOZgGhDsjE6schsNOGIMG0wVwu1NBp22qz 30+g== X-Gm-Message-State: AOJu0YwqUQLuj63MT2iVc36SbeDTIdhUbc73KhFSFiJ4MgjlhLYecqB7 0vS8uSM4MjdFS17bN+Im6LhTWCRizlAmECbmWPoAWVGapxA92xq7bMrKCAYT X-Google-Smtp-Source: AGHT+IHUBw6nG6EWhvHITmtmIjJWdqM4lN7yBGq7jKZThzJuom80+gOwsf8fXBO56xZzzvIe87aVcQ== X-Received: by 2002:a5d:470c:0:b0:371:9121:5643 with SMTP id ffacd0b85a97d-37a42252931mr3441550f8f.12.1726897579892; Fri, 20 Sep 2024 22:46:19 -0700 (PDT) Received: from smtpclient.apple (dynamic-046-114-115-140.46.114.pool.telefonica.de. [46.114.115.140]) by smtp.googlemail.com with ESMTPSA id ffacd0b85a97d-378e78054c3sm19532620f8f.105.2024.09.20.22.46.17 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 20 Sep 2024 22:46:18 -0700 (PDT) From: =?utf-8?Q?Klaus_K=C3=BCchemann?= Content-Type: text/plain; charset=us-ascii 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: Sat, 21 Sep 2024 07:46:06 +0200 References: <5kADboXE-OUia2ncm13XjDesvDmjB3tjWSyr3ytCpa5XYof9xOrL9AbRownQoRG9eJcJpYswqjbMt0P0XiZfs7KNNfiNF7vQ93m72mm_Fyk=@protonmail.com> To: freebsd-arm@freebsd.org In-Reply-To: <5kADboXE-OUia2ncm13XjDesvDmjB3tjWSyr3ytCpa5XYof9xOrL9AbRownQoRG9eJcJpYswqjbMt0P0XiZfs7KNNfiNF7vQ93m72mm_Fyk=@protonmail.com> Message-Id: <614574A2-B696-4353-BF28-2F0535ABB141@googlemail.com> X-Mailer: Apple Mail (2.3818.100.11.1.3) X-Spamd-Result: default: False [-2.82 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.94)[-0.942]; R_MIXED_CHARSET(0.63)[subject]; DMARC_POLICY_ALLOW(-0.50)[googlemail.com,quarantine]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; R_DKIM_ALLOW(-0.20)[googlemail.com:s=20230601]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; DWL_DNSWL_NONE(0.00)[googlemail.com:dkim]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; 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_DN_NONE(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]; FREEMAIL_ENVFROM(0.00)[googlemail.com]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::433:from] X-Rspamd-Queue-Id: 4X9dXs4mzQz46xb X-Spamd-Bar: -- here`s a verbose dmesg for the case that the driver authors don`t have a = Rock64 board available : https://dmesgd.nycbug.org/index.cgi?do=3Dview&id=3D7931 From nobody Sat Sep 21 06: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 4X9g5f0XxBz5XSFy for ; Sat, 21 Sep 2024 06:56:22 +0000 (UTC) (envelope-from freebsd-arm-freebsd-org097@ketas.si.pri.ee) Received: from green.sau.si.pri.ee (d004-fea2-0bff-021e-13e8-8437-07d0-2001.dyn.estpak.ee [IPv6:2001:7d0:8437:13e8:21e:bff:fea2:d004]) (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 4X9g5d1RwMz4GB0 for ; Sat, 21 Sep 2024 06:56:20 +0000 (UTC) (envelope-from freebsd-arm-freebsd-org097@ketas.si.pri.ee) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=ketas.si.pri.ee header.s=ketas-si-pri-ee-20240416002854-4096 header.b=wIqNnNn7; dmarc=pass (policy=reject) header.from=ketas.si.pri.ee; spf=pass (mx1.freebsd.org: domain of freebsd-arm-freebsd-org097@ketas.si.pri.ee designates 2001:7d0:8437:13e8:21e:bff:fea2:d004 as permitted sender) smtp.mailfrom=freebsd-arm-freebsd-org097@ketas.si.pri.ee X-Original-To: freebsd-arm@freebsd.org DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=ketas.si.pri.ee; s=ketas-si-pri-ee-20240416002854-4096; t=1726901769; bh=Ykfiv+fQIZDewjRcowjFijTWS7JeOrY2dE7soCeNZgU=; h=Date:From:To:Subject:In-Reply-To:References; b=wIqNnNn7RoqLw0MNHU0CaBrorTSt/slfyDwiMYEX9i6qWPR/22jTJl+SrQFyqso5q w8//dr7cWpfYHKPu1/5eW6KOF5pKJp4AyJ7Z1nEUkDgkuBkplHAN5EG55Yd7bWmKY+ P/keSBT+CfHcSH6ua0m6l5XKRaNN9R1BaevIsB3aOF1iEtFffbq6/vuUURZ1LCVo1O oDRnXEBbBsfAZ0CM0n7pox4fxytkoIy/9FL/ujBo0p3nYweMrW9Y0IoIuQBV+cMosl 2wdZylZLb96cVq0l4uL1AcoHWUfuA47y0gWr87lb7Vu9rys/pAeZS9Am/eOSn4bTJW W7+R7R8bvncmP7uNPqtm8BvDbJqtd9Y7ocCRc3H8zV7z9ursRo5nD7c1LdL9pGS3YQ ffPGHYRuT1o6lYdagBzn+cf+uOgpJNfyoXChMPYuysU8hhdhIbFs2pBr2w4H5f3Khf UZxj1mTOXAYd0gYDOwbDrKvvMZgRxCCKfSI76RdjgPP0hjG6udzjPQmHRA8OzG4Nyw MYg0CoVrB6wZ3J3S5NfJaaV7Mey9dep/5UqlXBY77o+AY2L1SwkwOdjzfG9WptQQpn KEOuLSdexR7DVW586NMZ13q6xbzuWGf5R1R+/N4C/GSmhBG0V3bw+DdNsEO0aLdgfO g46U+k0urDH0ooR4PE49DfrQ= Received: from [IPv6:::1] (0114-0000-0000-0000-13c8-8437-07d0-2001.dyn.estpak.ee [IPv6:2001:7d0:8437:13c8::114]) (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) (No client certificate requested) by forestgreen.jails.green.sau.si.pri.ee (Postfix) with ESMTPSA id B673F58B4F8 for ; Sat, 21 Sep 2024 09:56:08 +0300 (EEST) Date: Sat, 21 Sep 2024 09:56:07 +0300 From: Sulev-Madis Silber To: freebsd-arm@freebsd.org Subject: Re: Beaglebone Black/Green/Blue support (volunteering) User-Agent: K-9 Mail for Android In-Reply-To: <17af25e9-2cd9-6293-deba-df1087a93640@pobox.com> References: <276f57f2-5194-cad1-d859-e49b2bce2580@pobox.com> <69E08B38-7388-46A6-8864-20074BFFF8F4@yahoo.com> <88d2cc76-f980-600e-0da4-2fa1070d76ba@pobox.com> <6b848423-bdd1-b215-889a-1f07e5064412@pobox.com> <4BEC1DC0-7528-4B4B-8FD0-254BD7BF1BD9@ketas.si.pri.ee> <7B680499-8260-4C42-97EB-248EA6AC5BC8@yahoo.com> <17af25e9-2cd9-6293-deba-df1087a93640@pobox.com> Message-ID: <9FC18546-206F-4271-B09F-E1EE64547891@ketas.si.pri.ee> 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=utf-8 Content-Transfer-Encoding: quoted-printable X-Spamd-Result: default: False [-0.86 / 15.00]; HFILTER_HOSTNAME_5(3.00)[d004-fea2-0bff-021e-13e8-8437-07d0-2001.dyn.estpak.ee]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-0.99)[-0.985]; NEURAL_HAM_SHORT(-0.98)[-0.976]; DMARC_POLICY_ALLOW(-0.50)[ketas.si.pri.ee,reject]; R_SPF_ALLOW(-0.20)[+ip6:2001:7d0:8437:1300::/56]; R_DKIM_ALLOW(-0.20)[ketas.si.pri.ee:s=ketas-si-pri-ee-20240416002854-4096]; ONCE_RECEIVED(0.10)[]; MIME_GOOD(-0.10)[text/plain]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:3249, ipnet:2001:7d0::/32, country:EE]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_ONE(0.00)[1]; RCVD_TLS_ALL(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DKIM_TRACE(0.00)[ketas.si.pri.ee:+] X-Rspamd-Queue-Id: 4X9g5d1RwMz4GB0 X-Spamd-Bar: / unsure why i gave parse errors, maybe i'm just weird, but anyway yes, i do like ti am soc that powers bb*=2E awesome io=2E i got one board = to get fbsd support better=2E it did get better=2E but i didn't get why ssh= lagged still=2E one of the issues funnily=2E why, i don't know=2E it didn'= t perform bad in other ways=2E encryption perf issues? what if i want to us= e trusted control channels like we all should nowadays i also, yeah, don't like closed nature of hw that doesn't protect them fro= m other companies, just makes more ewaste and headache=2E i don't think rep= urposing phone soc is always bad, it's the closedown=2E phones make up larg= e amount of hw=2E sadly no fbsd on phones either, with rare examples that's why i'm looking other options besides rpi and yes, i look things for remote monitoring and control=2E seems like ser= ver/desktop/nas/video out is already pushed by many others and usb wifis do work=2E less as ap, more at sta=2E with realteks being ch= eapest and worst so i don't know, i understand that h618 specs are also under nda, iirc=2E = h616 isn't iirc? but i find that area really difficult to navigate still=2E= why i look for those instead of bb* is cost=2E=2E=2E fun isn't it=2E bit l= ess of io, bit less industrial, faster, cheaper=2E i don't mean desktop/ser= ver/buildbox fast, just for headless i'm also open for suggestions on hw=2E as i don't really make hw, let alon= e ic's like what's the least expensive thing with ~10 gpios that runs full fbsd a= nd has 100m ethernet? 512m ram is enough, even 256m would be one type of hw i'm looking for is this=2E i think it fits some of your pur= poses too=2E i think in here, cheap doesn't mean shit, it just doesn't need= to "perform" the others, running on fbsd, would be nice too, eg ability to run some gui= =2E maybe xorg, firefox, js will work on some hw, tho i realize it has huge= overhead and something with a storage those are all components of usual scada systems, really i know fbsd is used in some of those places already=2E and they need to be= secure=2E i think fbsd is good here=2E even if for os diversity=2E just so= me time ago someone said that he has bbb's in high security facility and ca= n't get them replaced=2E good if fbsd made it there because if people say fbsd sucks i've never heard of fbsd is insecure, fbs= d is unstable, fbsd has bad code=2E it's always that fbsd doesn't support = hw, fbsd is slow to adapt features, fbsd is stubborn=2E now, fbsd removes h= w support=2E maybe it's price to pay for all goodness? people joke how linux is a car with safety features removed=2E runs fast, = runs everywhere, is built, even just kernel, from ton of components with un= known background=2E yes, it does work really well this way=2E hence it's us= ed! popular, attractive, works=2E even if worse, still works=2E since it "w= orks" more, it also earns more money, hence it's developed for more, used m= ore, tested more, even if something is bad=2E how sad, isn't it? that's how= i see it there's a reason why i'm with fbsd for over half of my lifetime already=2E= but i can't really make hw support any better because i guess i'm not just= that guy so yeah, i'm just wondering here what to choose if i want fbsd and tasks i= listed above=2E as a hobby but could do more here=2E but that assumes some= thing works too=2E and keeps working for 10+ years=2E because you don't thr= ow those things out, yet they still need be secure unsure what nbsd focus was, runs everywhere? how do they do it there, i ne= ver checked? it would be crazy to move to linux because that just runs a lot of hw=2E d= oesn't matter how while thinking of all this, i would still want to use fbsd on a server rea= lly well=2E so if that would mean embedded is gone, that's sad story=2E alt= ho what is a "server" nowadays, is questionable=2E maybe in future the smal= ler hw also gets x86 type standards so at least that part is solved=2E big = machines have it=2E like lpt port which works as poor gpio=2E but it works = same everywhere? ok there are issues in cpu power mgmt etc=2E as i said, th= ere are better guys than me on this so yeah, in the end, i don't know=2E some fbsd support would be nice=2E on= open hw=2E on various io/power level embedded devices=2E maybe not just ar= m=2E continued support=2E but continued by who, i don't know=2E ai? mostly = joking on this! but really=2E=2E=2E From nobody Sat Sep 21 11:05: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 4X9md00X6Tz5Vp0X for ; Sat, 21 Sep 2024 11:05:24 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-pj1-x1033.google.com (mail-pj1-x1033.google.com [IPv6:2607:f8b0:4864:20::1033]) (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 4X9mcz5k99z4kKZ for ; Sat, 21 Sep 2024 11:05:23 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pj1-x1033.google.com with SMTP id 98e67ed59e1d1-2d86f71353dso2128592a91.2 for ; Sat, 21 Sep 2024 04:05:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1726916722; x=1727521522; 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=sZVN7lzsUxbkS1SJzWnZdPFb65mSZl3C7zjaIycmk5E=; b=u0Pe0eNq0XqrToCZsHdVXq0RO1Nz/a8TqQPUMxD09nURRBdbLVrqxlUq4BiAC7s5np lcNUuubcg32q8q1p2K3+kGLrsNRFyqRDqZOqbzxjqtiMmpdAO4djOZ5TdqXWQqc+4YXV QE0keMQ1OvFLEhgi2xnZ14avYHyFEEgFeV9Oykx44WLGwSE+8Zdqx7c8jCLf9TH8cCKN Ozv4ux5D+1Ns/V+QOyB7Z/TyIgCe9wewAnkL34XN7NRRwYTtwmOQMTI9nwyt9i4nnV6O GMxsH26PSqEodOE43mfJcKU9C+zN77xcq6rQZ0RgFDmoN47jXGhZJmmLbQ9d2PUL9J6P PZ5w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1726916722; x=1727521522; 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=sZVN7lzsUxbkS1SJzWnZdPFb65mSZl3C7zjaIycmk5E=; b=X+bIOWeid7KSMd8aPDJy/nc4RytLzAMFcIcxCCR7EjJGKUNFYIsuTR177DQvvjMvSb EJqNpWHbe0LN0yYNVNjNapEqx67U0I2z1M9u8qdWLOEqnAekDOwn9tPlqMndNvjzC6o9 YanA3hZFj6HP4y4H589b1KSYorPv7v7mfuOphhnJ1rwSw7fpqaxke1Tjg05v2NKaHGr3 Q/RouC/iX+G8vggYqs3/HAA1Td7wVF6dznYpGZUa68uXlc95kKJ049l0urjprRq2WHCm HRgd7tcIOFySNhjo0EeDbPaqmBO2IRy3U9gpo2Bde+7ai9z+RAIEYyJ3gTDrJ+mB5A3M vRdg== X-Gm-Message-State: AOJu0YygGQWYf6gt/RxwiDP7G13vPDe+MNBu2UZiPeoAr8WKjPpWAVvZ OOB0GR9AIAwnlX5mQTG+Am9R4mL5oScINFOSDFULaYKPyUoknOxfDIxgeOSPC7oRpThO/lsWv5H Igi2PIhnSNbhNI1Sw4b2t01YXUqzVtKfqHGIhXQWjNita6otQAXs= X-Google-Smtp-Source: AGHT+IHnGAZW7y4gstwqBQqbo6gBokCEQNGzXhE3+39lBehj83v6PsULcm/g3ur5HvPtGUoWt6ytaCSAZEADi/7J7bA= X-Received: by 2002:a17:90b:33c4:b0:2da:8730:5683 with SMTP id 98e67ed59e1d1-2dd7f726038mr7403504a91.39.1726916722619; Sat, 21 Sep 2024 04:05:22 -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: <276f57f2-5194-cad1-d859-e49b2bce2580@pobox.com> <69E08B38-7388-46A6-8864-20074BFFF8F4@yahoo.com> <88d2cc76-f980-600e-0da4-2fa1070d76ba@pobox.com> <6b848423-bdd1-b215-889a-1f07e5064412@pobox.com> <4BEC1DC0-7528-4B4B-8FD0-254BD7BF1BD9@ketas.si.pri.ee> <7B680499-8260-4C42-97EB-248EA6AC5BC8@yahoo.com> <17af25e9-2cd9-6293-deba-df1087a93640@pobox.com> <9FC18546-206F-4271-B09F-E1EE64547891@ketas.si.pri.ee> In-Reply-To: <9FC18546-206F-4271-B09F-E1EE64547891@ketas.si.pri.ee> From: Warner Losh Date: Sat, 21 Sep 2024 12:05:11 +0100 Message-ID: Subject: Re: Beaglebone Black/Green/Blue support (volunteering) To: Sulev-Madis Silber Cc: freebsd-arm@freebsd.org Content-Type: multipart/alternative; boundary="000000000000cf0f8206229f2152" 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: 4X9mcz5k99z4kKZ X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated --000000000000cf0f8206229f2152 Content-Type: text/plain; charset="UTF-8" I talked with Oskar Holmlund (oh@freebsd.org) yesterday at EuroBSDcon... He's working on upstreaming a number of patches that his company has been running for a while now. Please contact him if you can help testing and/or fixing things. Warner --000000000000cf0f8206229f2152 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I talked with Oskar Holmlund (oh@freebsd.org) yesterday at EuroBSDcon...=C2=A0= He's working=C2=A0 on upstreaming a number of patches
th= at his company has been running for a while now.=C2=A0 Please contact him i= f you can help testing and/or fixing things.

Warne= r
--000000000000cf0f8206229f2152-- From nobody Sat Sep 21 11:20:48 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 4X9n0P6wgbz5Vppl for ; Sat, 21 Sep 2024 11:22:13 +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 4X9n0P3c8vz4n2D for ; Sat, 21 Sep 2024 11:22:13 +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=1726917725; 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=6TNkvCTZPjzCf7BpiStufG37+qBAIcnVdxF/YC2XJeI=; b=L+yE1yQAWw3PF/LHBIdCrPx4LOUwL+Z76ue3ONzn4znbP1pngzoGltXeT3jppzOQnADy0C RTU1pnNqQwfa69oQfy4IsJgxVi6VIVXjQp5DaLQvjvFcQ35V26Bj/x4f5OrojTuDqW5CKU YP6dsVVkcf/0RWbyONSnFOsBeRvcPRU= 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 90f11178 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Sat, 21 Sep 2024 11:22:05 +0000 (UTC) Date: Sat, 21 Sep 2024 13:20:48 +0200 From: Emmanuel Vadot To: Warner Losh Cc: Sulev-Madis Silber , freebsd-arm@freebsd.org Subject: Re: Beaglebone Black/Green/Blue support (volunteering) Message-Id: <20240921132048.cb54a78ee306457271a539e9@bidouilliste.com> In-Reply-To: References: <276f57f2-5194-cad1-d859-e49b2bce2580@pobox.com> <69E08B38-7388-46A6-8864-20074BFFF8F4@yahoo.com> <88d2cc76-f980-600e-0da4-2fa1070d76ba@pobox.com> <6b848423-bdd1-b215-889a-1f07e5064412@pobox.com> <4BEC1DC0-7528-4B4B-8FD0-254BD7BF1BD9@ketas.si.pri.ee> <7B680499-8260-4C42-97EB-248EA6AC5BC8@yahoo.com> <17af25e9-2cd9-6293-deba-df1087a93640@pobox.com> <9FC18546-206F-4271-B09F-E1EE64547891@ketas.si.pri.ee> 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=US-ASCII Content-Transfer-Encoding: 7bit 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: 4X9n0P3c8vz4n2D X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated On Sat, 21 Sep 2024 12:05:11 +0100 Warner Losh wrote: > I talked with Oskar Holmlund (oh@freebsd.org) yesterday at EuroBSDcon... > He's working on upstreaming a number of patches > that his company has been running for a while now. Please contact him if > you can help testing and/or fixing things. > > Warner Yes talking to Oskar is the way to go if you want BBB support with recent DTS. Note that he started to describe the status at https://wiki.freebsd.org/arm/BeagleBoneBlackMain Cheers, -- Emmanuel Vadot From nobody Sat Sep 21 11:22:29 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 4X9n283hwJz5Vq8Q for ; Sat, 21 Sep 2024 11:23:44 +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 4X9n281mh5z4nKS for ; Sat, 21 Sep 2024 11:23:44 +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=1726917822; 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=uOPL4G9Ijvy1ZdIPOOYs+fO/BCyODb7TTmNo03S25pQ=; b=Uc+TFf8uwSJtbFPI/x8RKQNCTW+WyBHRn3754T0/CDtQMfBsCjpa/VlrdobP1+PBcFUstl L1baVVAM/qm5MjSptSzIoxfBNNp30VuG1ckMwLmXtbxPLhB4UvZ5LWHiwin7o1il+iT8sS wprUxqfQTHlBVT12gp7zvVWu3Caxe1o= 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 3cd57630 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Sat, 21 Sep 2024 11:23:42 +0000 (UTC) Date: Sat, 21 Sep 2024 13:22:29 +0200 From: Emmanuel Vadot To: Christoph Pfaller Cc: "freebsd-arm@FreeBSD.org" Subject: Re: Rockchip RK3328 Rock64 HDMI Message-Id: <20240921132229.6e3ba1e1d2a257660333a361@bidouilliste.com> In-Reply-To: <5kADboXE-OUia2ncm13XjDesvDmjB3tjWSyr3ytCpa5XYof9xOrL9AbRownQoRG9eJcJpYswqjbMt0P0XiZfs7KNNfiNF7vQ93m72mm_Fyk=@protonmail.com> References: <5kADboXE-OUia2ncm13XjDesvDmjB3tjWSyr3ytCpa5XYof9xOrL9AbRownQoRG9eJcJpYswqjbMt0P0XiZfs7KNNfiNF7vQ93m72mm_Fyk=@protonmail.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=US-ASCII Content-Transfer-Encoding: 7bit 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: 4X9n281mh5z4nKS X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated Hi Christoph, On Fri, 20 Sep 2024 17:22:58 +0000 Christoph Pfaller wrote: > 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 output does not work. So I want to change that. At least efifb should work (which isn't ideal I know). > 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. We have an out of tree driver for rockchip stuff, only support rk3399 but adding rk3328 shouldn't be too hard I think. See https://github.com/evadot/drm-subtree/ > 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. > > Greetings > pf0 Cheers, -- Emmanuel Vadot From nobody Sat Sep 21 11:25:33 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 4X9n5h3cstz5W59c for ; Sat, 21 Sep 2024 11:26:48 +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 4X9n5h1GL9z4pmS for ; Sat, 21 Sep 2024 11:26:48 +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=1726918007; 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=F8xNn675z1hMAdNmVgxNdxpWDqcUl+L6HiEPm6QuchM=; b=XBapaBTd/PfOSLMoGt38eqSPKU5zYrzTWYsiHuAtCMecabswDHmO/5zofM8523c4oy3dgh Pdx/UbeCw+0da4Vyqvuzo3vYSaPHLPXUj/RMxVTOFbXq6pd44zlPoq/+ewuf1SqHs2ATVQ HAGbDe90CBNv1Ao8vIUt2tnr27qKt48= 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 88f77f46 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Sat, 21 Sep 2024 11:26:46 +0000 (UTC) Date: Sat, 21 Sep 2024 13:25:33 +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: <20240921132533.8b8cf0229a38275128ef0ccc@bidouilliste.com> In-Reply-To: <4F94C5BF-B5D8-4EA0-8B4E-695BBC28D693@googlemail.com> References: <5kADboXE-OUia2ncm13XjDesvDmjB3tjWSyr3ytCpa5XYof9xOrL9AbRownQoRG9eJcJpYswqjbMt0P0XiZfs7KNNfiNF7vQ93m72mm_Fyk=@protonmail.com> <4F94C5BF-B5D8-4EA0-8B4E-695BBC28D693@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-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: 4X9n5h1GL9z4pmS X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated Hi Klaus, On Sat, 21 Sep 2024 01:06:21 +0200 Klaus K=FCchemann wrote: > 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 https:= //dmesgd.nycbug.org) 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. > 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. Cheers, >=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 pan= ics when running the board with Linux. So far I enjoy the operating system.= However; there is one little annoyance - the integrated HDMI output does n= ot work. So I want to change that. > >=20 > > 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/m= aster/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. Accodri= ng to https://wiki.freebsd.org/arm/RockChip HDMI works for the rockchip rk3= 399 but I could not find any drivers neither in the freebsd-src or drm-kmo= d (I am new to FreeBSD so i don't know if this is even the right place to l= ook for). I hope someone with more technical knowledge about FreeBSD or HDM= I can provide me with some guidance on where I have to look and work on. > >=20 > > Greetings > > pf0 > >=20 > >=20 >=20 >=20 --=20 Emmanuel Vadot From nobody Sat Sep 21 13:49:51 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 4X9rH365zKz5Wcjw for ; Sat, 21 Sep 2024 13:50:07 +0000 (UTC) (envelope-from maciphone2@googlemail.com) Received: from mail-ej1-x634.google.com (mail-ej1-x634.google.com [IPv6:2a00:1450:4864:20::634]) (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 4X9rH2612Vz4GfB for ; Sat, 21 Sep 2024 13:50:06 +0000 (UTC) (envelope-from maciphone2@googlemail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ej1-x634.google.com with SMTP id a640c23a62f3a-a8a789c4fc5so677653666b.0 for ; Sat, 21 Sep 2024 06:50:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20230601; t=1726926605; x=1727531405; 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=6p10uAkm5NsWB31CskZbJDVMRmLGetqNIXSOS3brsCk=; b=aTw2D0egybQjWC452r91QCcWP2y72YUY4fZBVdxFB2XXCThZGNiX5PtuJW3scnZocn a6zuOnk15dK0ejPWuLY+ydkgRYgVDRyFv1fnybYhMaAoJnrVbGNpMVtHWNcPwo0zJDqv E5V8Bcj11Rc8F7981NjB7k32xqUUWwgwMpwhvHm5J+pJKelSYwD+3kpmg0vR8CZxQfd7 OKcSj2yGFxL+O/frHOIoq2OsQ6+74oNd+FYc9GA/eeo22osgKg4lp2mtiAuwDgz0/LQF YPL6VmPHRpMojBFVmRhCMmSbJ/N0dLHYI/28KKJE0ngu7vZhoyVwr8P37x0HsJk9fSO7 LEcw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1726926605; x=1727531405; 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=6p10uAkm5NsWB31CskZbJDVMRmLGetqNIXSOS3brsCk=; b=npsbZeFk9u9DrmIjSLn8ik04IRSQOaOSdeqaZz9k9IEwZSJdOu6LRqgTU4YZtMFdZ8 YTE0IlEFMN0cndvgS8pjENoSZABor6Oo06vDJ2qJbk+wcYzo1CX8pQtuDwJfpuH56Zev l07Hcf3sKVeXUSq466aBACTd1pdFoXx4VWD2sIyT4pnQuNz9jJAKX1cGMR9v3akaAjJh HJV5optSm/uGyPg3dPJUy9TLiAcnCLGZORp679CPuRNxs6GFxr96/v/kN1lQJsy4jiMp a2F2lwhiSOdFiWpIPnirhveLek3xIXmQG0J+epX8yetOleLp7n2juDTDgTGQx0qaDAq+ Ukpw== X-Forwarded-Encrypted: i=1; AJvYcCVvdjADk11xcIz+w+p+pk3fzn2gFqUePHaTwyCurm6p9ZPESv3ju/vwdmaw2ABIaZw/a1QlJxMk9T0lsQ==@freebsd.org X-Gm-Message-State: AOJu0YzFjT+B3ufWTmWLCe4LJ/hnIVfCIBJKj0dWDn69uWQA4fLtVpCS qs6hxDK9zqcOilScnVB25BfVxthd8GdewMaFJIM6NWGmzB4/NmpI X-Google-Smtp-Source: AGHT+IH5SgVpAHmi0qedntIZwJrncS+o5D09BoFZ2hNz7h2bcip57GpfLo+iNmzVGAb6SiTYBmcwng== X-Received: by 2002:a17:907:988:b0:a86:8f9b:ef6e with SMTP id a640c23a62f3a-a90d3513a5cmr604135466b.13.1726926604947; Sat, 21 Sep 2024 06:50:04 -0700 (PDT) Received: from smtpclient.apple (dynamic-046-114-115-140.46.114.pool.telefonica.de. [46.114.115.140]) by smtp.googlemail.com with ESMTPSA id a640c23a62f3a-a906132fa05sm970340866b.190.2024.09.21.06.50.02 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sat, 21 Sep 2024 06:50:03 -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: Sat, 21 Sep 2024 15:49:51 +0200 References: <5kADboXE-OUia2ncm13XjDesvDmjB3tjWSyr3ytCpa5XYof9xOrL9AbRownQoRG9eJcJpYswqjbMt0P0XiZfs7KNNfiNF7vQ93m72mm_Fyk=@protonmail.com> <4F94C5BF-B5D8-4EA0-8B4E-695BBC28D693@googlemail.com> <20240921132533.8b8cf0229a38275128ef0ccc@bidouilliste.com> To: Emmanuel Vadot , freebsd-arm@freebsd.org In-Reply-To: <20240921132533.8b8cf0229a38275128ef0ccc@bidouilliste.com> Message-Id: X-Mailer: Apple Mail (2.3818.100.11.1.3) X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Queue-Id: 4X9rH2612Vz4GfB X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated 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 : >=20 >=20 > Hi Klaus, >=20 > On Sat, 21 Sep 2024 01:06:21 +0200 > Klaus K=C3=BCchemann 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 = 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 = : >>>=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 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 From nobody Sat Sep 21 18:51:04 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 4X9yyc1Q9pz5X8gh for ; Sat, 21 Sep 2024 18:51:20 +0000 (UTC) (envelope-from maciphone2@googlemail.com) Received: from mail-ej1-x636.google.com (mail-ej1-x636.google.com [IPv6:2a00:1450:4864:20::636]) (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 4X9yyb6B4tz4Dm0 for ; Sat, 21 Sep 2024 18:51:19 +0000 (UTC) (envelope-from maciphone2@googlemail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ej1-x636.google.com with SMTP id a640c23a62f3a-a90188ae58eso369684666b.1 for ; Sat, 21 Sep 2024 11:51:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20230601; t=1726944678; x=1727549478; 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=FvHgUUnjoYg11bptfjNqz5jaxxjjLo0gHsdYmgeUERE=; b=aeasV1n8ebvE76yHSeIIY1KNa76eyLHl/ccfZp1uTPeO1mehY8VAAx35zKY9ooeZeN RsEHa258SlnXtY7xzX8GB+makHKvztnEicq7AW183gPKzCb9ugiDZD1wo6iA86sbs3+E vyUTZbBYrC060waz0nrFLgCnK3UgOH6W1EO1zVAW8zEw7DxY1t7rrdsXBDzdu6lRHsD9 GPoTDsXKQLmatA7QOp//fKjENJ5h5Ssd7iJr+9T24m96aQniGvkpu0aiqIHGCkDc09sk P68NZ5+N4h1QlUrqhP12fa5FCCwRdnAjx4Cz9q3cPsnOc0YLGKFFzWqghAat2Jwes1f0 nW7A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1726944678; x=1727549478; 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=FvHgUUnjoYg11bptfjNqz5jaxxjjLo0gHsdYmgeUERE=; b=LRpAHwdXm/jjnjMPpebJLOe12IYwc2VNy/Ww/Ti0bQsMNu/qohEKdcFWfJcjoXldId f8KYOWF94BMGbQeWj9kyePAdzHthOuS8Oc6XLt9Tph+1RcldQ0R957JUfzJ8Geefmwrr gJJQhlnysy6FXSwfmBu+oKWA2LGKi3B5crqY1djepRvx9vK5/UuwGcbiic8iHsfnqGZ1 XH9kKfVG84BHgf2xYczHJetW4hXa5yVvQf70K78znUzpPb5HtJs7Xc50hk3IvUAYBezB G7vpaL8PYQNu0+WDrSeORkE8mQNndoBmsagcYK8j89nxG5+MnxfgmwAf+LN3kWUm8kBx I3Mg== X-Forwarded-Encrypted: i=1; AJvYcCW18LYDQl89orGPf8vuifwhQsV9dw/jfJOpwB1ivf5QgUs4YcHv5z03U841EI01GzZUirWQLBnppJENdA==@freebsd.org X-Gm-Message-State: AOJu0YzJKOTnu5pjzjai8RJL8/hE71c9tDQsCPx3mwHh9NTn/qIeFgas kO6J+g1QTYQ3ML+ZaW8TEwysx3hJvElEVfA9cy5m2NSGzHVMrOKM X-Google-Smtp-Source: AGHT+IEzLXRWP9LqAetgjGpRdRPbgs9Y20560rscBTOe7F1Xc80LuDjRf4iBfQ3U5IJ68e8QMwbgMw== X-Received: by 2002:a17:907:98a:b0:a8d:5d28:8e07 with SMTP id a640c23a62f3a-a90d59292f6mr638764266b.42.1726944677758; Sat, 21 Sep 2024 11:51:17 -0700 (PDT) Received: from smtpclient.apple (dynamic-046-114-115-140.46.114.pool.telefonica.de. [46.114.115.140]) by smtp.googlemail.com with ESMTPSA id a640c23a62f3a-a90612b33d9sm990838066b.114.2024.09.21.11.51.15 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sat, 21 Sep 2024 11:51:16 -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: Sat, 21 Sep 2024 20:51:04 +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 , Mark Millard , pfaller@protonmail.com, freebsd-arm@freebsd.org In-Reply-To: <20240921193608.d88ec27b1da889a52c1f6e3e@bidouilliste.com> Message-Id: <6B056224-6771-42B9-B9FF-1A64E54F9D35@googlemail.com> X-Mailer: Apple Mail (2.3818.100.11.1.3) X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Queue-Id: 4X9yyb6B4tz4Dm0 X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated thanks for the clarification, Manu, ..that`s what I=E2=80=99d expected.=20 Now it`s clear for the first where to begin to get efifb working at = first. After removing the dust I can read a shiny Rock64 V2.0 on the board :-) If anybody of you has ever seen any HDMI-output on RK3328 with FreeBSD`s = fdt/u-boot setup , it would help to tell the (u-boot/fdt-and = board-)versions.`hope I=E2=80=99ll find some years old u-boot-hacks for = this board in my dustbin :-) Thx=20 Regards K.=20 > 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 ? >=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 = 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. >=20 >> 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=C3=BCchemann 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 = 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 = : >>>>>=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 >>=20 >>=20 >>=20 >=20 >=20 > --=20 > Emmanuel Vadot From nobody Sun Sep 22 21:00:19 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 4XBdn06FYNz5Wm8f for ; Sun, 22 Sep 2024 21:00:20 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (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-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XBdn02jLNz49Fj for ; Sun, 22 Sep 2024 21:00:20 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1727038820; a=rsa-sha256; cv=none; b=BqtryooshFeTWJZvt9vcPrP2APDnzNFKaCIYW35utDsE+n2NHn4yV3J3Ux6eOtqOSEwkBK dsPaZ+ck/gfT1Xy+MhBaB+Fc13ZcPh0x9TUtGl3FepH8xvnk8RxEOW6Y5JPLDNpKXfLoGN olDl44RWe5VrME3rqr55e11LmLR1+MG6XXaDiEsTLpUonvqx2z2J7C1axp70uG1pa9OMpm 7WJ8yPY1bPefDW9+rGAtKtAN11/2ZGBFqxfPrL+Ba+Z0oQxZcjTh4q4G2lCEr/rsuid2s4 mnu9O//1kDHMLOjAZCigRlZJkStxKfxblfl2znXPEzsH/bc5GS5/eMEnhcjoSA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1727038820; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=MhJD0yYQzR/nvOtpiwNdKXsJc+Un+l8blQxy9MUItzo=; b=bkZxIuWLfqKRoRmhLdc+xX1l/Gy5mKJ29VKcyuQ2+Ycj2WQGspZCiLaLqJOizc8p5e6Chv 595hETrdO8qQY3eyvRQvGarTTXhPRR3aFSZAuMvCf4CGZ3XBy29KUSyenPABpCz/DGH39x oQPumpb2jt3aIFhtBJQQKTEN9/zPgYRigioSBZySayswQuB9ci6L/neCLSngeMkppI6JmF t0MsFM4KaluVzX3cXg9gs7Cy+mzDWWBpfv3G9O8QhlaOJ9d7ktewQvrEZ3VyqTQyblAN4M b06azeDjmvyfiDpMsRf39kYXSqfYQGD+dBHt9E79hFk665Exdg8tCF6Vc874Xg== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (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 mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4XBdn00bFQzH4C for ; Sun, 22 Sep 2024 21:00:20 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 48ML0Jfk050301 for ; Sun, 22 Sep 2024 21:00:19 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 48ML0JFQ050300 for freebsd-arm@FreeBSD.org; Sun, 22 Sep 2024 21:00:19 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <202409222100.48ML0JFQ050300@kenobi.freebsd.org> X-Authentication-Warning: kenobi.freebsd.org: bugzilla set sender to bugzilla-noreply@FreeBSD.org using -f From: bugzilla-noreply@FreeBSD.org To: freebsd-arm@FreeBSD.org Subject: Problem reports for freebsd-arm@FreeBSD.org that need special attention Date: Sun, 22 Sep 2024 21:00:19 +0000 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: multipart/alternative; boundary="17270388191.9Bf6200ef.47719" Content-Transfer-Encoding: 7bit --17270388191.9Bf6200ef.47719 Date: Sun, 22 Sep 2024 21:00:19 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- Open | 264574 | sdhci(4): Support ACPI attachment in BCM2835_sdhc 1 problems total for which you should take action. --17270388191.9Bf6200ef.47719 Date: Sun, 22 Sep 2024 21:00:19 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" 
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.

Status      |    Bug Id | Description
------------+-----------+---------------------------------------------------
Open        |    264574 | sdhci(4): Support ACPI attachment in BCM2835_sdhc

1 problems total for which you should take action.
--17270388191.9Bf6200ef.47719--