Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 19 May 2020 12:40:07 +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:  <c88780825e96fe583b32adf86416706e@unrelenting.technology>
In-Reply-To: <DpE7TKy0bLe_A7aFUtC16tw_OZ6XPvYOJhEM8-j-SOJfQYEJm9BTewrQ98CR9aW96gTykuslmPHhsaWcyXt26bEw_Zx1vPEwj_IPwKCySUk=@a9development.com>
References:  <DpE7TKy0bLe_A7aFUtC16tw_OZ6XPvYOJhEM8-j-SOJfQYEJm9BTewrQ98CR9aW96gTykuslmPHhsaWcyXt26bEw_Zx1vPEwj_IPwKCySUk=@a9development.com> <-993X5kyX6HEebSKMfqeSWmICCLli6PEFDf82ulKUdk49KTg9sf2u6V_4a8wWQGyFpwtgdXwqvk2kIjFm5u_ZWw6t2qGw5nSV7f-O_96U_g=@a9development.com> <_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> <0012917d629a48e9fcd8589f4f002e1b@unrelenting.technology> <947c2f9bfaad823a2b104b8741502b40@unrelenting.technology>

next in thread | previous in thread | raw e-mail | index | archive | help
May 19, 2020 6:08 AM, "Dan Kotowski" <dan.kotowski@a9development.com> wro=
te:=0A=0A> Booted with the updated UEFI and kernel+modules, new dmesg.boo=
t here:=0A> https://gist.github.com/agrajag9/a9702c04a659784c829a77d969f6=
315c=0A=0ACool, that's about what I was hoping to see.=0A=0A> It looks li=
ke there's a handful of new things there, but unfortunately I still only =
see da0, which=0A> is the installer-imaged sdcard. Any ideas why the eMMC=
 block device isn't showing up?=0A=0ANight coding fail: I added the gener=
ic SDHCI ID to the driver..=0Aon the wrong computer, not the mcbin that I=
 was building the kernel on :D=0A=0A> And I'll pull some drives off my sh=
elves tomorrow to verify the SATA ports.=0A=0Awell with "ahci0: unable to=
 map interrupt" they aren't gonna work..=0A=0ALet's try this kernel:=0A=
=0Ahttps://send.firefox.com/download/37e834fd4c903d80/#UpK-DrJoy-k3OgdA7e=
ZyJg=0A=0A- SDHCI included lol=0A- not including the GIC interrupt improv=
ement from https://reviews.freebsd.org/D24876 - might help with ahci inte=
rrupts? maybe?=0A- I2C support (https://reviews.freebsd.org/D24361 + ACPI=
 attachment) not that it's urgently needed, but why not, that was easy en=
ough, I wonder if it would attach or, knowing my luck, crash :D



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