Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Nathan Owens <nathan@nathan.io>
To: dickroy@alum.mit.edu
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] For all you PHY enthusiasists
Date: Wed, 30 Jun 2021 10:29:13 -0700	[thread overview]
Message-ID: <CALjsLJsgy6DqNVfpsK41xkVVwi3EHptvBpP_TvkrHJDPDw0Agg@mail.gmail.com> (raw)
In-Reply-To: <A718DC25D16B451C924B681991977306@SRA6>

[-- Attachment #1: Type: text/plain, Size: 885 bytes --]

What’s state of the art that isn’t space rated? I assume wayyy more capable
than this thing? The Xilinx Ultrascale+ RFSOC has 16x 2.5GSP ADCs or 8x at
5GSP with 14 bits, and that’s sorta old tech at 16nm.

On Wed, Jun 30, 2021 at 9:01 AM Dick Roy <dickroy@alum.mit.edu> wrote:

> FYI all PHY enthusiasts …
>
>
>
>
> https://www.electronicdesign.com/markets/defense/article/21168402/microwaves-rf-fourchannel-adc-makes-the-grade-for-space?utm_source=EG%20ED%20Today&utm_medium=email&utm_campaign=CPS210625102&o_eid=5487F0022834D6Y&rdx.ident%5Bpull%5D=omeda%7C5487F0022834D6Y&oly_enc_id=5487F0022834D6Y
>
>
>
> This is especially relevant for smart antenna geeks!
>
>
>
> Cheers,
>
>
>
> RR
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
>

[-- Attachment #2: Type: text/html, Size: 3892 bytes --]

  reply	other threads:[~2021-06-30 17:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-30 16:01 Dick Roy
2021-06-30 17:29 ` Nathan Owens [this message]
2021-06-30 18:04   ` Dick Roy

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=CALjsLJsgy6DqNVfpsK41xkVVwi3EHptvBpP_TvkrHJDPDw0Agg@mail.gmail.com \
    --to=nathan@nathan.io \
    --cc=dickroy@alum.mit.edu \
    --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