Date: Wed, 10 Jun 2020 00:43:29 +0000 From: greg@unrelenting.technology To: "=?utf-8?B?S2xhdXMgS8O8Y2hlbWFubg==?=" <maciphone2@googlemail.com>, freebsd-arm@freebsd.org Subject: Re: Driver for Raspberry Pi 4 PCI-express controller Message-ID: <f1e2a0cd8a14821aa550b33ce24d8192@unrelenting.technology> In-Reply-To: <A6D4B55B-E3D3-4A65-B1DE-732EF84E064D@googlemail.com> References: <A6D4B55B-E3D3-4A65-B1DE-732EF84E064D@googlemail.com> <747C1F44-658F-4178-9021-F97F9115AEB0@yahoo.com> <Pm_LEzoJP7MAKrZ9L-pRYQ4-qTv7TK1QARu1mwqoNFS5mzra-4zmS_0WYotf7CKSKDoZ2fjC3BSEUGIy-k95Qv1g35Zq0AsfiXwLHXpS0bE=@protonmail.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> <D9E73DDB-71B7-4C56-9A43-43D6C821BDB6@googlemail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
June 10, 2020 3:07 AM, "Klaus K=C3=BCchemann" <maciphone2@googlemail.com>= wrote:=0A=0A>> Am 10.06.2020 um 01:57 schrieb Klaus K=C3=BCchemann <maci= phone2@googlemail.com>:=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: <G= eneric USB 3.0 controller> iomem 0x600000000-0x600000fff irq 0 on acpi0= =0A... :)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f1e2a0cd8a14821aa550b33ce24d8192>