From nobody Wed Jan 10 15:45: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 4T9Bvl5NtGz57CTZ for ; Wed, 10 Jan 2024 15:45:23 +0000 (UTC) (envelope-from dfr@rabson.org) Received: from mail-yw1-x1132.google.com (mail-yw1-x1132.google.com [IPv6:2607:f8b0:4864:20::1132]) (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 4T9Bvk3t8Sz52pZ for ; Wed, 10 Jan 2024 15:45:22 +0000 (UTC) (envelope-from dfr@rabson.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=rabson-org.20230601.gappssmtp.com header.s=20230601 header.b=VZgpacr5; dmarc=none; spf=pass (mx1.freebsd.org: domain of dfr@rabson.org designates 2607:f8b0:4864:20::1132 as permitted sender) smtp.mailfrom=dfr@rabson.org Received: by mail-yw1-x1132.google.com with SMTP id 00721157ae682-5f07f9d57b9so40664137b3.1 for ; Wed, 10 Jan 2024 07:45:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rabson-org.20230601.gappssmtp.com; s=20230601; t=1704901521; x=1705506321; 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=t3tpLxv0tNCbnosVuAHf1mkIbN/DOy7n3x8uB4xxhWk=; b=VZgpacr5D2v278cVWZ7oR1bNR7yOCgji+R6aD38ekUNznJhEV0/YEIufsI2v0cfNha wxxMuUzLvnI8TpuqiSefwaqqLlvErtzvL/vIKA4TPxAufKvWmg2DR09acMsG+iVkm2Bo 0MIQJx08ZRDFTKdx4BVTtfmZiM3cS1T/RuMWnvgG3bk8npvCYpO+ZDxDdSb4qhDk4Jnf htT5IMIvOtMij1NOkOM6LcCo212vKYjDAk/Pr+gXlPcfrvhQMcqGJYZjVuQllb0vfuBr MF9w4BgtJteKSGSooLZxUOHzC8JVPCwol2B2XB/rGkscrQXH8J7Io50ElXtMppabWAEd LYIA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1704901521; x=1705506321; 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=t3tpLxv0tNCbnosVuAHf1mkIbN/DOy7n3x8uB4xxhWk=; b=o0jGhwuYozoIBhBz88MLCyRNjR7ZUwAKPmJJT5Rp3UJe4cuwXhrfrWc83I23A6PJpf S//KDV8+y7iJH+IF3hZP0gUzEYB/J8Vo/chbCMCtyj3JCaQ5rQGINnry1l8C10x7tBlx zw3SaQ2Vi84vgI+XIvFXlsZ0uKRVLLqq3F5JPy20EMkhtCJnwYE/a9OdaSGYjl1/Pls4 aHExoIcdqcoyOWErHdo6fPdNBlo8FUF7fHozI/9LHTAr31xXCQp+jBW14NZw127vv4Mk TVh1BzvqrJdremk+i+KTB6Y8TZyLVsJJdKXR5vEvwTjp7qaUlJ5Cma3EAj+2F3Doc4sV 3Rbg== X-Gm-Message-State: AOJu0Yx1TBxI2zAG9Ba3pA7mggjSXLSQgLeqLFbZ3+Q2YlA4ifeWplqY lJWGwKVmgV7QRMxRfuETSnjxAAUL1It59tp2bcbCH83Sn5Mjlg== X-Google-Smtp-Source: AGHT+IGt68d9fMvjokbwwSd+bYDElVIercI5OGyqJN83ORAolAP4rPB+wDYFCuMzSZtJJxQTzVjZpDXPvKfiwP0eIW8= X-Received: by 2002:a0d:f743:0:b0:5de:a261:9074 with SMTP id h64-20020a0df743000000b005dea2619074mr1287359ywf.7.1704901521325; Wed, 10 Jan 2024 07:45:21 -0800 (PST) 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: <5a39810c-5fd8-4969-a222-2561b050b035@FreeBSD.org> In-Reply-To: <5a39810c-5fd8-4969-a222-2561b050b035@FreeBSD.org> From: Doug Rabson Date: Wed, 10 Jan 2024 15:45:11 +0000 Message-ID: Subject: Re: When will FreeBSD support RPI5? To: Jesper Schmitz Mouridsen Cc: John Kennedy , ykla , FreeBSD ARM List Content-Type: multipart/alternative; boundary="0000000000008e522c060e995121" X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.50 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[rabson-org.20230601.gappssmtp.com:s=20230601]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; ARC_NA(0.00)[]; FREEFALL_USER(0.00)[dfr]; RCVD_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; MISSING_XM_UA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::1132:from]; RCVD_TLS_LAST(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; FREEMAIL_CC(0.00)[phouka.net,gmail.com,freebsd.org]; DMARC_NA(0.00)[rabson.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; DKIM_TRACE(0.00)[rabson-org.20230601.gappssmtp.com:+] X-Rspamd-Queue-Id: 4T9Bvk3t8Sz52pZ --0000000000008e522c060e995121 Content-Type: text/plain; charset="UTF-8" I was able to boot FreeBSD-14.0 on an rpi5 using EDK2 from https://github.com/worproject/rpi5-uefi. I put the EDK2 firmware on an SD card and an aarch64 memstick image on a USB thumb drive and was able to boot all the way into the installer. PCI express is missing as well as ethernet but it's a really promising start. Doug. On Wed, 3 Jan 2024 at 15:10, Jesper Schmitz Mouridsen wrote: > > On 31.12.2023 20.37, John Kennedy wrote: > > On Fri, Dec 29, 2023 at 06:05:25PM +0100, Jesper Schmitz Mouridsen wrote: > >> On 29.12.2023 05.55, ykla wrote: > >>> Hi, When will FreeBSD support RPI5 > >> https://forums.freebsd.org/threads/raspberry-pi-5-status.91406/ > > Having ordered my RPI5 ~11/28, I think it has a shipping guesstimate > in late > > Jan/early Feb. It looks like someone is working on uboot, which FreeBSD > seems > > to favor (I think the argument I retained was "it works for lots of > things, > > piggyback on those efforts rather than have some RPI-unique thing). > Then once > > you start getting things properly enumerated to where you can load the > kernel, > > then you work on the kernel drivers. > > > > RPI seems to favor linux support first, and I suspect that there is a > fair > > amount of GPL issues that you might have to worry about creeping into > the BSD > > kernel. So not as simple as reimplement from what you see in linux. I > know > > there are a lot of strong opinions on video drivers, for example, but > for that > > to even ben an option it'd have to be something that could be a module > that > > could be packaged outside of the BSD base. I only bring that up because > I've > > had garbage luck trying to get serial consoles to work properly on RPIs > when > > they're competing for things like cooling fans and such, so graphics > console > > is nice, even if it is just very basic. > > > > How have people been chicken-n-egging the initial setup? I know > there have > > been uboot issues in the past. Seems like you basically have to build > memstick > > style images and see if they boot. Is there a bhyve/QEMU setup that is a > > generic test setup that is used? > > I just built a patched u-boot and uses a stock rpi img snapshot, then > cross build and move the kernel to the rpi sd card.. > > no qemu emulates all the phys. hw in the rpi5.. > > > --0000000000008e522c060e995121 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I was able to boot FreeBSD-14.0 on an rpi5 using EDK2 from= =C2=A0https://github.co= m/worproject/rpi5-uefi. I put the EDK2 firmware on an SD card and an aa= rch64 memstick image on a USB thumb drive and was able to boot all the way = into the installer. PCI express is missing as well as ethernet but it's= a really promising start.

Doug.


On = Wed, 3 Jan 2024 at 15:10, Jesper Schmitz Mouridsen <jsm@freebsd.org> wrote:
On 31.12.2023 20.37, John Kennedy wrote:
> On Fri, Dec 29, 2023 at 06:05:25PM +0100, Jesper Schmitz Mouridsen wro= te:
>> On 29.12.2023 05.55, ykla wrote:
>>> Hi, When will FreeBSD support RPI5
>> https://forums.freebsd.org/t= hreads/raspberry-pi-5-status.91406/
>=C2=A0 =C2=A0 Having ordered my RPI5 ~11/28, I think it has a shipping = guesstimate in late
> Jan/early Feb.=C2=A0 It looks like someone is working on uboot, which = FreeBSD seems
> to favor (I think the argument I retained was "it works for lots = of things,
> piggyback on those efforts rather than have some RPI-unique thing).=C2= =A0 Then once
> you start getting things properly enumerated to where you can load the= kernel,
> then you work on the kernel drivers.
>
>=C2=A0 =C2=A0 RPI seems to favor linux support first, and I suspect tha= t there is a fair
> amount of GPL issues that you might have to worry about creeping into = the BSD
> kernel.=C2=A0 So not as simple as reimplement from what you see in lin= ux.=C2=A0 I know
> there are a lot of strong opinions on video drivers, for example, but = for that
> to even ben an option it'd have to be something that could be a mo= dule that
> could be packaged outside of the BSD base.=C2=A0 I only bring that up = because I've
> had garbage luck trying to get serial consoles to work properly on RPI= s when
> they're competing for things like cooling fans and such, so graphi= cs console
> is nice, even if it is just very basic.
>
>=C2=A0 =C2=A0 How have people been chicken-n-egging the initial setup?= =C2=A0 I know there have
> been uboot issues in the past.=C2=A0 Seems like you basically have to = build memstick
> style images and see if they boot.=C2=A0 Is there a bhyve/QEMU setup t= hat is a
> generic test setup that is used?

I just built a patched u-boot and uses a stock rpi img snapshot, then
cross build and move the kernel to the rpi sd card..

no qemu emulates all the phys. hw in the rpi5..


--0000000000008e522c060e995121--