From: Jonathan Bennett <jonathanbennett@hackaday.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: starlink@lists.bufferbloat.net,
cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Starlink] gpl drop on starlink 2 router
Date: Sat, 29 Jan 2022 13:36:11 -0600 [thread overview]
Message-ID: <CAHtUBug5K_1Ag3ksyVNVSBm1bMzH0UuGVQQQBm9ki6xGkz1cnw@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw79QhmN3ub2kNoLQ-bzcFaSxg3v7VeVJGcvzoBandS+vA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 828 bytes --]
https://github.com/SpaceExplorationTechnologies/starlink-wifi-gen2/tree/main/openwrt
instructions there for flashing over jtag. Running your own build is
possible. It looks like lede 17.01, which is ancient these days...
On Sat, Jan 29, 2022, 1:30 PM Dave Taht <dave.taht@gmail.com> wrote:
> I am delighted to see they switched to the mt76 wifi chip. I have not
> poked into it to see what version of openwrt it is,
>
> https://github.com/SpaceExplorationTechnologies/starlink-wifi-gen2
>
>
> --
> I tried to build a better future, a few times:
> https://wayforward.archive.org/?site=https%3A%2F%2Fwww.icei.org
>
> Dave Täht CEO, TekLibre, LLC
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
>
[-- Attachment #2: Type: text/html, Size: 1652 bytes --]
next prev parent reply other threads:[~2022-01-29 19:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-29 19:30 [Cerowrt-devel] " Dave Taht
2022-01-29 19:36 ` Jonathan Bennett [this message]
2022-01-29 21:12 ` Etienne Champetier
Reply instructions:
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAHtUBug5K_1Ag3ksyVNVSBm1bMzH0UuGVQQQBm9ki6xGkz1cnw@mail.gmail.com \
--to=jonathanbennett@hackaday.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=starlink@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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