wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: Philipp Richter <richterphilipp.pops@gmail.com>
To: Jason@zx2c4.com
Cc: wireguard@lists.zx2c4.com
Subject: Re: Missing <asm/neon.h> with 0.0.20180904 on arm with kernel 3.10.107
Date: Fri, 7 Sep 2018 09:24:49 +0200	[thread overview]
Message-ID: <CA+Vb7hpM1BBg+nR8shSgg298sLt5+PPmxed9vdrYP3cRF1e9jQ@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9ps967EZUMwL+2Scw=8pSLF16SO2C6bZ+B8LexMb7DqGQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 843 bytes --]

Hello Jason,

yes this works indeed thank you!

This means however that NEON SIMD instructions are not used, right ? The
datasheet of the board mentions that it includes the NEON SIMD coprocessor
: https://dn.odroid.com/S805/Datasheet/S805_Datasheet%20V0.8%2020150126.pdf

And CONFIG_NEON=y is activated in the kernel. Forgive me, I don't know much
about what it means for the wireguard module not using the neon simd
instructions.

Best Regards,
Philipp Richter

*Fingerprint* : *452F 7EBD 2716 B179 5E3E  A2CB AE2B 7FFA CA43 4586*
*PGP Public Key* <https://u.teknik.io/ytoEw.asc>


On Fri, 7 Sep 2018 at 04:47, Jason A. Donenfeld <Jason@zx2c4.com> wrote:

> Hi Philipp,
>
> Thanks for the report. Can you tell me if this fixes it for you?
>
>
> https://git.zx2c4.com/WireGuard/commit/?id=dcb765a453fa22e4195bc42de1792567fe511c67
>
> Jason
>

[-- Attachment #2: Type: text/html, Size: 1820 bytes --]

  reply	other threads:[~2018-09-07  7:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-06 21:00 Missing <asm/neon.h> with 0.0.20180904 on arm with kernel 3.10.107 Philipp Richter
2018-09-07  2:47 ` Jason A. Donenfeld
2018-09-07  7:24   ` Philipp Richter [this message]
2018-09-07 14:22     ` Jason A. Donenfeld
2018-09-08 15:15       ` Philipp Richter

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=CA+Vb7hpM1BBg+nR8shSgg298sLt5+PPmxed9vdrYP3cRF1e9jQ@mail.gmail.com \
    --to=richterphilipp.pops@gmail.com \
    --cc=Jason@zx2c4.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).