From: Sebastian Moeller <moeller0@gmx.de>
To: cerowrt-devel@lists.bufferbloat.net,
Jonathan Morton <chromatix99@gmail.com>,
David Lang <david@lang.hm>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Looking for MORE SQM Router Recommendations !
Date: Wed, 17 Mar 2021 07:11:25 +0100 [thread overview]
Message-ID: <BDD71A27-D576-401B-9FF4-60993390DDAF@gmx.de> (raw)
In-Reply-To: <CFB9220F-9B89-4CB9-B70A-D448F809C09D@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1441 bytes --]
There is also an io board for the compute module that offers a PCIe slot which might could be used for a real NIC...
On 17 March 2021 03:57:24 CET, Jonathan Morton <chromatix99@gmail.com> wrote:
>> On 17 Mar, 2021, at 3:01 am, David Lang <david@lang.hm> wrote:
>>
>> This is using the compute module, that does not have any on-board
>ports
>
>Actually, the CM4 brings the on-board GigE interface out to the
>connector pins via a suitable PHY. All that is needed is a magjack on
>the carrier. What this particular carrier does is to provide a *twin*
>magjack, wire the appropriate CM4 pins to half of it, and wire the
>other half to a LAN7800 USB-to-GigE adapter. The latter is then wired
>up to the CM4 via a 4-port USB hub chip, so there are also three USB
>ports (one on a header, two as physical ports).
>
>All but the cheapest of the CM4 models also include a single-channel,
>dual-band wifi/BT chip. This requires only an antenna to make it an
>austere but probably usable AP. For better performance, a
>multi-channel wifi adapter could be plugged into the USB header, and
>the cheapest CM4 "Lite" would probably then be sufficient.
>
> - Jonathan Morton
>_______________________________________________
>Cerowrt-devel mailing list
>Cerowrt-devel@lists.bufferbloat.net
>https://lists.bufferbloat.net/listinfo/cerowrt-devel
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
[-- Attachment #2: Type: text/html, Size: 1835 bytes --]
next prev parent reply other threads:[~2021-03-17 6:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1287379027.1155590.1615919208363.ref@mail.yahoo.com>
2021-03-16 18:26 ` Charles Rothschild
[not found] ` <mailman.2387.1615919214.24343.cerowrt-devel@lists.bufferbloat.net>
2021-03-16 22:03 ` [Cerowrt-devel] " Jonathan Morton
2021-03-16 22:04 ` Dave Taht
2021-03-16 22:14 ` Jonathan Morton
2021-03-16 22:58 ` Michael Richardson
2021-03-17 1:01 ` David Lang
2021-03-17 2:57 ` Jonathan Morton
2021-03-17 6:11 ` Sebastian Moeller [this message]
2021-03-17 3:06 ` Matt Taggart
2021-03-17 10:54 ` Toke Høiland-Jørgensen
[not found] ` <mailman.2393.1615978451.24343.cerowrt-devel@lists.bufferbloat.net>
2021-03-19 4:23 ` Aaron Wood
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=BDD71A27-D576-401B-9FF4-60993390DDAF@gmx.de \
--to=moeller0@gmx.de \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=david@lang.hm \
/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