From nobody Sat Jan 13 19:04:55 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 4TC7Bm0ZMcz56RZd for ; Sat, 13 Jan 2024 19:05:04 +0000 (UTC) (envelope-from mike@karels.net) Received: from mail2.karels.net (mail2.karels.net [3.19.118.201]) (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 "freebsd", Issuer "freebsd" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4TC7Bl5skTz444G for ; Sat, 13 Jan 2024 19:05:03 +0000 (UTC) (envelope-from mike@karels.net) Authentication-Results: mx1.freebsd.org; none Received: from mail2.karels.net (localhost [IPv6:0:0:0:0:0:0:0:1]) by mail2.karels.net (8.17.1/8.17.1) with ESMTP id 40DJ4u4J074423; Sat, 13 Jan 2024 13:04:57 -0600 (CST) (envelope-from mike@karels.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=karels.net; s=mail2; t=1705172697; bh=ZDZrmh+Iv8pQy/wAD7vk0hdpCQVP9TYKm7S4tlVApno=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=G8YOHaceeeoLigfjCQlI7WIseDqWFwev2cFP0ElcBGq4Ct7HT17rnEFvMiKPbo4gv 8tvr04Y5fvd3kFIxjni5YHxTB5ECXq2IBvqOGZ3QAoALulZXn54i1L3Dquo/ms1VyV 1c5UHSrgGYr8xGN10rq/Su8NmNs+lvUDbPdtbZ8TpkszoH2kzysLSpuoGEw1NVqhSG BPWoUR/Bsqkh0B4V9t3EtxUzsVe7NaEQaaYVjnVLDziNT+1FmMJLTtPE+DZokCdbQW phPUMa+LhZuqQHm2ZM0zZ4dNpXaXKRqHvPO7F3xdBL5BVHq7AXPyWAv8X/uyNUVaRP rAlwQdR/2ckAg== Received: from [10.0.2.130] ([73.62.165.147]) by mail2.karels.net with ESMTPSA id aFuuMtjeomW1IgEAs/W3XQ (envelope-from ); Sat, 13 Jan 2024 13:04:57 -0600 From: Mike Karels To: Mark Millard Cc: Doug Rabson , FreeBSD ARM List Subject: Re: When will FreeBSD support RPI5? Date: Sat, 13 Jan 2024 13:04:55 -0600 X-Mailer: MailMate (1.14r6015) Message-ID: <1C02D1FA-5BF0-4C82-AD0E-6F9E5EB8A0B9@karels.net> In-Reply-To: <76FA010A-338F-4E32-B381-37C7BA63CAFC@yahoo.com> References: <5a39810c-5fd8-4969-a222-2561b050b035@FreeBSD.org> <347FE009-A470-4765-A9B9-7C9AB5E954DA@yahoo.com> <76FA010A-338F-4E32-B381-37C7BA63CAFC@yahoo.com> 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 Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4TC7Bl5skTz444G X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:16509, ipnet:3.16.0.0/14, country:US] On 13 Jan 2024, at 12:32, Mark Millard wrote: > On Jan 13, 2024, at 07:38, Doug Rabson wrote: > >> Getting back to the RPI 5, with a tweak to arm/broadcom/bcm2835bcm2835= _vcbus.c to treat the memory config the same as RPI 4 and to dev/sdhci/sd= hci_fdt.c to treat the RPI 5 sdhci controllers as generic, I can boot to = multiuser mode using the EDK2 firmware from https://github.com/worproject= /rpi5-uefi with ACPI/Device Tree mode set to Both. > > What does FreeBSD do with "Both"? Does it actually use some ACPI > and some Device Tree? Or does it just use ACPI? Does your > combination do anything different than just using ACPI? > >> This does not have working PCIe or ethernet yet - I think ethernet oug= ht to work since we seem to have a matching driver in the tree in dev/cad= ence. > > Sounds like the same status as booting just ACPI with no such > adjustments too bcm2835bcm2835_vcbus.c or sdhci_fdt.c ? > > I think Mike Karels plans on investigating getting Ethernet > going based on cgem . I've no clue if this is ACPI, DeviceTree, > or both. The cadence/cgem driver uses FDT. I haven't looked at details yet. The = addition might be as simple as adding a compat string. Hopefully it doesn't requi= re major surgery. I just ordered an RPi 5 (8 GB); it will take a while to be deli= vered. Mike > > My usage has been pure ACPI, no software adjustments specific > to getting the RPi5 operational. Use of a USB3 Ethernet dongle. > > =3D=3D=3D > Mark Millard > marklmi at yahoo.com