Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 19 May 2020 15:24:04 +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:  <d709b1aae3d33f49fadcce9817cb102a@unrelenting.technology>
In-Reply-To: <TLwmTbuqZXh21TMiFjCu96O2fOIoWgPXE-0amhQa7y66As1E39i0v-nC7j1saPpCy8KrT63uE_W92527rywGhtxTKVATtYBSLfrLRdZ3faA=@a9development.com>
References:  <TLwmTbuqZXh21TMiFjCu96O2fOIoWgPXE-0amhQa7y66As1E39i0v-nC7j1saPpCy8KrT63uE_W92527rywGhtxTKVATtYBSLfrLRdZ3faA=@a9development.com> <DpE7TKy0bLe_A7aFUtC16tw_OZ6XPvYOJhEM8-j-SOJfQYEJm9BTewrQ98CR9aW96gTykuslmPHhsaWcyXt26bEw_Zx1vPEwj_IPwKCySUk=@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> <c88780825e96fe583b32adf86416706e@unrelenting.technology>

next in thread | previous in thread | raw e-mail | index | archive | help
May 19, 2020 4:43 PM, "Dan Kotowski" <dan.kotowski@a9development.com> wro=
te:=0A=0A>> Let's try this kernel:=0A>> =0A>> https://send.firefox.com/do=
wnload/37e834fd4c903d80/#UpK-DrJoy-k3OgdA7eZyJg=0A>> =0A>> - SDHCI includ=
ed lol=0A>> - not including the GIC interrupt improvement from https://re=
views.freebsd.org/D24876 - might help=0A>> with ahci interrupts? maybe?=
=0A>> - I2C support (https://reviews.freebsd.org/D24361 + ACPI attachment=
) not that it's urgently needed,=0A>> but why not, that was easy enough, =
I wonder if it would attach or, knowing my luck, crash :D=0A> =0A> Gettin=
g closer...=0A> =0A> dmesg.boot: https://gist.github.com/agrajag9/99d2638=
5be0f49a8a4f046f15a2c0f08=0A=0A"iicbus0: <unknown card> at addr 0x77" nic=
e!=0AWould be great if you could run `i2c -s` also.=0A=0APosted the i2c p=
atch: https://reviews.freebsd.org/D24917=0A=0A>; And still seeing the AHCI=
 interrupt issue=0A=0AOh well, at least we know the GIC patch is innocent=
.=0A=0AAnd at least it's just SATA, no complaints from USB or PCIe.=0A=0A=
Speaking of, looking forward to your testing of PCIe cards ;)=0A=0A> sdhc=
i_acpi0-slot0 seems to have hung the boot process for almost 5min waiting=
 for various timeouts.=0A=0Aoops, so they didn't really make generic sdhc=
i work :D=0A=0AWell turns out we do have a Freescale ESDHC driver already=
.=0AIt doesn't have DMA so performance won't be great (but SD/MMC is bad =
stuff anyway lol).=0A(interesting dev note: NetBSD gets away with just so=
me quirks in the sdhci acpi driver:=0ASDHC_FLAG_HAVE_DVS|SDHC_FLAG_NO_PWR=
0|SDHC_FLAG_32BIT_ACCESS|SDHC_FLAG_ENHANCED)=0A=0ATrying to add ACPI supp=
ort to it:=0A=0Ahttps://send.firefox.com/download/926c72b043182c40/#49y3T=
aeL7_hif_YEHUFQ2g



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