Date: Mon, 18 May 2020 20:11:00 +0000 From: Dan Kotowski <dan.kotowski@a9development.com> To: "greg@unrelenting.technology" <greg@unrelenting.technology> Cc: John-Mark Gurney <jmg@funkthat.com>, freebsd-arm@freebsd.org Subject: Re: FreeBSD on Layerscape/QorIQ LX2160X Message-ID: <eG5oKZGzo-y7vxv1fxUTT4fqnlao8e3KpGlswwhQtC6u1zPFDbHJ04Xdl6V1_bkqNNUgrAi3Yy8GJErFDyIZ9HB4p0q0lLED-bj_YZCdSVY=@a9development.com> In-Reply-To: <2053cd2299b81860deecc638ef839d1f@unrelenting.technology> References: <tgkWGU5EYU6JgQBf8OJrBsqIt4KsOjOMva_gEI0MVtVbUrKwrm2DJtmpWoIll5kfk6AWdJG0Agnwn59sUsIu3PInY1528SpdZ3BmjhpBb-4=@a9development.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> <2053cd2299b81860deecc638ef839d1f@unrelenting.technology>
next in thread | previous in thread | raw e-mail | index | archive | help
> Cool, please please please post a dmesg tohttps://dmesgd.nycbug.org :) > Done: https://dmesgd.nycbug.org/index.cgi?do=3Dview&id=3D5490 > Created a bug for the ACPI detection issue: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D246552 > Thanks! I'll keep my eyes on that as well. > > Is there a reason that we can't use on the DTBs compiled from SolidRun = and NXP's sources? > > The devicetree uses NXP specific device descriptions (for USB, SATA, PCIe= , all the things) > and FreeBSD doesn't understand them. > > ACPI tables mostly use generic devices descriptions that all operating sy= stems support > out of the box. > > It is technically possible to make a DTB that mostly uses generic nodes a= nd ACPI tables > full of custom vendor nodes, but almost nobody does this. > (Okay, actually, Qualcomm does ACPI with almost all vendor nodes on the W= indows aarch64 laptops :D) > > Generic descriptions are good. ARM systems that work in the "boring" plug= &play way (with standardized > generic devices) are the ideal we all should strive for, so ACPI should a= lways be preferred. > If you're using any DTB on a server/workstation-class system, something h= as gone wrong :) Thanks for the explanataion, it's very helpful.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?eG5oKZGzo-y7vxv1fxUTT4fqnlao8e3KpGlswwhQtC6u1zPFDbHJ04Xdl6V1_bkqNNUgrAi3Yy8GJErFDyIZ9HB4p0q0lLED-bj_YZCdSVY=>