Date: Wed, 17 Jun 2020 11:44:51 +0000 From: Dan Kotowski <dan.kotowski@a9development.com> To: myfreeweb <greg@unrelenting.technology> Cc: freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: FreeBSD on Layerscape/QorIQ LX2160X Message-ID: <nlhCtVaaZNcHSX1IQln3UFlbo-JhWAUKTEC2KRhemn47vxujuE3kYZafL8qr2za8zYUlGDB1PvnyjrC3YwL5vS7l3S1DFb3d7gMNWr6_oo4=@a9development.com> In-Reply-To: <D2780D27-20F4-4706-9956-7E188AD73F62@unrelenting.technology> References: <NkmJNP_BMdinQ07E7zvRW9EQtYTkHLISOPlALNNcbFXi7d0dsuvgHD2IW73ptiSh1kEml7_VHb9_eTIMaLAIeAici_qpz2UyIrBWzXR4mvE=@a9development.com> <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> <D2780D27-20F4-4706-9956-7E188AD73F62@unrelenting.technology>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > 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. > > > > Well, it's definitely stable enough for lab use, that's a bonus. 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... > > Oddly the i2c bus is gone - any ideas what we changed that caused it to= disappear? > > https://gist.github.com/agrajag9/03d9f2f52084ef0ae1e64cbba190e062 > > If I'm reading the DSDT correctly, then it should be hanging right off = acpi0. We can even see it in an older dmesg.boot: > > i2c0: <Vybrid Family Inter-Integrated Circuit (I2C)> iomem 0x2000000-0x= 200ffff irq 7 on acpi0 > > But now, nothing... > > Probably because I deleted that i2c acpi attachment at some point, becaus= e it didn't seem to actually work. Yes, that would make sense... > > Aside - since the builtin netifs are basically useless for us, any sugg= estions on USB wifi dongles? I tried a few from my parts piles, but all of = them were unstable Realtek trash. 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.. I guess we're going to find out! https://www.thinkpenguin.com/gnu-linux/penguin-wireless-n-usb-adapter-gnu-l= inux-tpe-n150usb > Ralink is fine I think? Actually Realtek wifi shouldn't be unusable too.. While the realtek device I have does move packets, it also likes to emit wa= rnings every few minutes, and it was definitely caused problems during boot= a few times as well. > For USB Ethernet though, I recommend the "Nintendo Switch compatible" ASI= X chips (axge). Hah! I would not have expected that, but I may pick one up as well for the = future - sadly no eth in my office at the moment. > By the way, did you get any different firmware builds in the meantime? Th= at don't have everything suspiciously routed to the SMMU in IORT.. No, not yet. I think he may be a one-man-army over there for a lot of SR's = firmwares and progress has been slow - especially because they're focused s= o much on supporting Linux. Also, is there some good intro documentation for SMMU and IORT? I'm still p= retty new to both Arm and ACPI, and while the spec docs on uefi.org have be= en great reference material, they're a bit challenging to just sit down and= read.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?nlhCtVaaZNcHSX1IQln3UFlbo-JhWAUKTEC2KRhemn47vxujuE3kYZafL8qr2za8zYUlGDB1PvnyjrC3YwL5vS7l3S1DFb3d7gMNWr6_oo4=>