From nobody Wed Jan 3 15:10: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 4T4tSy1rNgz5644p for ; Wed, 3 Jan 2024 15:10:42 +0000 (UTC) (envelope-from jsm@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (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 "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4T4tSy1Q7rz4WKH; Wed, 3 Jan 2024 15:10:42 +0000 (UTC) (envelope-from jsm@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1704294642; 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=0FD5q2PckT1AzycQuqKV+Sd6RXNULclGqFM568N9pmY=; b=cKZ8qMHfKY12bcQ2nxhibSCGcRnfvGF7lSzChWcp9shV4fgNZeOCRF/3LXgGnc0LMkb9U6 wGnSOf4JK7KYnB0GcLnJ28iPN8eTq3W6TqYvnGf8GaaV/Z5x2qM6wmxuNpNbsTA/SmJTTz Bx6f2E6hyLWTHfEmoSCbNhzo+vkfsU+Xdm+/bG7OKrXDb40fEiOkHwwZTltaWwIRonXY1i uTNT9bCAkO1kqHwhJb6Vapkx0LMSLo0AvqDtaaDuuOnpqBGERjgLeCqLOuJx7sB6xSEzYF YBu0oDHwCHH3MUXQomQyK3ZpZTX69UAliSegyxMZgfUxkXpv5LUMyk1tK4Wkbw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1704294642; 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=0FD5q2PckT1AzycQuqKV+Sd6RXNULclGqFM568N9pmY=; b=pMzjfVeBLvKsXJx2Gtk6EoTyI+Ab5LGtYg4yLZgpFCWdVfM1a5gDcm9A9H96WCcjYm7ooo XkswEeg2if0FsdtyesTEz1a7kw6CHbP/JGvyCOPpWld693yo+Lh+oYqMq71rlunjsjRLAI DTTX33y78Q9Vu3XDs1unAiDxJpm8d5x/RP0bG5vfiTWtZX5LCD9oC4AfUevNsEhjaoxYCj zsWgi/dQu2dNeTDTQc+V+o9DAsVY6r4pKYHT8sFMk2mJtRkDT2oP8dlBi2QbNug62eSm7h tPkZmu7l5H4PPdK/gKJ3twc+PqQvxxi4N03IPqzz55liO7IoCCagg+jikUXuag== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1704294642; a=rsa-sha256; cv=none; b=VwV6oWuBifYAg2yhnq8a2Nu/DOrODDIAVSZ+bjfXM8+AmXI8TAG38m9rs7MpW5t7y3Cn2p S4VvZJCLlWIs4K/+dKy0ZyJf73Ptwiwd2BRYkKEP9Mhv5416/XR3eVyVbtEhYvjWoPAlKd SsmDasWwUVQ8WDFCR2PWeCfxBg6lSptWc5IU4Dunfjja5dVga0JuUOT4LpbaUk3sE6qh+L s0d+PbIulEQ68ZCZ/c9DP4auKkfE9kHuCkma/l7wcDo4hnLHERuAjcQuJE/YgPDwIGoFlf kb3QJGLxmILTREsBc/DABD4fXoQuM6U9mDrzmppB8qyju0NEyN+G93/Ks5p2Pg== Received: from [192.168.1.5] (mail.northatlanticmusicsupplies.com [212.237.182.202]) (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) (Authenticated sender: jsm) by smtp.freebsd.org (Postfix) with ESMTPSA id 4T4tSx4S5Wz139k; Wed, 3 Jan 2024 15:10:41 +0000 (UTC) (envelope-from jsm@FreeBSD.org) Message-ID: <5a39810c-5fd8-4969-a222-2561b050b035@FreeBSD.org> Date: Wed, 3 Jan 2024 16:10:10 +0100 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 Thunderbird Subject: Re: When will FreeBSD support RPI5? To: John Kennedy Cc: ykla , FreeBSD ARM List References: Content-Language: en-US From: Jesper Schmitz Mouridsen In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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..