From: Nathan Owens <nathan@nathan.io>
To: Nils Andreas Svee <me@lochnair.net>
Cc: Dave Taht <davet@teklibre.net>,
starlink@lists.bufferbloat.net,
Hauke Mehrtens <hauke@hauke-m.de>
Subject: Re: [Starlink] (udm pro) Was: Re: Does the dish run OpenWrt?
Date: Tue, 8 Jun 2021 15:31:24 -0700 [thread overview]
Message-ID: <CALjsLJt8rZZzZ5tNuNVvJB7ZrutOxTqe8BkOoA+uS71Z8DvUcg@mail.gmail.com> (raw)
In-Reply-To: <82e37c76-c116-4fd7-9ec1-4963b1cef843@www.fastmail.com>
[-- Attachment #1: Type: text/plain, Size: 819 bytes --]
Yep, I run the latest code:
Linux Nathan-UDMP 4.19.152-al-linux-v10.2.0-v1.10.0-12.3672-bace201 #1 SMP
Fri May 28 18:00:20 UTC 2021 aarch64 GNU/Linux
At least it has fq_codel now...
On Tue, Jun 8, 2021 at 3:29 PM Nils Andreas Svee <me@lochnair.net> wrote:
> Nice find!
>
> I guess someone finally managed to coax the kernel sources out of them.
> Still nothing on the download page, so I guess you got to reach out to them
> yourself if you'd like a copy.
>
> Are you on the beta firmware that got upgraded to kernel 4.19 Nathan?
> Wouldn't have high expectations of CAKE being enabled, but at least you
> won't have to backport.
>
> Either way the software on those things are a disappointment, so if I ever
> get one it'll be to run OpenWrt on (or just plain Alpine/Debian or similar).
>
> Best Regards
> Nils
>
>
[-- Attachment #2: Type: text/html, Size: 1354 bytes --]
next prev parent reply other threads:[~2021-06-08 22:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <98e5e35f-dcca-0b1c-65c1-3da193779b5f@phrozen.org>
[not found] ` <d7409eb6-e972-ac74-36d0-ea5297c39ad0@hauke-m.de>
[not found] ` <95CC2CF3-6EBB-4F8F-AD2C-58E791459E8D@teklibre.net>
[not found] ` <701613ff-7a53-267f-77d0-a4e015b8410c@hauke-m.de>
[not found] ` <6A2BF4D0-EF5E-4256-AE95-B61F12200BD8@teklibre.net>
2021-06-08 21:52 ` Nathan Owens
2021-06-08 22:29 ` Nils Andreas Svee
2021-06-08 22:31 ` Nathan Owens [this message]
2021-06-08 23:37 ` Dave Taht
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=CALjsLJt8rZZzZ5tNuNVvJB7ZrutOxTqe8BkOoA+uS71Z8DvUcg@mail.gmail.com \
--to=nathan@nathan.io \
--cc=davet@teklibre.net \
--cc=hauke@hauke-m.de \
--cc=me@lochnair.net \
--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