From nobody Sun Dec 31 19:37:33 2023 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 4T38ZW6YBTz557cq for ; Sun, 31 Dec 2023 19:39:31 +0000 (UTC) (envelope-from warlock@phouka1.phouka.net) Received: from phouka1.phouka.net (phouka1.phouka.net [107.170.196.116]) (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 (2048 bits) client-digest SHA256) (Client CN "phouka.net", Issuer "Go Daddy Secure Certificate Authority - G2" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4T38ZW1122z3Nmh; Sun, 31 Dec 2023 19:39:31 +0000 (UTC) (envelope-from warlock@phouka1.phouka.net) Authentication-Results: mx1.freebsd.org; dkim=none; spf=none (mx1.freebsd.org: domain of warlock@phouka1.phouka.net has no SPF policy when checking 107.170.196.116) smtp.mailfrom=warlock@phouka1.phouka.net; dmarc=none Received: from phouka1.phouka.net (localhost [127.0.0.1]) by phouka1.phouka.net (8.17.1/8.17.1) with ESMTPS id 3BVJbY01070862 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Sun, 31 Dec 2023 11:37:34 -0800 (PST) (envelope-from warlock@phouka1.phouka.net) Received: (from warlock@localhost) by phouka1.phouka.net (8.17.1/8.17.1/Submit) id 3BVJbXhm070861; Sun, 31 Dec 2023 11:37:33 -0800 (PST) (envelope-from warlock) Date: Sun, 31 Dec 2023 11:37:33 -0800 From: John Kennedy To: Jesper Schmitz Mouridsen Cc: ykla , FreeBSD ARM List Subject: Re: When will FreeBSD support RPI5? Message-ID: References: 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-Disposition: inline In-Reply-To: X-Spamd-Result: default: False [-0.70 / 15.00]; AUTH_NA(1.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.90)[-0.905]; FORGED_SENDER(0.30)[warlock@phouka.net,warlock@phouka1.phouka.net]; MIME_GOOD(-0.10)[text/plain]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; R_SPF_NA(0.00)[no SPF record]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:14061, ipnet:107.170.192.0/18, country:US]; R_DKIM_NA(0.00)[]; FREEMAIL_CC(0.00)[gmail.com,freebsd.org]; MID_RHS_MATCH_FROMTLD(0.00)[]; TO_DN_ALL(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; FROM_NEQ_ENVFROM(0.00)[warlock@phouka.net,warlock@phouka1.phouka.net]; RCPT_COUNT_THREE(0.00)[3]; DMARC_NA(0.00)[phouka.net]; RCVD_TLS_LAST(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4T38ZW1122z3Nmh X-Spamd-Bar: / 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?