From: Dave Taht <dave.taht@gmail.com>
To: "Xianjun Jiao (UGent-imec)" <Xianjun.Jiao@ugent.be>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] mips goes risc-v
Date: Tue, 9 Mar 2021 07:10:30 -0800 [thread overview]
Message-ID: <CAA93jw41yDvfdQuj7MYMyWK2JZQO59nwbpzCs8_aDr49X_G66g@mail.gmail.com> (raw)
In-Reply-To: <fc5c6b29522a49d5ad71c814a4179579@UGent.be>
I would suggest reaching out to various members of the risc-v consortium
as for their desire for a wifi stack, and/or doing a preso there.
On Tue, Mar 9, 2021 at 5:03 AM Xianjun Jiao (UGent-imec)
<Xianjun.Jiao@ugent.be> wrote:
>
> 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
--
"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
prev parent reply other threads:[~2021-03-09 15:10 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)
2021-03-09 15:10 ` Dave Taht [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=CAA93jw41yDvfdQuj7MYMyWK2JZQO59nwbpzCs8_aDr49X_G66g@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=Xianjun.Jiao@ugent.be \
--cc=cerowrt-devel@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