From owner-freebsd-arm@freebsd.org Fri Jun 12 18:18:11 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 042E9341CA0 for ; Fri, 12 Jun 2020 18:18:11 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: from out0.migadu.com (out0.migadu.com [94.23.1.103]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 49k89G1M1Jz3c4k; Fri, 12 Jun 2020 18:18:09 +0000 (UTC) (envelope-from greg@unrelenting.technology) Date: Fri, 12 Jun 2020 18:17:57 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=unrelenting.technology; s=default; t=1591985881; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=1k+hrVm2e9lk2zYodNkGftKJ8kewkgEKo5a0GXho/k4=; b=YNJb3MIRtny62SE0Vkuul9sZisSXbjtcfikDFm4GnpfrCR1AYL7VvpBrJgww56L6b45eD2 ED5r64kQQ2mwZsSw7sCGHhz3eZVPpI5OCOQa/3Ebw9gWKyjoJFxcZO1Xpli/TG6QJUJSYe 5lrXsGu4STiVbEKDw0jL3jofUD2H0ko= X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: myfreeweb To: Ian Lepore , Hans Petter Selasky , Robert Crowston , =?ISO-8859-1?Q?Klaus_K=FCchemann?= , Mark Millard , freebsd-arm@freebsd.org Subject: Re: Unrelenting testplan D25219 In-Reply-To: References: <876E685B-B3AC-4821-A88F-702ABA3D9812@yahoo.com> <5FE76178-4255-46B0-9A0D-F7640EFCBBE4@googlemail.com> <8414e0163e5cb2e9c4a4c7b02aa01666@unrelenting.technology> <5B8A58D0-9662-49DD-9CC3-226A3A92EFD6@googlemail.com> <097cbf6a-7b47-9346-c3af-fee7e709e1fa@selasky.org> Message-ID: <8E5794F2-EB53-465B-ADB6-D9896FACDD78@unrelenting.technology> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Score: -0.10 X-Rspamd-Queue-Id: 49k89G1M1Jz3c4k X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=unrelenting.technology header.s=default header.b=YNJb3MIR; dmarc=pass (policy=none) header.from=unrelenting.technology; spf=pass (mx1.freebsd.org: domain of greg@unrelenting.technology designates 94.23.1.103 as permitted sender) smtp.mailfrom=greg@unrelenting.technology X-Spamd-Result: default: False [-3.71 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.98)[-0.978]; R_DKIM_ALLOW(-0.20)[unrelenting.technology:s=default]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:94.23.1.103]; NEURAL_HAM_LONG(-0.99)[-0.985]; MIME_GOOD(-0.10)[text/plain]; RCPT_COUNT_FIVE(0.00)[6]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[unrelenting.technology:+]; DMARC_POLICY_ALLOW(-0.50)[unrelenting.technology,none]; NEURAL_HAM_SHORT(-0.75)[-0.752]; FREEMAIL_TO(0.00)[freebsd.org,selasky.org,protonmail.com,googlemail.com,yahoo.com]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RWL_MAILSPIKE_VERYGOOD(0.00)[94.23.1.103:from]; ASN(0.00)[asn:16276, ipnet:94.23.0.0/16, country:FR]; MID_RHS_MATCH_FROM(0.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jun 2020 18:18:11 -0000 On June 12, 2020 5:35:47 PM UTC, Ian Lepore 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)