Re: building and using modules on arm64 hikey board

On Tue, May 31, 2016 at 1:58 PM, Ard Biesheuvel wrote: > On 31 May 2016 at 22:24, Dmitry Shmidt wrote: >> On Mon, May 30, 2016 at 4:30 AM, Ard Biesheuvel >> wrote: >>> This is likely caused by the fact that the Android

Re: building and using modules on arm64 hikey board

On Tue, May 31, 2016 at 1:58 PM, Ard Biesheuvel wrote: > On 31 May 2016 at 22:24, Dmitry Shmidt wrote: >> On Mon, May 30, 2016 at 4:30 AM, Ard Biesheuvel >> wrote: >>> This is likely caused by the fact that the Android AArch64 toolchain uses >>> -fpic by default. Could you try adding -fno-pic

Re: building and using modules on arm64 hikey board

On 01-06-16 11:01, Arend Van Spriel wrote: > > > On 31-5-2016 22:58, Ard Biesheuvel wrote: >> On 31 May 2016 at 22:24, Dmitry Shmidt wrote: >>> On Mon, May 30, 2016 at 4:30 AM, Ard Biesheuvel >>> wrote: This is likely caused by the fact

Re: building and using modules on arm64 hikey board

On 01-06-16 11:01, Arend Van Spriel wrote: > > > On 31-5-2016 22:58, Ard Biesheuvel wrote: >> On 31 May 2016 at 22:24, Dmitry Shmidt wrote: >>> On Mon, May 30, 2016 at 4:30 AM, Ard Biesheuvel >>> wrote: This is likely caused by the fact that the Android AArch64 toolchain uses -fpic

Re: building and using modules on arm64 hikey board

On 31-5-2016 22:58, Ard Biesheuvel wrote: > On 31 May 2016 at 22:24, Dmitry Shmidt wrote: >> On Mon, May 30, 2016 at 4:30 AM, Ard Biesheuvel >> wrote: >>> This is likely caused by the fact that the Android AArch64 toolchain uses >>> -fpic by

Re: building and using modules on arm64 hikey board

On 31-5-2016 22:58, Ard Biesheuvel wrote: > On 31 May 2016 at 22:24, Dmitry Shmidt wrote: >> On Mon, May 30, 2016 at 4:30 AM, Ard Biesheuvel >> wrote: >>> This is likely caused by the fact that the Android AArch64 toolchain uses >>> -fpic by default. Could you try adding -fno-pic to the

Re: building and using modules on arm64 hikey board

On 31 May 2016 at 22:24, Dmitry Shmidt wrote: > On Mon, May 30, 2016 at 4:30 AM, Ard Biesheuvel > wrote: >> This is likely caused by the fact that the Android AArch64 toolchain uses >> -fpic by default. Could you try adding -fno-pic to the

Re: building and using modules on arm64 hikey board

On 31 May 2016 at 22:24, Dmitry Shmidt wrote: > On Mon, May 30, 2016 at 4:30 AM, Ard Biesheuvel > wrote: >> This is likely caused by the fact that the Android AArch64 toolchain uses >> -fpic by default. Could you try adding -fno-pic to the CFLAGS? > > Actually Arend is using 4.4, and we need to

Re: building and using modules on arm64 hikey board

On Mon, May 30, 2016 at 4:30 AM, Ard Biesheuvel wrote: > This is likely caused by the fact that the Android AArch64 toolchain uses > -fpic by default. Could you try adding -fno-pic to the CFLAGS? Actually Arend is using 4.4, and we need to pull your fix, Ard: commit

Re: building and using modules on arm64 hikey board

On Mon, May 30, 2016 at 4:30 AM, Ard Biesheuvel wrote: > This is likely caused by the fact that the Android AArch64 toolchain uses > -fpic by default. Could you try adding -fno-pic to the CFLAGS? Actually Arend is using 4.4, and we need to pull your fix, Ard: commit

Re: building and using modules on arm64 hikey board

On Mon, 30 May 2016 20:54:33 +0200 Arend van Spriel wrote: > On 30-05-16 13:30, Ard Biesheuvel wrote: > > This is likely caused by the fact that the Android AArch64 toolchain uses > > -fpic by default. Could you try adding -fno-pic to the CFLAGS? > > I did only

Re: building and using modules on arm64 hikey board

On Mon, 30 May 2016 20:54:33 +0200 Arend van Spriel wrote: > On 30-05-16 13:30, Ard Biesheuvel wrote: > > This is likely caused by the fact that the Android AArch64 toolchain uses > > -fpic by default. Could you try adding -fno-pic to the CFLAGS? > > I did only to notice with 'make V=1 ...'

Re: building and using modules on arm64 hikey board

On 30-05-16 13:30, Ard Biesheuvel wrote: > This is likely caused by the fact that the Android AArch64 toolchain uses > -fpic by default. Could you try adding -fno-pic to the CFLAGS? I did only to notice with 'make V=1 ...' that it was already used hence showing up in the compile command line

Re: building and using modules on arm64 hikey board

On 30-05-16 13:30, Ard Biesheuvel wrote: > This is likely caused by the fact that the Android AArch64 toolchain uses > -fpic by default. Could you try adding -fno-pic to the CFLAGS? I did only to notice with 'make V=1 ...' that it was already used hence showing up in the compile command line

Re: building and using modules on arm64 hikey board

This is likely caused by the fact that the Android AArch64 toolchain uses -fpic by default. Could you try adding -fno-pic to the CFLAGS? > On 30 mei 2016, at 12:21, Arend Van Spriel > wrote: > > I got myself an arm64 HiKey board from LeMaker and build an Android

Re: building and using modules on arm64 hikey board

This is likely caused by the fact that the Android AArch64 toolchain uses -fpic by default. Could you try adding -fno-pic to the CFLAGS? > On 30 mei 2016, at 12:21, Arend Van Spriel > wrote: > > I got myself an arm64 HiKey board from LeMaker and build an Android AOSP > image for it (see

building and using modules on arm64 hikey board

I got myself an arm64 HiKey board from LeMaker and build an Android AOSP image for it (see [1]). For development I would like to use CONFIG_MODULES. However, when I try to insmod the build module I get: [ 287.903653] module cfg80211: overflow in relocation type 261 val ffbffc006530 Looking

building and using modules on arm64 hikey board

I got myself an arm64 HiKey board from LeMaker and build an Android AOSP image for it (see [1]). For development I would like to use CONFIG_MODULES. However, when I try to insmod the build module I get: [ 287.903653] module cfg80211: overflow in relocation type 261 val ffbffc006530 Looking