Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: John Crispin <john@phrozen.org>
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] starlink wifi router sources
Date: Mon, 19 Jul 2021 22:11:20 +0200	[thread overview]
Message-ID: <443e04a4-dc01-cf97-7374-a924d59e0b09@phrozen.org> (raw)
In-Reply-To: <CAA93jw50KPR-g_DLHAaCzmprcbf=7qeLpG+EhG+JsA+Wx7kj5Q@mail.gmail.com>


On 19.07.21 19:50, Dave Taht wrote:
> This just in: 
> https://github.com/SpaceExplorationTechnologies/starlink-wifi Had I 
> known this existed that would have tempered my outrage on the FLOSS 
> show a little bit. 
Moin,

initial scan of the tree ...

CONFIG_TARGET_ipq806x_QSDK_Premium=y
CONFIG_GCC_VERSION_4_8_LINARO=y  (the 90's called, they want their gcc 
back)

CONFIG_PACKAGE_wnc-hal=y --> winstron appears to be the TW based ODM

CONFIG_LINUX_4_4=y

# stat qca/src/linux-4.4/

/src$ diff -urN stable.4.4.60.git/ starlink-linux.4.4.60/ | wc -l
622648

this appears to be a patched version of qsdk 11.2 or 11.3 SFP based upon 
a pre-historic owrt 15.05

CONFIG_PACKAGE_kmod-qca-wifi-minimal-profile=m using the qsdk wifi driver

funnily there is no package/base-files/ in the tree and grep'ing for 
"init.d" in the tree yields no promising results.
leaning out the window, the GPL drop appears to be incomplete.

     John



      reply	other threads:[~2021-07-19 20:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-19 17:50 Dave Taht
2021-07-19 20:11 ` John Crispin [this message]

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/starlink.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=443e04a4-dc01-cf97-7374-a924d59e0b09@phrozen.org \
    --to=john@phrozen.org \
    --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