From: Tony Arcieri <bascule@gmail.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: Jonathan Beri <jmberi@gmail.com>,
WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Cortex-m support
Date: Tue, 3 Mar 2020 08:14:48 -0800 [thread overview]
Message-ID: <CAHOTMVKcqDKD0hPHh_RM-LijXLbE-V8vBGTb82aPJMDQ+i2F_Q@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9r6Tvc55m1YpX+rdXtx-RO32UgPRTJy4Y76j9E3U2CGeg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 718 bytes --]
On Sat, Feb 29, 2020 at 11:08 PM Jason A. Donenfeld <Jason@zx2c4.com> wrote:
> It's likely our rust implementation well be well-suited for what you
> have in mind.
Looking at wireguard-rs, in its current form it makes a lot of use of
`alloc` (namely `Vec` and `HashMap`) and `std` features (`fs`, `net`,
`sync`).
Getting it working on a Cortex-M would involve extracting a core protocol
implementation which doesn't make use of any of those features as a
library/crate which has no dependencies (or only optional dependencies
which can be switched off with Cargo features) on `alloc` and `std`.
(as it were, I'm also interested in using wireguard-rs this way in a
"heapless" no_std environment)
--
Tony Arcieri
[-- Attachment #1.2: Type: text/html, Size: 1130 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
prev parent reply other threads:[~2020-03-03 23:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-04 20:04 Jonathan Beri
2018-02-16 22:21 ` Jason A. Donenfeld
2018-02-17 15:39 ` Jonathan Beri
2020-02-29 22:20 ` Jonathan Beri
2020-03-01 7:07 ` Jason A. Donenfeld
2020-03-03 16:14 ` Tony Arcieri [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAHOTMVKcqDKD0hPHh_RM-LijXLbE-V8vBGTb82aPJMDQ+i2F_Q@mail.gmail.com \
--to=bascule@gmail.com \
--cc=Jason@zx2c4.com \
--cc=jmberi@gmail.com \
--cc=wireguard@lists.zx2c4.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;
as well as URLs for NNTP newsgroup(s).