From owner-freebsd-arm@freebsd.org Wed Jun 10 00:43:39 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 2A385342CB8 for ; Wed, 10 Jun 2020 00:43:39 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: from out1.migadu.com (out1.migadu.com [IPv6:2001:41d0:2:863f::]) (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 49hSsP6cqdz4BYl for ; Wed, 10 Jun 2020 00:43:37 +0000 (UTC) (envelope-from greg@unrelenting.technology) MIME-Version: 1.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=unrelenting.technology; s=default; t=1591749809; 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=N/aHi0kZXopZ2he4EuUkaeipRhYLxYefG2cOSPH+WsU=; b=ZZrPBFtY02hEgm7iF2wqzdEUfs1fxADKymEojSVZbk4HrTef4jg9DW5cNOtKXKY3Qvmt/x SiJ5RldSwK6iHuQRlF/CjaBwDyRC9KDo0VdqXua1PlgC0x6e6hKaU5A26Rqx2ty7ny3vnS 0o55VwJAMC2OgM1qyQxOuPHapFkmlws= Date: Wed, 10 Jun 2020 00:43:29 +0000 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: greg@unrelenting.technology Message-ID: Subject: Re: Driver for Raspberry Pi 4 PCI-express controller To: "=?utf-8?B?S2xhdXMgS8O8Y2hlbWFubg==?=" , freebsd-arm@freebsd.org In-Reply-To: References: <747C1F44-658F-4178-9021-F97F9115AEB0@yahoo.com> <7F058E92-DDD3-4728-9A51-09BF1D47855C@googlemail.com> <1RBZ-1AclgkiNDwWUqrWhun8T8YSAX6g64NeSc2DKy9EF1wGsJobselP4UYGflpcmbfUx3sEEM2YplIJOXPmZ6EG_GwiMC1_3GLrqpZxisQ=@protonmail.com> <46519DEB-E96D-43DD-B739-401F9F51371E@googlemail.com> <87EE030D-5323-477B-9FF3-CB8970138729@googlemail.com> <377EA2D7-F7C8-4ECA-9BFC-1EC081665C04@yahoo.com> <0AA4AF68-62D5-4918-8B23-13D29E2EB09F@googlemail.com> <15c76ecd4fcaf4306682ac4a6c8ef393@unrelenting.technology> X-Spam-Score: -0.10 X-Rspamd-Queue-Id: 49hSsP6cqdz4BYl X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=unrelenting.technology header.s=default header.b=ZZrPBFtY; dmarc=pass (policy=none) header.from=unrelenting.technology; spf=pass (mx1.freebsd.org: domain of greg@unrelenting.technology designates 2001:41d0:2:863f:: as permitted sender) smtp.mailfrom=greg@unrelenting.technology X-Spamd-Result: default: False [-4.29 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.02)[-1.020]; R_DKIM_ALLOW(-0.20)[unrelenting.technology:s=default]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2001:41d0:2:863f::]; NEURAL_HAM_LONG(-0.98)[-0.984]; MIME_GOOD(-0.10)[text/plain]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[unrelenting.technology:+]; RCPT_COUNT_TWO(0.00)[2]; FROM_NO_DN(0.00)[]; NEURAL_HAM_SHORT(-1.29)[-1.286]; DMARC_POLICY_ALLOW(-0.50)[unrelenting.technology,none]; FREEMAIL_TO(0.00)[googlemail.com,freebsd.org]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:16276, ipnet:2001:41d0::/32, 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: Wed, 10 Jun 2020 00:43:39 -0000 June 10, 2020 3:07 AM, "Klaus K=C3=BCchemann" = wrote:=0A=0A>> Am 10.06.2020 um 01:57 schrieb Klaus K=C3=BCchemann :=0A>> =0A>>> Am 10.06.2020 um 01:34 schrieb greg@u= nrelenting.technology:=0A>>> =0A>>> =E2=80=A6.=0A>>> Only NetBSD does the= required thing right now.=0A>>> =E2=80=A6=0A>> =0A>> no, they also panic= after disabling the 3 gig limit :=0A>> https://www.klos.com/~john/rpi4_3= gig_8gig_dmesg=0A>> =0A>> but since you really hit the ground running unr= elenting today :-) , you can send your next bugfix=0A>> also to NetBSD=0A= >> Maybe it has to do with the V1.14, so perhaps, after we tested all you= r patches=0A>> On both 4&8Gig we talk to @AndreWarkentin again perhaps=0A= > =0A> ah, forgot link to boot failure in NetBSD :=0A> https://www.klos.c= om/~john/rpi_boot_failure.jpg=0A=0AWell that's a hang that might be cause= d by anything.=0AThey do handle *this*.=0A=0AAnd here's a little preview = of how we'll handle it:=0Ahttps://reviews.freebsd.org/P391=0A=0Aroot@:~ #= vmstat=0Aprocs memory page disks faults = cpu=0Ar b w avm fre flt re pi po fr sr da0 pa0 in = sy cs us sy id=0A0 0 0 95M 3.7G 139 0 1 0 167 1 0 = 0 119 442 263 0 0 100=0A=0Aroot@:~ # dmesg | grep xhci=0Axhci0: iomem 0x600000000-0x600000fff irq 0 on acpi0= =0A... :)