From nobody Sat Jan 13 19:22:07 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 4TC7ZT5qGkz56TFt for ; Sat, 13 Jan 2024 19:22:09 +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 4TC7ZT5KJ7z46Ll; Sat, 13 Jan 2024 19:22:09 +0000 (UTC) (envelope-from jsm@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1705173729; 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=VOqXgyBbawo4hCTb9GC0Lak2nVyMItPWnRSs17IQpsU=; b=Wu68pMJOwM3I/B6qsjUPCpCFyggv8LLBqcumoEj3R2mWpGGY4Y79ZFclJK/VY+jWt6YyVR AXSSpX+P+ivr01mahGHa+eNEg5pK7Cn4BrvBSXlOyiU4qY11DJ41c0WpW93yP5MzD7uFX+ x5oh/JGNR/BMgiacYLwcJM5zs3oJ+XtMKWW/ihPJpur/OFoBVoUY/dLhWZgP4yl6NbYhkN rvdjbL5LY1Tp5TsCFby1pAbgyr3ww4CVHL/BJTSzIOnbpq8pdH80VlxHZGxhiFFd0DdOB4 1DShppRw1ciXJ/vSHlVVeM2WhS0ITca6N1/bOvQHSbmvMO4EBcsV+zr8Kuarpw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1705173729; 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=VOqXgyBbawo4hCTb9GC0Lak2nVyMItPWnRSs17IQpsU=; b=g9sRYhf04ZN0dnPqss/fu0ozuUCMYJMMQRBe2pi39wXcc2zBVV9vZoC8XgW7zMpesvvWje DsJySL+p/YyvyzU6mFcQUTcafS56zUb1sNwIBaVeILrg1rRlm+claNvn1i+vKVZQovayAI FriLebjOkqH6VT+gnte2UrkH5aG8VZJe5QHB1Z5U4FB2gg5RkjfISwYzU+AXlZeanQ6pZB KWRMbskzDKgBgWRl12bdi13G5aksuQryl+S0IsWzlHI9ghMy/I3UiRbHCCbWtWlbhpJew2 Z1k2ih+CYLYuhls/krgsL/MebfW1OY2pNWydmf6cDaGx1/OBOkqVlhH3miTldA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1705173729; a=rsa-sha256; cv=none; b=jvC34+MZCbvOM1EWTciVrz2DdQmIV/8soLF7Ssghi1LuxQPLGJjVbSDmmH6GHkdLyayyR0 qJQVTWikymQd+eqp/MZOlLt3JQwk7n6TX/I6Q3eK9mSe5yEwwirvPxosvRW4mZcQJEbfj0 xlrNawR85b6yUqdeTd2yJ/0Vj+c6YZIuDuqka5wYK+Nwx4ASHJ0bl4AvL1m7wqwlX9qse0 axIFO1q8B0btnOD1BYzjw5r6RutvHZ0pt69xzrWjbZQraoBbT8K6gC/UQQVFtZ3Z5UCMYo qgiAMPS67vdD3wJpcMwKfyxWdFWjkF4mYGE8I3afAJIm5rjAc8FdUE1U2sOGwQ== 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 4TC7ZS6yqkzQfj; Sat, 13 Jan 2024 19:22:08 +0000 (UTC) (envelope-from jsm@FreeBSD.org) Message-ID: <9e45c7d7-450c-48e5-8101-c6ea5cb3a023@FreeBSD.org> Date: Sat, 13 Jan 2024 20:22:07 +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? Content-Language: en-US To: Mark Millard , Doug Rabson Cc: John Kennedy , ykla , FreeBSD ARM List References: <5a39810c-5fd8-4969-a222-2561b050b035@FreeBSD.org> <347FE009-A470-4765-A9B9-7C9AB5E954DA@yahoo.com> <76FA010A-338F-4E32-B381-37C7BA63CAFC@yahoo.com> From: Jesper Schmitz Mouridsen In-Reply-To: <76FA010A-338F-4E32-B381-37C7BA63CAFC@yahoo.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 13.01.2024 19.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? How does the sd card show up? BTW i did put some stuff here [1] I could not get bcm_dma to work anyone planning on getting that to work? it should be similar to 2711 documented in [2] >> 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. > > === > Mark Millard > marklmi at yahoo.com > > [1] https://github.com/jsm222/rpi5-stuff [2] https://datasheets.raspberrypi.com/bcm2711/bcm2711-peripherals.pdf