Date: Sat, 25 Apr 2020 20:20:56 +0100 From: Mark Murray <markm@FreeBSD.org> To: greg@unrelenting.technology Cc: Marcel Flores <marcel@brickporch.com>, freebsd-arm@freebsd.org Subject: Re: Bootable image for Macchatobin Double Shot? Message-ID: <B30FC73E-1721-4E3B-9C12-510EE095413D@FreeBSD.org> In-Reply-To: <461d8d1da4ad0c03e0f3a256e4ff4b77@unrelenting.technology> 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> <461d8d1da4ad0c03e0f3a256e4ff4b77@unrelenting.technology>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail=_9495AE25-3A1A-47B8-9E29-DE27C17BDBA8 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi Greg, > On 25 Apr 2020, at 19:01, greg@unrelenting.technology wrote: >=20 > Okay, so for some reason RELEASE builds don't work properly, what the = heck. > Uploaded a working DEBUG build to that URL, > = sha256:86fba8d239e83d87389a641c90d40137a15604a4b1ec0a7a047cb55f58b1e944 It works! It works! Thank you! > now it's actually tested, sorry for being too lazy to test :D No problem. It's very chatty on startup, but that's DEBUG builds for = you. I'm not complaining. > April 25, 2020 7:32 PM, "Mark Murray" <markm@freebsd.org> wrote: >=20 >> Can I help in any way? I'm used to big build (but no good at building = on Windows). >=20 > Windows is not required, the build is not really big either. > Everything builds on FreeBSD (if you patch a couple things to use = gmake instead of make, etc). I could do that! > X86_64 now can actually use clang's native PE output btw. > This hasn't been done for AARCH64 yet, so we still have to rely on the = weird "build-ELF-and-repack" system.. Cool. =46rom where do I clone? >>>>> Also, have you tried any other PCIe cards? >>>>=20 >>>> Nope - 'fraid not :-(. >>>>=20 >>>> My intention is to use this dual-port NIC until (if?) the on-board = NICs are made to work, then I'll >>>> use them and then buy a cheapo PCIe video card to make a proper = console I can use with a KVM >>>> switch. But I need to get the PCI going first :-) >=20 > That's a surprising usage for a mcbin by the way :) Its going to be a combination build-box (occasionally) and = firewall/gateway (permanently on). I'm retiring an old, power-hungry PC and I want a gateway that can do = double-duty as a background buildibox. "Console" here doesn't imply graphics; just enough to do = basic administration. > It's quite expensive for its capabilities, I only bought it because of = pure aarch64 enthusiasm > and desire to have a physical ARM desktop dev box with a working AMD = GPU. I chose it because of its capabilities :-) the price is acceptable. > If I needed something as practical as a console, I would've picked up = some cheap Intel thing > that wouldn't even need an external video card. I also have RPIs, WandBoards and so on, but these aren't much good for = building. Pretty, though! > Also, a USB3 NIC should be more than enough for a console, right? > I recommend axge(4) ASIX chips found in "Nintendo Switch compatible" = dongles. > My mcbin gets ~600 Mbit/s on iperf3 tcp with that thing. Naah. It will be routing DSL broadband for a living. >>>=20 >>> I've started an attempt at porting the onboard NIC driver last = summer: >>> https://github.com/myfreeweb/pepevtwo-kmod >>=20 >> Oooh! Are you amenable to bribery? ;-) >=20 > The lack of knowledge is bigger than the lack of motivation here, = haha. > I'm not really familiar with DMA, iflib (or the more basic kernel API = for NICs), all that stuff. > I basically don't know what I'm doing, my driver dev skills max out at = making tiny > drivers for simple things like watchdogs and fixing stuff in existing = drivers. Aah, OK. I have zero knowledge of that myself. :-( M -- --Apple-Mail=_9495AE25-3A1A-47B8-9E29-DE27C17BDBA8 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.2 Comment: GPGTools - http://gpgtools.org iQEzBAEBCgAdFiEEyzPHvybPbOpU9MCxQlsJDh9CUqAFAl6kjZgACgkQQlsJDh9C UqDhTgf/dN2UwD4Ww8QNb+vwEKiFDBEKW2Try+jeJS1KyQc14NGOKFAIPvqmQR7t 7zViyaYz8CgQCWYj3P3oQ4+oETtJy01BEqkXxHO8jW2bp2QRwu1Pe4AxfXkIOg+9 fMUxAESfd37m3K2MhnxX5KEtY1Ege6Bf0xjLfuSjJkKXYZtds5JYPLG6OUKJsGUa trsIdVjR/hd6YMWMGujP4ondfK9c8ZKpuebgajyrreelTZ4pj1VRurTEgSSFR0tA wtF/B3b0GsIrhGqQkJcn70Ag4wam0G+NSzWLr+Vms+YkpZZ+4CC+YKBlwUAQ+01s iFwj0HGcaf15lnHrjB4HAK0RlSh6Qw== =g5X0 -----END PGP SIGNATURE----- --Apple-Mail=_9495AE25-3A1A-47B8-9E29-DE27C17BDBA8--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B30FC73E-1721-4E3B-9C12-510EE095413D>