From nobody Sat Aug 12 03:29:38 2023 X-Original-To: freebsd-current@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 4RN5kZ3LtXz4qCrL for ; Sat, 12 Aug 2023 03:29:42 +0000 (UTC) (envelope-from madis555@gmail.com) Received: from mail-pj1-x102d.google.com (mail-pj1-x102d.google.com [IPv6:2607:f8b0:4864:20::102d]) (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 "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4RN5kX6gPwz3DvP; Sat, 12 Aug 2023 03:29:40 +0000 (UTC) (envelope-from madis555@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20221208 header.b=nwLwSw7r; spf=pass (mx1.freebsd.org: domain of madis555@gmail.com designates 2607:f8b0:4864:20::102d as permitted sender) smtp.mailfrom=madis555@gmail.com; dmarc=fail reason="SPF not aligned (relaxed), DKIM not aligned (relaxed)" header.from=hot.ee (policy=reject) Received: by mail-pj1-x102d.google.com with SMTP id 98e67ed59e1d1-26871992645so1786102a91.0; Fri, 11 Aug 2023 20:29:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1691810979; x=1692415779; h=cc:to:subject:message-id:date:from:references:in-reply-to:sender :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=ra8KDOIr+kVv7iKcrp8dKRSiEKL1AUr+wdL5Oujv5i0=; b=nwLwSw7rEdDrrW73v4Wrqpg/svRXz+6NAvKkc4I2rBceNRi0bjdPpQ5ow1jGG4wcTD bNQ2kd06vfHAa5aTL1RuyDOJCdYcXalfp/TSHG+GZc9XR2xqCFHkfWi8peY+rDGf9A2o Jpyz5Yu54r3pi7NIBizfmc4pCVjvrYPiVTlLSSeEvs/KsGr8TOuyzEi53jHQ3ViXBvhf JtjTCsMHArqRZ81fszO3mmPnPFhI5uSmis2Nw19cOE8g3d2K5r4l/gSuZuhjU2g1xn+h HKNY2LFfeD1dJrsv5X7FMkv/C3aVXo1gDRwfLcREUQBGYB/L5wXYKQLazJNd6FNODEts F/0w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1691810979; x=1692415779; h=cc:to:subject:message-id:date:from:references:in-reply-to:sender :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=ra8KDOIr+kVv7iKcrp8dKRSiEKL1AUr+wdL5Oujv5i0=; b=ROhyQ+Nru3byvB3XncwjuJJA5qYULqca6e7PamF3cFbeJEqU1nbYsB6279n+SgjRPX DLajoxUW6dHtbP+237DEm3fSwUgj3fzpP4rxISN2kfVdywhu7DFagrRe+EY6LLl6SOjX 83MX8UgZy10Yjro/UJ60bcuZAzqEuOL5Qh5Zm2JVYbwM8q34kde7oDjleBm66+ZaLLg7 3WuSVDCxT5Oq1MGRavG0grI0yHmrbkAHs5jnil86wwPzd3gTCMYxZ/Bqmdvuus70jkbQ HZbUUQ0UZE+0vfGBydGn3DRuWikgC6OoxaAk/VKd6MpzTombO5KsZXTWhijnSvhHbmeO RDZw== X-Gm-Message-State: AOJu0YxACYO8C0dJi1TpK5aAtcKE2TJ6bZj+HoOtmuLFlt89qMcMKem7 6d0IE85szctEF8tAayQammUdzmfRkrfCCV9PnaA= X-Google-Smtp-Source: AGHT+IGCFzvzNP823L923tIO6H6kCtVtsiVmL+oOcDqKk+9ovpToI0h2CnwWzoinbgDBqOPGyccyAvaJsadoCYtEUVI= X-Received: by 2002:a17:90a:294e:b0:263:9816:fe0f with SMTP id x14-20020a17090a294e00b002639816fe0fmr3179720pjf.15.1691810978828; Fri, 11 Aug 2023 20:29:38 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Received: by 2002:ac4:ac8a:0:b0:624:beb4:2d with HTTP; Fri, 11 Aug 2023 20:29:38 -0700 (PDT) In-Reply-To: <95f063b3-e122-cfa8-f9fd-9ca2365d663e@fork.id.au> References: <1a77457f-319a-1025-f969-3c294dcc7432@fork.id.au> <95f063b3-e122-cfa8-f9fd-9ca2365d663e@fork.id.au> From: Sulev-Madis Silber Date: Sat, 12 Aug 2023 06:29:38 +0300 X-Google-Sender-Auth: eRWtuKU5UcnGjpCCEkzboZ4q2so Message-ID: Subject: Re: The future for support of BeagleBone Black and its variants To: George Abdelmalik Cc: David Chisnall , FreeBSD Current Content-Type: multipart/alternative; boundary="0000000000006b9ac50602b1702c" X-Spamd-Result: default: False [-1.20 / 15.00]; DMARC_POLICY_REJECT(2.00)[hot.ee : SPF not aligned (relaxed), DKIM not aligned (relaxed),reject]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.996]; FORGED_SENDER(0.30)[madis555@hot.ee,madis555@gmail.com]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20221208]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; RCVD_TLS_LAST(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::102d:from]; TO_DN_ALL(0.00)[]; FROM_NEQ_ENVFROM(0.00)[madis555@hot.ee,madis555@gmail.com]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FREEMAIL_FROM(0.00)[hot.ee]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim] X-Spamd-Bar: - X-Rspamd-Queue-Id: 4RN5kX6gPwz3DvP --0000000000006b9ac50602b1702c Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable i wonder what's the latest point in repository that DOES work? my bbb runs current from year 2014, it does run well and off emmc. it's awfully crap compared to my h3 but i would still like to have something on it. when i started working with embedded hw again, i took that out of box too, expected to seamlessly run latest current on that still, only to found out that doesn't work... On Thursday, August 10, 2023, George Abdelmalik wrote: > Hi David, > > The problems are kernel related. If I understand correctly it's in the area of clock definitions I think but I've not properly studied the patches= . > > DTC is good. > > Regards, > George. > > > On 10/8/23 14:52, David Chisnall wrote: >> >> Hi, >> >> What are the changes to the DTS files? If there are problems with DTC handling the new files, please can you raise issues here: https://github.com/davidchisnall/dtc/issues >> >> If there are problems with the kernel=E2=80=99s handling of the dtb, ple= ase ignore me. >> >> David >> >>> On 10 Aug 2023, at 13:24, George Abdelmalik wrote: >>> >>> =EF=BB=BFHi all, >>> >>> For a long while now CURRENT has not been working on the BBB due to incompatible upstream changes in vendor DTS files. I know there are some patches available which at least get FreeBSD running but those have yet to be incorporated into the project's repository. >>> >>> This leaves me with the feeling that BBB support in FreeBSD is on the path to being dropped. Is there someone from the FreeBSD project that could speak directly to this? >>> >>> As a user it would be helpful to know if I should be searching of an alternate SBC platform or another OS for my projects. >>> >>> If it still remains the plan to keep supporting BBB into 14.0 and beyond then I'd like to know what work is missing to make that happen. I'm willing and able to help. >>> >>> Regards, >>> George. >>> >>> >>> > > --0000000000006b9ac50602b1702c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable i wonder what's the latest point in repository that DOES work? my bbb r= uns current from year 2014, it does run well and off emmc. it's awfully= crap compared to my h3 but i would still like to have something on it. whe= n i started working with embedded hw again, i took that out of box too, exp= ected to seamlessly run latest current on that still, only to found out tha= t doesn't work...

On Thursday, August 10, 2023, George Abdelmali= k <george@fork.id.au> wrote:=
> Hi David,
>
> The problems are kernel related. If I un= derstand correctly it's in the area of clock definitions I think but I&= #39;ve not properly studied the patches.
>
> DTC is good.
&g= t;
> Regards,
> George.
>
>
> On 10/8/23 14:5= 2, David Chisnall wrote:
>>
>> Hi,
>>
>>= ; What are the changes to the DTS files? If there are problems with DTC han= dling the new files, please can you raise issues here: https://github.com/davidchisnall/dtc/is= sues
>>
>> If there are problems with the kernel=E2= =80=99s handling of the dtb, please ignore me.
>>
>> Davi= d
>>
>>> On 10 Aug 2023, at 13:24, George Abdelmalik &= lt;george@fork.id.au> wrote:>>>
>>> =EF=BB=BFHi all,
>>>
>>&= gt; For a long while now CURRENT has not been working on the BBB due to inc= ompatible upstream changes in vendor DTS files. I know there are some patch= es available which at least get FreeBSD running but those have yet to be in= corporated into the project's repository.
>>>
>>&g= t; This leaves me with the feeling that BBB support in FreeBSD is on the pa= th to being dropped. Is there someone from the FreeBSD project that could s= peak directly to this?
>>>
>>> As a user it would b= e helpful to know if I should be searching of an alternate SBC platform or = another OS for my projects.
>>>
>>> If it still rem= ains the plan to keep supporting BBB into 14.0 and beyond then I'd like= to know what work is missing to make that happen. I'm willing and able= to help.
>>>
>>> Regards,
>>> George.<= br>>>>
>>>
>>>
>
> --0000000000006b9ac50602b1702c--