Date: Mon, 18 May 2020 19:44:32 +0000 From: greg@unrelenting.technology To: "Dan Kotowski" <dan.kotowski@a9development.com> Cc: "John-Mark Gurney" <jmg@funkthat.com>, freebsd-arm@freebsd.org Subject: Re: FreeBSD on Layerscape/QorIQ LX2160X Message-ID: <2053cd2299b81860deecc638ef839d1f@unrelenting.technology> In-Reply-To: <tgkWGU5EYU6JgQBf8OJrBsqIt4KsOjOMva_gEI0MVtVbUrKwrm2DJtmpWoIll5kfk6AWdJG0Agnwn59sUsIu3PInY1528SpdZ3BmjhpBb-4=@a9development.com> References: <tgkWGU5EYU6JgQBf8OJrBsqIt4KsOjOMva_gEI0MVtVbUrKwrm2DJtmpWoIll5kfk6AWdJG0Agnwn59sUsIu3PInY1528SpdZ3BmjhpBb-4=@a9development.com> <9UQiT9Df6hGA9k3-pzwpHifFsu7BVL2zFGOqDsnGva556e8nyvrKPp5XnKWxksvEKx1bpD-dnuYw8VCGiP9Z_kHc6tDFJcmRXzeJqLbo-yo=@a9development.com> <20200516051207.GT4213@funkthat.com> <3nsQUg1Gm4VFYfpHVELk6PWaHyYNb3CoyoKnLV55_3VR48tr90bhaseG3sJg007L8czZ4mXUmR_YMQvYVdMbUs1bsoqGtZp5d17FqYT6b-o=@a9development.com> <7AFDA7E0-82EC-4CD2-BB03-B7E33D019EDA@unrelenting.technology> <_lvahpuNQE69s4KpHud6ANL6yzL3RCVI-MTyB0_J_ULyW-3UWsqAXnm5gfoFcOyvfRQRabZk4Z4bQgyp15a001kA-WcvsvnWcjqgMBkgGTY=@a9development.com> <BB317821-62C7-416E-83E6-69101A64E9A3@unrelenting.technology> <cjE8j_Tehwtmk7Aw0hzP-EZxwfAQC4ywIrgcqrarkCiRI_X5kacVsJHpaX_SMO9QHVCqfEdJH45eC4AE2cwzfx9nmHzWbhE7M-h09hDe8MA=@a9development.com> <7F9D7164-2C04-4E27-85F9-A495EAC8FC84@unrelenting.technology> <63b4f78ff4ee07359a345bcbc03afeaa@unrelenting.technology>
next in thread | previous in thread | raw e-mail | index | archive | help
May 18, 2020 10:22 PM, "Dan Kotowski" <dan.kotowski@a9development.com> wr= ote:=0A=0A>> Same as in it still says "using DTB"?=0A>> =0A>> I wonder if= that's the same weirdness I saw on the RPi4,=0A>> FreeBSD failing acpi_f= ind_table(ACPI_SIG_SPCR) even though the SPCR table=0A>> is present and d= eciding we don't have ACPI..=0A>> =0A>> You could try my current kernel w= hich has has_acpi hardcoded to true=0A>> (extract into the root of the me= mstick's ufs partition):=0A>> =0A>> https://send.firefox.com/download/c3d= 69444ce92d3cf/#AuYrYtDvJWNYbEeJWRX4fA=0A> =0A> Yes, it does still say "us= ing DTB"=0A> =0A> Also, your kernel works! Or at least I'm into the insta= ller. It doesn't see the onboard eMMC in the=0A> Partition Editor, but on= ce I have the NVMe gumstick in hand I'll pick back this back up.=0A=0ACoo= l, please please please post a dmesg to https://dmesgd.nycbug.org :)=0A= =0ACreated a bug for the ACPI detection issue:=0Ahttps://bugs.freebsd.org= /bugzilla/show_bug.cgi?id=3D246552=0A=0A> Is there a reason that we can't= use on the DTBs compiled from SolidRun and NXP's sources?=0A=0AThe devic= etree uses NXP specific device descriptions (for USB, SATA, PCIe, all the= things)=0Aand FreeBSD doesn't understand them.=0A=0AACPI tables mostly u= se generic devices descriptions that all operating systems support=0Aout = of the box.=0A=0AIt is technically possible to make a DTB that mostly use= s generic nodes and ACPI tables=0Afull of custom vendor nodes, but almost= nobody does this.=0A(Okay, actually, Qualcomm does ACPI with almost all = vendor nodes on the Windows aarch64 laptops :D)=0A=0AGeneric descriptions= are good. ARM systems that work in the "boring" plug&play way (with stan= dardized=0Ageneric devices) are the ideal we all should strive for, so AC= PI should always be preferred.=0AIf you're using any DTB on a server/work= station-class system, something has gone wrong :)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2053cd2299b81860deecc638ef839d1f>