X-Original-To: alpine-user@lists.alpinelinux.org Received: from mail.zandea.com (mail.zandea.com [78.46.49.252]) by lists.alpinelinux.org (Postfix) with ESMTP id 2C69A5C58E6 for ; Sat, 27 Oct 2018 21:15:47 +0000 (GMT) Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.zandea.com (Postfix) with ESMTP id C942E9C604F for ; Sat, 27 Oct 2018 23:15:46 +0200 (CEST) Received: from mail.zandea.com ([127.0.0.1]) by localhost (mail.zandea.com [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id XUh0YTea5WkU for ; Sat, 27 Oct 2018 23:15:46 +0200 (CEST) Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.zandea.com (Postfix) with ESMTP id 5DF849C6056 for ; Sat, 27 Oct 2018 23:15:46 +0200 (CEST) X-Virus-Scanned: amavisd-new at mail.zandea.com Received: from mail.zandea.com ([127.0.0.1]) by localhost (mail.zandea.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 7CbKgynu5wqE for ; Sat, 27 Oct 2018 23:15:46 +0200 (CEST) Received: from [10.222.0.45] (ppp-93-104-75-212.dynamic.mnet-online.de [93.104.75.212]) by mail.zandea.com (Postfix) with ESMTPSA id 16E629C604D for ; Sat, 27 Oct 2018 23:15:45 +0200 (CEST) To: alpine-user@lists.alpinelinux.org From: Florian Frankenberger Subject: [alpine-user] Replacing kernel with custom kernel on Raspberry Pi Message-ID: Date: Sat, 27 Oct 2018 23:15:45 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 X-Mailinglist: alpine-user Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="------------A01A9B6ABC3818DF46C64D8D" This is a multi-part message in MIME format. --------------A01A9B6ABC3818DF46C64D8D Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Hi everyone, I'm trying to get wiringPi working on my RaspberryPi 3. The first=20 problem I stumbled upon is that the wiringPi package is not on version=20 2.46 as described here=20 https://pkgs.alpinelinux.org/package/edge/community/armhf/wiringpi but=20 rather uses a very old version from 2015 which unfortunately does not=20 support the Pi3. This is due to the APKBUILD file for that module which=20 is still using the old commit (5edd177). I managed to upgrade the commit and build a more recent version (2.36).=20 Now my problem is that wiringPi uses mmap to access the BCM's memory to=20 directly control the GPIO ports. When I try to use the wiringPi library=20 I get an "mmap (GPIO) failed: Operation not permitted" as the Kernel was=20 compiled with the CONFIG_STRICT_DEVMEM set to yes (normally a good idea=20 to not give the userspace direct access to memory, but in this case I=20 need it). So I tried to compile a custom Kernel with that flag set to "no" and=20 managed (after some trial and error) to create an apk package. Now I=20 thought I succeeded in my endeavor and entered "apk add=C2=A0=20 linux-vanilla-4.14.78-r0.apk" but that did not work. I know now that the=20 whole /lib/modules directory is on a squashFS filesystem and is read-only= . My question now is: how can I properly replace my kernel with my custom=20 built one? Do I have to create my own squashFS file? But if so how do I=20 get the content of my package into that file (and where is it)? Or is=20 there an easier way to do that? Any hint you can give me is very much appreciated. Thank you! Best, Florian --------------A01A9B6ABC3818DF46C64D8D Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable

Hi everyone,

I'm trying to get wiringPi working on my RaspberryPi 3. The first problem I stumbled upon is that the wiringPi package is not on version 2.46 as described here https://pkgs.alpinelinux.org/= package/edge/community/armhf/wiringpi but rather uses a very old version from 2015 which unfortunately does not support the Pi3. This is due to the APKBUILD file for that module which is still using the old commit (5edd177).

I managed to upgrade the commit and build a more recent version (2.36). Now my problem is that wiringPi uses mmap to access the BCM's memory to directly control the GPIO ports. When I try to use the wiringPi library I get an "mmap (GPIO) failed: Operation not permitted" as the Kernel was compiled with the CONFIG_STRICT_DEVMEM set to yes (normally = a good idea to not give the userspace direct access to memory, but in this case I need it).

So I tried to compile a custom Kernel with that flag set to "no" and managed (after some trial and error) to create an apk package. Now I thought I succeeded in my endeavor and entered "apk add=C2=A0 linux-vanilla-4.14.78-r0.apk"= but that did not work. I know now that the whole /lib/modules directory is on a squashFS filesystem and is read-only.

My question now is: how can I properl= y replace my kernel with my custom built one? Do I have to create my own squashFS file? But if so how do I get the content of my package into that file (and where is it)? Or is there an easier way to do that?

Any hint you can give me is very much appreciated. Thank you!

Best,
Florian
 --------------A01A9B6ABC3818DF46C64D8D-- --- Unsubscribe: alpine-user+unsubscribe@lists.alpinelinux.org Help: alpine-user+help@lists.alpinelinux.org ---