[OpenWrt-Devel] wireguard: unknown relocation: 102 [ARMv7 Thumb-2]

[Jason A. Donenfeld]

On Wed, Jun 10, 2020 at 4:05 AM Rui Salvaterra <rsalvaterra at gmail.com> wrote:
>
> Hi, Jason,
>
> On Wed, 10 Jun 2020 at 10:31, Rui Salvaterra <rsalvaterra at gmail.com> wrote:
> >
> > Good question. :) You're testing in QEMU (which I personally never
> > used), right? I don't know how familiar you are with OpenWrt, but I
> > can surely send you my configuration (it's spread across multiple
> > files, though).
>
> Ok, so this is what I do (on a pristine tree, after cloning the
> buildroot and the packages feed):
>
> First, I change the CPU subtype to neon (sadly, the Armada 385 is
> castrated upstream since the 370 only supports VFPv3-D16 :/).
>
> diff --git a/target/linux/mvebu/cortexa9/target.mk
> b/target/linux/mvebu/cortexa9/target.mk
> index cdd4d86e49..9af3c95d7b 100644
> --- a/target/linux/mvebu/cortexa9/target.mk
> +++ b/target/linux/mvebu/cortexa9/target.mk
> @@ -10,5 +10,5 @@ include $(TOPDIR)/rules.mk
>  ARCH:=arm
>  BOARDNAME:=Marvell Armada 37x/38x/XP
>  CPU_TYPE:=cortex-a9
> -CPU_SUBTYPE:=vfpv3-d16
> +CPU_SUBTYPE:=neon
>  KERNELNAME:=zImage dtbs
>
> Then, I use the attached configuration files. The .config (for
> OpenWrt) in the buildroot, and config-default (for the kernel itself)
> in target/linux/mvebu/cortexa9/.
>
> Let me know if you need anything else!

Eventually I can probably get this building and testing and find some
hardware for this and such. But if you'd like things to move faster,
trying to reproduce the issue in the qemu test suite will result in a
quicker fix.

Jason

_______________________________________________
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel