Subject: Re: [9front] 9front on spim
Date: Mon, 04 Jul 2022 19:21:58 -0400 [thread overview]
Message-ID: <4838A219717B21C66038618289A970D9@eigenstate.org> (raw)
Quoth adventures in9 <email@example.com>:
> I'll make this a separate thread for anyone who wants to talk about spim
> I saw spim mentioned in the Port Status thread. I haven't had any trouble
> building for spim, and some of the missing parts might just be because it
> is building off code stored in "mips" but does it with with the "spim"
> compiler, which is really just a script with the mips compiler set with a
> little-endian flag.
> As for hardware, I've been using the Onion Omega 2. I've also found
> several Chinese router boards that also use the MT7688. I have got it to
> start booting on the Onion, but haven't finished it up yet. I haven't
> touched it in a couple months, but what I have done so far is here:
> I'm pretty sure the Loongson and Ingenic mips chips are also little endian,
> so there are a few systems out there that would use spim.
> My goal was to use the Onion Omega 2 kits to set up i2c sensors and control
> lights and such around my house. I also got a MT7688 based router, to make
> a 9front based wifi router with. And a MT7621 based router, which is
> similar but dual core.
> So, if anyone wants to help, I do have some little endian mips hardware to
> test on.
Awesome. Please send patches when you're ready!
next prev parent reply other threads:[~2022-07-04 23:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-04 23:15 adventures in9
2022-07-04 23:21 ` ori [this message]
2022-07-05 0:00 ` Frank D. Engel, Jr.
2022-07-05 0:40 ` adventures in9
2022-07-05 10:08 ` Frank D. Engel, Jr.
2022-07-05 0:11 ` Lyndon Nerenberg (VE7TFX/VE6BBM)
[not found] ` <CAPfmpJCxTjii5D5DAOPhYqW7scN=OjKfJ0MsMkFJx6gS_MsLaw@mail.gmail.com>
2022-07-05 1:07 ` Fwd: " adventures in9
2022-07-05 19:56 ` Lyndon Nerenberg (VE7TFX/VE6BBM)
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).