Date: Sun, 9 Feb 2020 20:32:33 -0800 From: Mark Millard <marklmi@yahoo.com> To: Bakul Shah <bakul@bitblocks.com> Cc: freebsd-arm@freebsd.org Subject: Re: RPI4 Install r357606 test 09.02.2020 failed Message-ID: <A5BFEEB5-7992-4442-91D5-3CDC41D977E5@yahoo.com> In-Reply-To: <00DDDEDB-7C81-461B-87C4-E6261E2F70C2@bitblocks.com> References: <202002092026.019KQXLF021366@mail.karels.net> <4551CAE8-08DA-463F-876C-DD1BBAA5D7C5@bitblocks.com> <D11F4E71-FF1F-4C13-8F3C-A197AB372E3E@yahoo.com> <D5F8A326-877A-42A4-B35B-7CD7B60CFF02@bitblocks.com> <1AD3680D-CDD9-4FB1-86B5-C49269F2CC33@yahoo.com> <00DDDEDB-7C81-461B-87C4-E6261E2F70C2@bitblocks.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2020-Feb-9, at 20:19, Bakul Shah <bakul at bitblocks.com> wrote: > On Feb 9, 2020, at 8:10 PM, Mark Millard via freebsd-arm = <freebsd-arm@freebsd.org> wrote: >>=20 >>=20 >>=20 >> On 2020-Feb-9, at 18:32, Bakul Shah <bakul at bitblocks.com> wrote: >>=20 >>> On Feb 9, 2020, at 2:48 PM, Mark Millard via freebsd-arm = <freebsd-arm@freebsd.org> wrote: >>>>=20 >>>> If you want a build that works, use the kernel from head >>>> -r356767 . The next head version ( -r356776 ) is where >>>> the broken status starts for RPi4 and RPi3. RPi4B's with >>>> 4 GiBYTes of RAM fail to boot. As I understand, at least >>>> some forms of RPi3 boot but are messed up, such as only >>>> running 1 core. (Not surprising given the PSCI version >>>> problem which happens there as well.) >>>=20 >>> With this version I was able to boot it and log in as root. >>> Thanks! >>>=20 >>> I don't see any bcm2711 specific files in sys/arm/broadcom/bcm2835. >>> Is this intentional? pi3 (bcm2838) and pi4 (bcm2711) are rather >>> different. >>=20 >> The ports: >>=20 >> sysutils/rpi-firmware >> sysutils/u-boot-rpi4 >>=20 >> have the materials that are used, including a .dtb >> file. There are other >>=20 >> sysutils/u-boot-rpi* >>=20 >> ports as well. The rpi-firmware has materials for >> all of them. >=20 > Thanks. Yes, I am aware of those and used them as well. >=20 > Sorry, I wasn't clear. I am talking about FreeBSD driver > code. For example PCIe, XHCI and ethernet code will be > different. There are other differences as well. Not sure > all that is captured in the device tree files. Ahh. These things have not been developed yet. I'm not sure it is clear what their future is, given the=20 documentation status for them and other issues around RPi*'s and their history for FreeBSD. =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A5BFEEB5-7992-4442-91D5-3CDC41D977E5>