Date: Fri, 12 Jun 2020 18:17:57 +0000 From: myfreeweb <greg@unrelenting.technology> To: Ian Lepore <ian@freebsd.org>, Hans Petter Selasky <hps@selasky.org>, Robert Crowston <crowston@protonmail.com>, =?ISO-8859-1?Q?Klaus_K=FCchemann?= <maciphone2@googlemail.com>, Mark Millard <marklmi@yahoo.com>, freebsd-arm@freebsd.org Subject: Re: Unrelenting testplan D25219 Message-ID: <8E5794F2-EB53-465B-ADB6-D9896FACDD78@unrelenting.technology> In-Reply-To: <c153681ede0b1aeea61ea75405bc2fa9e844979e.camel@freebsd.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> <c153681ede0b1aeea61ea75405bc2fa9e844979e.camel@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On June 12, 2020 5:35:47 PM UTC, Ian Lepore <ian@freebsd=2Eorg> wrote: >On Fri, 2020-06-12 at 18:49 +0200, Hans Petter Selasky wrote: >> 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=2E >>=20 >> The XHCI doesn't set any limits on the DMA location, but it easily >> can=2E >>=20 >>=20 > >If the xhci controller's view of memory is limited to certain ranges, >then that should be reflected in the dmatag set up by its bus parent >who knows the range restrictions=2E Nothing would need to change in the >xhci driver itself (assuming xhci uses bus_get_dma_tag() like it should >when creating its own tag(s))=2E That is what I did in D25219=2E Works for me=2E (Again, the firmware has a memory limiter option that makes it easy to che= ck whether DMA location is the problem)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8E5794F2-EB53-465B-ADB6-D9896FACDD78>