Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 18 May 2020 19:22:22 +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:  <tgkWGU5EYU6JgQBf8OJrBsqIt4KsOjOMva_gEI0MVtVbUrKwrm2DJtmpWoIll5kfk6AWdJG0Agnwn59sUsIu3PInY1528SpdZ3BmjhpBb-4=@a9development.com>
In-Reply-To: <63b4f78ff4ee07359a345bcbc03afeaa@unrelenting.technology>
References:  <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
> Same as in it still says "using DTB"?
>
> I wonder if that's the same weirdness I saw on the RPi4,
> FreeBSD failing acpi_find_table(ACPI_SIG_SPCR) even though the SPCR table
> is present and deciding we don't have ACPI..
>
> You could try my current kernel which has has_acpi hardcoded to true
> (extract into the root of the memstick's ufs partition):
>
> https://send.firefox.com/download/c3d69444ce92d3cf/#AuYrYtDvJWNYbEeJWRX4f=
A

Yes, it does still say "using DTB"

Also, your kernel works! Or at least I'm into the installer. It doesn't see=
 the onboard eMMC in the Partition Editor, but once I have the NVMe gumstic=
k in hand I'll pick back this back up.

Is there a reason that we can't use on the DTBs compiled from SolidRun and =
NXP's sources?



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?tgkWGU5EYU6JgQBf8OJrBsqIt4KsOjOMva_gEI0MVtVbUrKwrm2DJtmpWoIll5kfk6AWdJG0Agnwn59sUsIu3PInY1528SpdZ3BmjhpBb-4=>