Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 8 Oct 2020 15:27:49 +0200
From:      Klaus Cucinauomo <maciphone2@googlemail.com>
To:        Mark Millard <marklmi@yahoo.com>, freebsd-arm@freebsd.org
Subject:   Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting)
Message-ID:  <ABE16EA6-49F1-461F-9B8A-6DAA7ED6A18D@googlemail.com>
In-Reply-To: <D8BDF95A-D6A8-4E95-A0CE-D53068E8355B@yahoo.com>
References:  <D8BDF95A-D6A8-4E95-A0CE-D53068E8355B.ref@yahoo.com> <D8BDF95A-D6A8-4E95-A0CE-D53068E8355B@yahoo.com>

next in thread | previous in thread | raw e-mail | index | archive | help


> Am 08.10.2020 um 11:01 schrieb Mark Millard via freebsd-arm =
<freebsd-arm@freebsd.org>:
>=20
>=20
> The old u-boot/DTB combination in use does not have emmc2bus.
> And, even if it did, FreeBSD would not use =E2=80=A6=E2=80=A6=E2=80=A6.

=E2=80=A6 and the new 2020.10- combinations will even be more =
annoying=E2=80=A6
While I meanwhile e.g. could boot the 4GB off of xhci, it hangs in =
DeviceTree,
Depending on GUESSED ;-) combinations and DeviceTree-patches in src .
There have to be necessary  adjustments which are even not yet =
upstreamed in u-boot=20
(depending on hw-revisions)=E2=80=A6and so on ...
I doubt that anyone really will take explicitly time consuming care of =
all that annoying RPI4-crap.
I don't see any other way than targeting minimum 1 developer(better =
more) ONLY to the RPI-platform=20
for a  time period=E2=80=A6 other than leaving it crappy as is and to be =
happy that it nevertheless=20
is a working fbsd-gadget :-)











Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ABE16EA6-49F1-461F-9B8A-6DAA7ED6A18D>