From nobody Sun Jan 14 15:11: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 4TCdzX0vx2z56Nyx for ; Sun, 14 Jan 2024 15:12:08 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mx.blih.net (mx.blih.net [212.83.155.74]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4TCdzW3xSZz44V3; Sun, 14 Jan 2024 15:12:07 +0000 (UTC) (envelope-from manu@bidouilliste.com) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bidouilliste.com; s=mx; t=1705245119; 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=6YinCkRpW6HP8qJpIf25LpnHJcCwN0Mc5Vw7H5BKNgk=; b=LdGkQkYQvrLhOG9pTwAnsvSDmlyJv0OPpp2WX+vb7s4whc7fBjfjEmuX5V55zg5vNvvfQt w6OMNrN9R6aHVdD7qp/I1UQuZnCgFbYixwKD1A+XO16/Yj+ghLNXnTmAJfNFq0uIYL+10H Xl2OeRWVTHV+d0QudboA2UuRLAfoHyc= Received: from skull.home.blih.net (lfbn-lyo-1-2174-135.w90-66.abo.wanadoo.fr [90.66.97.135]) by mx.blih.net (OpenSMTPD) with ESMTPSA id 34e1e58b (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Sun, 14 Jan 2024 15:11:59 +0000 (UTC) Date: Sun, 14 Jan 2024 16:11:55 +0100 From: Emmanuel Vadot To: Doug Rabson Cc: Mark Millard , Jesper Schmitz Mouridsen , John Kennedy , ykla , FreeBSD ARM List Subject: Re: When will FreeBSD support RPI5? Message-Id: <20240114161155.e82b64f2b0cf82fea0e606e4@bidouilliste.com> In-Reply-To: References: <5a39810c-5fd8-4969-a222-2561b050b035@FreeBSD.org> <347FE009-A470-4765-A9B9-7C9AB5E954DA@yahoo.com> <76FA010A-338F-4E32-B381-37C7BA63CAFC@yahoo.com> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd15.0) 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-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4TCdzW3xSZz44V3 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:12876, ipnet:212.83.128.0/19, country:FR] On Sun, 14 Jan 2024 13:52:51 +0000 Doug Rabson wrote: > On Sat, 13 Jan 2024 at 18: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/sdhci_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 ought > > to work since we seem to have a matching driver in the tree in dev/cadence. > > > > 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. > > > > My usage has been pure ACPI, no software adjustments specific > > to getting the RPi5 operational. Use of a USB3 Ethernet dongle. > > > > As far as I can tell, 'Both' works almost exactly the same as 'Devicetree' > - I don't think the acpi device is attached to nexus at all. 'Both' for EDK2 mean that dt and acpi table are exposed, and by default on FreeBSD we use dt and only fallback to acpi if dt wasn't found. > Ethernet should be supported by cgem(4). This device is on the rp1 > southbridge. In the DTB, rp1 is a simplebus under pcie@120000 > and ethernet@100000 is a child of rp1. I think it doesn't match for me > because there is no driver matching pcie@ yet. The existing bcm2838 pci > driver could be adapted for RPI 5 - reading the linux driver shows some > smallish differences in device initialisation. > > I have attached verbose dmesg dumps for all three EDK2 acpi modes. > > > > -- Emmanuel Vadot