Date: Tue, 16 Jun 2020 21:57:32 +0000 From: myfreeweb <greg@unrelenting.technology> To: Dan Kotowski <dan.kotowski@a9development.com> Cc: freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: FreeBSD on Layerscape/QorIQ LX2160X Message-ID: <D2780D27-20F4-4706-9956-7E188AD73F62@unrelenting.technology> In-Reply-To: <eRSoUazwekUoXHKtXhs_unN_78Zp3ow_uJ8j-ODdb7mgzz3n8L18wonbrqkmPn2ulVXoUKxHLh8Cc0VU6KMeIEm3X0KsPn8NH-JiqKmq8fI=@a9development.com> References: <NkmJNP_BMdinQ07E7zvRW9EQtYTkHLISOPlALNNcbFXi7d0dsuvgHD2IW73ptiSh1kEml7_VHb9_eTIMaLAIeAici_qpz2UyIrBWzXR4mvE=@a9development.com> <32d1c173d986884efb9b28932c0ead52@unrelenting.technology> <5e1b4bfe845e62bbcd8b827fa37f2b98@unrelenting.technology> <a727f3c05b234218e053c53100b539f0@unrelenting.technology> <KwrTwABcfEzegUc4D8ZsCgFSxouYQIMOa9JoIbpe6d1HInlAX4G0OzdL_d_uug3gifKwFoh1C_EUd5MucQUgtvFy4T0qraW6riyZbje4Mw8=@a9development.com> <cbf5773a03d3c67e133096a0f826274d@unrelenting.technology> <c1788ee7f14b9236e0972909032cb8fd@unrelenting.technology> <940a6099e971e01bd6d04564d0982b9d@unrelenting.technology> <c1e4129989005bc9bfd117988019107d@unrelenting.technology> <XYXpaNQ3XeZR6g5RpmjR3qs56wTKfNi_OpPX53S3yYdPMNMWR0kme-Q7hmNpxzR6EL3DqKxUnG8BcW6ueHv82Kaexu1j4VSLtNtQgYuxX_g=@a9development.com> <eRSoUazwekUoXHKtXhs_unN_78Zp3ow_uJ8j-ODdb7mgzz3n8L18wonbrqkmPn2ulVXoUKxHLh8Cc0VU6KMeIEm3X0KsPn8NH-JiqKmq8fI=@a9development.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On June 16, 2020 9:38:34 PM UTC, Dan Kotowski <dan=2Ekotowski@a9developmen= t=2Ecom> wrote: >> AHCI is looking better and better! >> I'm going to do a little bit of poking at that >> SATA HDD just to see how stable it really is=2E > >Well, it's definitely stable enough for lab use, that's a bonus=2E I caus= ed myself a few headaches by doing stupid things that caused a series of pa= nics, but all are easily attributed to human errata=2E=2E=2E > >Oddly the i2c bus is gone - any ideas what we changed that caused it to d= isappear? > >https://gist=2Egithub=2Ecom/agrajag9/03d9f2f52084ef0ae1e64cbba190e062 > >If I'm reading the DSDT correctly, then it should be hanging right off ac= pi0=2E We can even see it in an older dmesg=2Eboot: > >i2c0: <Vybrid Family Inter-Integrated Circuit (I2C)> iomem 0x2000000-0x20= 0ffff irq 7 on acpi0 > >But now, nothing=2E=2E=2E Probably because I deleted that i2c acpi attachment at some point, because= it didn't seem to actually work=2E=20 >Aside - since the builtin netifs are basically useless for us, any sugges= tions on USB wifi dongles? I tried a few from my parts piles, but all of th= em were unstable Realtek trash=2E I know Atheros chips are usually a good b= et in Linux land - does that hold true in FreeBSD as well? Not sure how common Atheros is on USB=2E=2E Ralink is fine I think? Actual= ly Realtek wifi shouldn't be unusable too=2E=2E For USB Ethernet though, I recommend the "Nintendo Switch compatible" ASIX= chips (axge)=2E By the way, did you get any different firmware builds in the meantime? Tha= t don't have everything suspiciously routed to the SMMU in IORT=2E=2E
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D2780D27-20F4-4706-9956-7E188AD73F62>