From nobody Wed Dec 14 16:10:29 2022 X-Original-To: freebsd-arch@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 4NXL1s4JcFz4jj7m for ; Wed, 14 Dec 2022 16:10:41 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ej1-x629.google.com (mail-ej1-x629.google.com [IPv6:2a00:1450:4864:20::629]) (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 4NXL1s2Y1xz3FPJ for ; Wed, 14 Dec 2022 16:10:41 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ej1-x629.google.com with SMTP id vv4so45701416ejc.2 for ; Wed, 14 Dec 2022 08:10:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20210112.gappssmtp.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=e1gI76ZClw7btF/eW7ecgTIi0Ga/zVsfXcqD4TpkZ9w=; b=na6DJO3sQ/yY8eFyWQ+z099iEHcfNqiHdJuXq2rvGURN8IDYBzYtUFY/pUs5QMTEEy mLyDi1KRL5ps5HCjitUUGwQ+i7CZ9a7XNY7RSHsk0Y/5ydzty40FSNsT0i0nTmZaEU0C Z51xS4aV9AxYu2jWFX3EZznFI1DUadmxKVPDPdRWzqC9DsgEXL1JNdQFB6VEkWvV3nP2 zesZWGdVS3XbH5vlVyJ5g28DZFdc7KmUt3BGvGGRaaGR9K/dLTIJph+G1TPEPD+HTjkd XfFWlxMsO9BWl0uDseVXvUj9CtbF6Qg4rBRg1bwfNwQWXsFguRL2CCECNwpK4nHsKU8p Os7w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; 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=e1gI76ZClw7btF/eW7ecgTIi0Ga/zVsfXcqD4TpkZ9w=; b=sbGdw5t3Dd/8tfty2pdX1bFVzrmUKSK0JQ9l7uffb17wMJVvkaItSsl89sBA8yjb9S 1OR17PHZ8e5dXCBksxDINGQ4PZDseEWCVZL1YXxo8vWULM5jbkJag9qEzr+ws0fgmX42 o2Ql4TTHxUWr4fDt90qCDlXx/jDJl6XsQ3GkQA+9oeni7ZHjMHFQtlXhC23dvlsinUp9 VvWelbKKnMJ3DVSbAdYrmxWmZ7VzcSLZTTt+ieedJH86yf72sDtpVwmgI+48Jdmr8lU1 al6ymGDfpE+SdM8WAjPKlUeiwwaLYrQJk08QlvLZKpFh/HQwGV2OifMvdrSgUhLHoWCk L88w== X-Gm-Message-State: ANoB5pljyNVJ0oJ6Z4CzPik9Vpfs9+Bs+Ll+AQnWgtJfIdTRnMrUE0yZ +1gMGUFbJysSuEwGEiwi2u6/sHJipqdsgcief4N0aPkwYEQepw== X-Google-Smtp-Source: AA0mqf4iZSEva2RQ3T7IB2a7aZjtg36mDqgTGYBev8tT/NmkxutpOdEiPRKfKA8/ivNhkSA/ciNDEmpHVOFCoBpqkJQ= X-Received: by 2002:a17:907:98ed:b0:7c0:e7a6:cd2d with SMTP id ke13-20020a17090798ed00b007c0e7a6cd2dmr16294365ejc.317.1671034240068; Wed, 14 Dec 2022 08:10:40 -0800 (PST) List-Id: Discussion related to FreeBSD architecture List-Archive: https://lists.freebsd.org/archives/freebsd-arch List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arch@freebsd.org MIME-Version: 1.0 References: <202212140222.2BE2MAoG074349@fire.js.berklix.net> In-Reply-To: From: Warner Losh Date: Wed, 14 Dec 2022 09:10:29 -0700 Message-ID: Subject: Re: FreeBSD 14: Poll armv6 deprecated or removed To: Ed Maste Cc: "Julian H. Stacey" , freebsd-arch Content-Type: multipart/alternative; boundary="0000000000004985d205efcbfa3c" X-Rspamd-Queue-Id: 4NXL1s2Y1xz3FPJ X-Spamd-Bar: ---- 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-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --0000000000004985d205efcbfa3c Content-Type: text/plain; charset="UTF-8" On Wed, Dec 14, 2022 at 8:50 AM Ed Maste wrote: > On Tue, 13 Dec 2022 at 21:22, Julian H. Stacey wrote: > > > > Extending wordings associated with each Pi dd image, would be very > > welcome, to specificaly list all hardware version of a Pi each image > > of v6, v7, aarch64, the image should boot. > > > > As a newbie to Raspberry Pi (but not FreeBSD) I have long been confused > > which image is for which version of Pi hardware. > > The Raspberry Pi model naming convention is indeed confusing. The > armv6 Raspberry Pis are those with the BCM2835 SoC. These are the > original Raspberry Pi (A, B, A+, B+) and the Raspberry Pi Zero > (including W variants, except 2 W). These are all the ones that would > be desupported after FreeBSD 14 in Warner's proposal. > Yes. The original Raspberry models are hard to come by in volume these days, at least relative to the later ones. Even the RPi 2's are hard to find, relatively speaking. Sure, you can find them in the after market and on ebay, but they haven't shipped in volume from Raspberry in years. The Zero and ZeroW are more available, but have always been poorly supported since we don't support any networking on them that's not a USB add-on device. There are a number of follow-on products from both Raspberry and others that fit the niche of the original Zero and ZeroW. > Raspberry Pi 2 uses armv7 images. You can use aarch64 images on 3, 4 and > Zero 2. > The RPi 2 1.1 and earlier uses armv7 images, but the 1.2 and later can use aarch64 images. Modulo missing dtb files, you can also boot the armv7 images on later rpi if you want / need to. I've not tried it lately, but have done it accidentally a few times over the years on the RPi 3's that I often confused with my RPi 2's when I'm not paying close attention... I don't think it's an officially supported and tested configuration (though the best way to find out is to make an absolute statement like this in public). Warner --0000000000004985d205efcbfa3c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Wed, Dec 14, 2022 at 8:50 AM Ed Ma= ste <emaste@freebsd.org> wr= ote:
On Tue, 13 = Dec 2022 at 21:22, Julian H. Stacey <jhs@berklix.com> wrote:
>
> Extending wordings associated with each Pi dd image, would be very
> welcome, to specificaly list all hardware version of a Pi each image > of v6, v7, aarch64, the image should boot.
>
> As a newbie to Raspberry Pi (but not FreeBSD) I have long been confuse= d
> which image is for which version of Pi hardware.

The Raspberry Pi model naming convention is indeed confusing. The
armv6 Raspberry Pis are those with the BCM2835 SoC. These are the
original Raspberry Pi (A, B, A+, B+) and the Raspberry Pi Zero
(including W variants, except 2 W). These are all the ones that would
be desupported after FreeBSD 14 in Warner's proposal.
<= div>
Yes. The original Raspberry models are hard to come by i= n volume these days,
at least relative to the later ones. Even th= e RPi 2's are hard to find, relatively speaking.
Sure, you ca= n find them in the after market and on ebay, but they haven't shipped
in volume from Raspberry in years. The Zero and ZeroW are more ava= ilable, but have
always been poorly supported since we don't = support any networking on them that's
not a USB add-on device= . There are a number of follow-on products from both
Raspberry an= d others that fit the niche of the original Zero and ZeroW.
=C2= =A0
Raspberry Pi 2 uses armv7 images. You can use aarch64 images on 3, 4 and Ze= ro 2.

The RPi 2 1.1 and earlier uses ar= mv7 images, but the 1.2 and later can use aarch64 images.
Modulo = missing dtb files, you can also boot the armv7 images on later rpi if you w= ant / need to.
I've not tried it lately, but have done it acc= identally a few times over the years on the RPi 3's that
I of= ten confused with my RPi 2's when I'm not paying close attention...= I don't think it's an officially
supported and tested co= nfiguration (though the best way to find out is to make an absolute
statement like this in public).

Warner
--0000000000004985d205efcbfa3c--