From: Stephen Hemminger <stephen@networkplumber.org>
To: Dave Taht <dave.taht@gmail.com>
Cc: "Toke Høiland-Jørgensen" <toke@toke.dk>,
"Cake List" <cake@lists.bufferbloat.net>,
cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Cake] merlin gains cake support
Date: Wed, 3 Mar 2021 10:44:20 -0800 [thread overview]
Message-ID: <20210303104421.35aeb4e4@hermes.local> (raw)
In-Reply-To: <CAA93jw5==m8ARhZX2KxFjTwAmaFOa9ugrFtyONBfgnN38J_JRw@mail.gmail.com>
On Wed, 3 Mar 2021 09:12:36 -0800
Dave Taht <dave.taht@gmail.com> wrote:
> it was the fact there is a cake port at all that was so exciting, and
> that some broadcom APIs existed, even more so.
>
> On Wed, Mar 3, 2021 at 9:09 AM Toke Høiland-Jørgensen <toke@toke.dk> wrote:
> >
> > Dave Taht <dave.taht@gmail.com> writes:
> >
> > > https://github.com/dtaht/tc-adv/issues/27
> > >
> > > I don't have any of the hardware supported by this firmware lying
> > > around handy... can anyone test?
> >
> > I believe the original reported already tested and confirmed the fix,
> > actually. I have a patch pending for upstream iproute2 which should show
> > up on netdev as soon as vger unclogs...
> >
> > -Toke
>
>
>
I have been using this https://github.com/ttgapers/cakeqos-merlin
for 5 days so far.
prev parent reply other threads:[~2021-03-03 18:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 17:00 [Cerowrt-devel] " Dave Taht
2021-03-03 17:09 ` Toke Høiland-Jørgensen
2021-03-03 17:12 ` Dave Taht
2021-03-03 18:44 ` Stephen Hemminger [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/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=20210303104421.35aeb4e4@hermes.local \
--to=stephen@networkplumber.org \
--cc=cake@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=toke@toke.dk \
/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