Date: Fri, 12 Jun 2020 19:34:40 +0200 From: =?utf-8?Q?Klaus_K=C3=BCchemann?= <maciphone2@googlemail.com> To: Hans Petter Selasky <hps@selasky.org>, Robert Crowston <crowston@protonmail.com>, myfreeweb <greg@unrelenting.technology>, Mark Millard <marklmi@yahoo.com>, freebsd-arm@freebsd.org Subject: Re: Unrelenting testplan D25219 Message-ID: <41B87C1F-E8F9-4B2C-890E-4A2F47E5FC6D@googlemail.com> In-Reply-To: <097cbf6a-7b47-9346-c3af-fee7e709e1fa@selasky.org> References: <876E685B-B3AC-4821-A88F-702ABA3D9812@yahoo.com> <5FE76178-4255-46B0-9A0D-F7640EFCBBE4@googlemail.com> <F1DC2AFB-0CC7-407D-A6C0-4E109590612E@unrelenting.technology> <C7D9957A-5C58-48FF-9601-7DD13DE9D89B@googlemail.com> <8414e0163e5cb2e9c4a4c7b02aa01666@unrelenting.technology> <5B8A58D0-9662-49DD-9CC3-226A3A92EFD6@googlemail.com> <abc05bea-ea4a-9189-611c-a1a0000182d8@selasky.org> <FE0813DD-29CA-4ADA-BD6B-963E3DC635B2@googlemail.com> <eHCAzXv-Rr39w3F-euypm4DrLx9jd88297x9hyHaNi_-VXR-ZiLdgFg6HvpI87aFLHGM_YcbOLADi0BLIR0jy557fbWDxKs4yIqf5ZfsDZ4=@protonmail.com> <097cbf6a-7b47-9346-c3af-fee7e709e1fa@selasky.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> Am 12.06.2020 um 18:49 schrieb Hans Petter Selasky <hps@selasky.org>:
>=20
> On 2020-06-12 17:02, Robert Crowston wrote:
>> What is the physical address to which the xhci controller is =
performing DMA? It needs to be in the lower 3 GB of the physical address =
space.
>=20
> The XHCI doesn't set any limits on the DMA location, but it easily =
can.
>=20
> We have a quirk for 32-bits:
>=20
> set hw.usb.xhci.dma32=3D1
>=20
> =46rom the loader.
>=20
> --HPS
no luck for now..
(later I=E2=80=99ll try kernel without D25219 )
-
OK show
beastie_disable=3DYES
boot_multicons=3DYES
boot_serial=3DYES
bootenv_autolist=3DYES
bootfile=3Dkernel
console=3Dcomconsole
currdev=3Ddisk1p2:
efi-version=3D2.70
efi_com_port=3D0
efi_com_speed=3D115200
efi_max_resolution=3D1x1
hint.smbios.0.mem=3D0x37200000
hw.usb.template=3D3
hw.usb.xhci.dma32=3D1
interpret=3DOK
kernel=3Dkernel
kernel_options=3D
kernel_path=3D/boot/kernel
kernelname=3D/boot/kernel/kernel
kernels_autodetect=3DYES
loaddev=3Ddisk1p2:
loader_color=3DNO
module_blacklist=3Ddrm drm2 radeonkms i915kms amdgpu
module_path=3D/boot/kernel;/boot/modules;/boot/dtb;/boot/dtb/overlays
nextboot_conf=3D/boot/nextboot.conf
nextboot_enable=3DNO
prompt=3D${interpret}
script.lang=3Dlua
smbios.bios.reldate=3DJun 9 2020 11:11:23
smbios.bios.vendor=3Dhttps://github.com/pftf/RPi4
smbios.bios.version=3DUEFI Firmware v1.14
smbios.chassis.maker=3DSony UK
smbios.chassis.serial=3D0000DCA632B35900
smbios.chassis.version=3DRaspberry Pi 4 Model B
smbios.memory.enabled=3D1048576
smbios.planar.maker=3DSony UK
smbios.planar.product=3DRaspberry Pi 4 Model B
smbios.planar.serial=3D0000DCA632B35900
smbios.planar.version=3DD03114
smbios.socket.enabled=3D1
smbios.socket.populated=3D1
smbios.system.family=3DRaspberry Pi
smbios.system.maker=3DSony UK
smbios.system.product=3DRaspberry Pi 4 Model B
smbios.system.serial=3D0000DCA632B35900
smbios.system.sku=3D0000000000D03114
smbios.system.uuid=3D00d03114-0000-0000-0000-dca632b35900=20
smbios.system.version=3DD03114
smbios.version=3D3.3
twiddle_divisor=3D1
verbose_loading=3DYES
> Am 12.06.2020 um 18:12 schrieb myfreeweb =
<greg@unrelenting.technology>:
>=20
> i.e. garbage instead of memstick contents.
>=20
That=E2=80=99s a bug in RPI_EFI.fd
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?41B87C1F-E8F9-4B2C-890E-4A2F47E5FC6D>