From: Dave Taht <davet@teklibre.net>
To: Nathan Owens <nathan@nathan.io>
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] dishy's ethernet chips?
Date: Sat, 5 Jun 2021 15:00:17 -0700 [thread overview]
Message-ID: <2640B4F9-A0BD-4537-839D-86694984E8C1@teklibre.net> (raw)
In-Reply-To: <CALjsLJu=qoZhWzGu7rgZw6HB_qN20Ei9Wn2yNndw-P3uqbPsFQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1035 bytes --]
normally they would have just copy/pasted some ethernet IP from some other chipset in their line….
I am curious which ethernet device driver that might be.
I’m not very knowledgable about st’s other chips
> On Jun 5, 2021, at 2:16 PM, Nathan Owens <nathan@nathan.io> wrote:
>
> It’s a custom ST Micro SoC:
>
> https://twitter.com/VirtuallyNathan/status/1331711512533028864?s=20 <https://twitter.com/VirtuallyNathan/status/1331711512533028864?s=20>
>
> https://twitter.com/VirtuallyNathan/status/1331709138276024320?s=20 <https://twitter.com/VirtuallyNathan/status/1331709138276024320?s=20>
>
> On Fri, Jun 4, 2021 at 7:05 PM Dave Taht <davet@teklibre.net <mailto:davet@teklibre.net>> wrote:
> has anyone seen what the ethernet chips on the dishy are?
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net <mailto:Starlink@lists.bufferbloat.net>
> https://lists.bufferbloat.net/listinfo/starlink <https://lists.bufferbloat.net/listinfo/starlink>
[-- Attachment #2: Type: text/html, Size: 2234 bytes --]
next prev parent reply other threads:[~2021-06-05 22:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-05 2:05 Dave Taht
2021-06-05 21:16 ` Nathan Owens
2021-06-05 22:00 ` Dave Taht [this message]
2021-06-06 1:35 ` Jared Mauch
2021-06-06 9:17 ` Dave Taht
2021-06-06 16:10 ` Nick Buraglio
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=2640B4F9-A0BD-4537-839D-86694984E8C1@teklibre.net \
--to=davet@teklibre.net \
--cc=nathan@nathan.io \
--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