Date: Sat, 25 Apr 2020 18:01:30 +0000 From: greg@unrelenting.technology To: "Mark Murray" <markm@freebsd.org> Cc: "Marcel Flores" <marcel@brickporch.com>, freebsd-arm@freebsd.org Subject: Re: Bootable image for Macchatobin Double Shot? Message-ID: <461d8d1da4ad0c03e0f3a256e4ff4b77@unrelenting.technology> In-Reply-To: <0532198F-B7DE-46A2-B262-6358EE8370E1@FreeBSD.org> References: <0532198F-B7DE-46A2-B262-6358EE8370E1@FreeBSD.org> <ED8A3428-E14A-44F6-85D9-A9EEABD364A7@FreeBSD.org> <E2887392-01E4-4ECC-8D0A-4871657D5F8E@FreeBSD.org> <9F7FB8F8-A29C-4F95-B0BB-CFEFEAFDDD5E@FreeBSD.org> <1039B382-2CA4-4F49-9F95-08BD1386A447@FreeBSD.org> <CA07A9C8-267B-4657-B9D1-1F53B62A969B@brickporch.com> <092721df6b1de3e75820acd32ba1b0e7@unrelenting.technology> <e307725bcba79d7c9e0f122ebce26ff1@unrelenting.technology> <c5b816c0d036e1c40f7f1d49fd76e845@unrelenting.technology>
next in thread | previous in thread | raw e-mail | index | archive | help
Okay, so for some reason RELEASE builds don't work properly, what the hec= k.=0AUploaded a working DEBUG build to that URL,=0Asha256:86fba8d239e83d8= 7389a641c90d40137a15604a4b1ec0a7a047cb55f58b1e944=0A=0Anow it's actually = tested, sorry for being too lazy to test :D=0A=0AApril 25, 2020 7:32 PM, = "Mark Murray" <markm@freebsd.org> wrote:=0A=0A> Can I help in any way? I'= m used to big build (but no good at building on Windows).=0A=0AWindows is= not required, the build is not really big either.=0AEverything builds on= FreeBSD (if you patch a couple things to use gmake instead of make, etc)= .=0A=0AX86_64 now can actually use clang's native PE output btw.=0AThis h= asn't been done for AARCH64 yet, so we still have to rely on the weird "b= uild-ELF-and-repack" system..=0A=0A>>>> Also, have you tried any other PC= Ie cards?=0A>>> =0A>>> Nope - 'fraid not :-(.=0A>>> =0A>>> My intention i= s to use this dual-port NIC until (if?) the on-board NICs are made to wor= k, then I'll=0A>>> use them and then buy a cheapo PCIe video card to make= a proper console I can use with a KVM=0A>>> switch. But I need to get th= e PCI going first :-)=0A=0AThat's a surprising usage for a mcbin by the w= ay :)=0A=0AIt's quite expensive for its capabilities, I only bought it be= cause of pure aarch64 enthusiasm=0Aand desire to have a physical ARM desk= top dev box with a working AMD GPU.=0AIf I needed something as practical = as a console, I would've picked up some cheap Intel thing=0Athat wouldn't= even need an external video card.=0A=0AAlso, a USB3 NIC should be more t= han enough for a console, right?=0AI recommend axge(4) ASIX chips found i= n "Nintendo Switch compatible" dongles.=0AMy mcbin gets ~600 Mbit/s on ip= erf3 tcp with that thing.=0A=0A>> =0A>> I've started an attempt at portin= g the onboard NIC driver last summer:=0A>> https://github.com/myfreeweb/p= epevtwo-kmod=0A> =0A> Oooh! Are you amenable to bribery? ;-)=0A=0AThe lac= k of knowledge is bigger than the lack of motivation here, haha.=0AI'm no= t really familiar with DMA, iflib (or the more basic kernel API for NICs)= , all that stuff.=0AI basically don't know what I'm doing, my driver dev = skills max out at making tiny=0Adrivers for simple things like watchdogs = and fixing stuff in existing drivers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?461d8d1da4ad0c03e0f3a256e4ff4b77>