From: "Xianjun Jiao (UGent-imec)" <Xianjun.Jiao@UGent.be>
To: Dave Taht <dave.taht@gmail.com>,
cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] mips goes risc-v
Date: Tue, 9 Mar 2021 13:03:14 +0000 [thread overview]
Message-ID: <fc5c6b29522a49d5ad71c814a4179579@UGent.be> (raw)
In-Reply-To: <CAA93jw4kVkOnrWBv_FdGwyoGVszb-jm6y0-tQczyGKyv=3cwZA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1805 bytes --]
risc-v indeed is getting more and more developers. I also looked into it a lot. In principle, there is a chance that some of the openwifi low level state machines (for low MAC protocol) could be replaced by some simple risc-v cores. -- Just some wild/initial ideas, no resource/action planned yet.
Best regards,
--
Xianjun Jiao
Senior researcher, imec - Gent university
210.007, floor 11, Technologiepark 126, 9052, Ghent, Belgium
________________________________
From: Dave Taht <dave.taht@gmail.com>
Sent: Tuesday, March 9, 2021 4:42:24 AM
To: cerowrt-devel
Subject: mips goes risc-v
https://hardware.slashdot.org/story/21/03/08/2117238/mips-technologies-joins-risc-v-moves-to-open-source-isa-standard
To me my biggest kvetch about the risc-v effort was the lack of
additional on-chip IP support, which,
lacking compatible busses and so on, was going to limit multiple
generations of chips to just what could be developed afresh. Even
"simple" IP blocks like usb support take time. While I really like
"chisel" as a design language, it is far behind what arm and intel
use. But: With the mips licensees scrambling to reuse their IP,
somehow, and move to risc-v, I think this architecture has an ever
increasing chance of success.
It's been a really good couple of months for open source this or that.
I keep hoping someone will seriously fund
https://github.com/open-sdr/openwifi as well, for, in order to handle
the complexities of 802.11n and beyond, a co-processor with some
serious oomph, and a well designed piece of open firmware, is needed.
--
"For a successful technology, reality must take precedence over public
relations, for Mother Nature cannot be fooled" - Richard Feynman
dave@taht.net <Dave Täht> CTO, TekLibre, LLC Tel: 1-831-435-0729
[-- Attachment #2: Type: text/html, Size: 4875 bytes --]
next prev parent reply other threads:[~2021-03-09 13:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-09 3:42 Dave Taht
2021-03-09 13:03 ` Xianjun Jiao (UGent-imec) [this message]
2021-03-09 15:10 ` 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/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=fc5c6b29522a49d5ad71c814a4179579@UGent.be \
--to=xianjun.jiao@ugent.be \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/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