Date: Fri, 9 Oct 2020 15:21:48 +0200 From: Klaus Cucinauomo <maciphone2@googlemail.com> To: Kyle Evans <kevans@freebsd.org>, freebsd-arm@freebsd.org, Mark Millard <marklmi@yahoo.com> Subject: Re: RPi4B: emmc2bus dma-range handling does not track the boot-time-FDT (u-boot based booting) Message-ID: <9D391B40-894C-4D18-B0BD-F5A03734290A@googlemail.com> In-Reply-To: <CACNAnaHeFEnja57fqq0Y8c__A3jUAvnM_jmOF64RVAqS7%2B1sLw@mail.gmail.com> References: <D8BDF95A-D6A8-4E95-A0CE-D53068E8355B.ref@yahoo.com> <D8BDF95A-D6A8-4E95-A0CE-D53068E8355B@yahoo.com> <CACNAnaG3CKTiXdXNUO1Jgr34=XGF4wYRuUnuiJRhNb1J9XaGbw@mail.gmail.com> <CACNAnaEZP=Gxs4cbvCOFzM8MZB6-2Ny0N7KEW-nYoDw22_Jzwg@mail.gmail.com> <CACNAnaFXpJcA5Xyw%2BPR6iem3U2nvpog53hsnCFKiGWiO6OgKKA@mail.gmail.com> <32A8A046-56DF-4998-9C3D-8630ACCE4951@yahoo.com> <CACNAnaHwAyw=6tiOC12WH9BBcj5FDZzDGxoh0UJw9KL0HE206g@mail.gmail.com> <68AC0E4E-0469-46AE-BD68-058DCB6B078F@yahoo.com> <CACNAnaHeFEnja57fqq0Y8c__A3jUAvnM_jmOF64RVAqS7%2B1sLw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Am 09.10.2020 um 14:55 schrieb Kyle Evans <kevans@freebsd.org>:
>>>>=20
>>=20
>> Another type of overall issue (that may not apply to
>> the specific context here) is dtb content like:
>>=20
>> scb {
>> compatible =3D "simple-bus";
>> #address-cells =3D <0x00000002>;
>> #size-cells =3D <0x00000002>;
>> ranges =3D * 0x0000000007ef8a18 [0x00000060];
>> dma-ranges =3D <0x00000000 0x00000000 0x00000000 =
0x00000000 0x00000000 0xfc000000 0x00000001 0x00000000 0x00000001 =
0x00000000 0x00000001 0x00000000>;
>> phandle =3D <0x000000d0>;
>> pcie@7d500000 {
>> compatible =3D "brcm,bcm2711-pcie";
>> . . .
>> #address-cells =3D <0x00000003>;
>> #interrupt-cells =3D <0x00000001>;
>> #size-cells =3D <0x00000002>;
>> . . .
>> dma-ranges =3D <0x02000000 0x00000000 =
0x00000000 0x00000000 0x00000000 0x00000000 0xc0000000>;
>> . . .
>> };
>> . . .
>>=20
>> where the inner most dma-ranges is not from the just-surrounding
>> context (parent) but is strictly local (despite the parent
>> potentially also having dma-ranges). I think that only pcie@...
>> is that way so far for the RPi4 --but notationally it seems to
>> be generally allowed.
>>=20
>=20
> This is irrelevant for the time being as the PCI driver doesn't cross
> paths with the snippet the patch touches.
>=20
> Thanks,
>=20
> Kyle Evans
>=20
Yes, dma is another topic=E2=80=A6 thanks for working on RPI again !,
external links to the xhci-initializiation - issue for the 8GB-model in =
u-boot 2020.10 :
=
http://u-boot.10912.n7.nabble.com/PATCH-v6-0-4-usb-xhci-Load-Raspberry-Pi-=
4-VL805-s-firmware-td418114.html
=
https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg2205783.html
=
https://patchwork.ozlabs.org/project/linux-pci/patch/20200629161845.6021-4=
-nsaenzjulienne@suse.de/
=
https://patchwork.ozlabs.org/project/linux-pci/patch/20200629161845.6021-5=
-nsaenzjulienne@suse.de/
`guess there will be some other DeviceTree-adjustments needed to boot =
directly off of an SSD until reaching the root-login.
Regards
K.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9D391B40-894C-4D18-B0BD-F5A03734290A>