Received: from mx1.tetrasec.net (mx1.tetrasec.net [74.117.190.25])
	by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id E0192782C02
	for <~alpine/devel@lists.alpinelinux.org>; Tue, 10 Sep 2019 08:46:06 +0000 (UTC)
Received: from mx1.tetrasec.net (mail.local [127.0.0.1])
	by mx1.tetrasec.net (Postfix) with ESMTP id 111AA9E305B;
	Tue, 10 Sep 2019 08:46:05 +0000 (UTC)
Received: from ncopa-desktop.copa.dup.pw (67.63.200.37.customer.cdi.no [37.200.63.67])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256)
	(No client certificate requested)
	(Authenticated sender: alpine@tanael.org)
	by mx1.tetrasec.net (Postfix) with ESMTPSA id 9D5109E2804;
	Tue, 10 Sep 2019 08:46:03 +0000 (UTC)
Date: Tue, 10 Sep 2019 09:40:14 +0200
From: Natanael Copa <ncopa@alpinelinux.org>
To: Chris Johnson <simplus314159@gmail.com>
Cc: ~alpine/devel@lists.alpinelinux.org
Subject: Re: Raspberry Pi 4 Kernel and Boot
Message-ID: <20190910094014.3dc6b728@ncopa-desktop.copa.dup.pw>
In-Reply-To: <CA+A6k6ef-T=A4=2j7OwxG8F4C7OUguP1d4pn84V9wNkRx33qwg@mail.gmail.com>
References: <CA+A6k6ef-T=A4=2j7OwxG8F4C7OUguP1d4pn84V9wNkRx33qwg@mail.gmail.com>
X-Mailer: Claws Mail 3.17.4 (GTK+ 2.24.32; x86_64-alpine-linux-musl)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Hi!

Thanks for this.

Can you please file an issue on
https://gitlab.alpinelinux.org/alpine/aports/issues with all those
details? It will help us not forget.

Thanks!

-nc

On Mon, 9 Sep 2019 23:54:40 -0500
Chris Johnson <simplus314159@gmail.com> wrote:

>  I have tried running arm64 rpi alpine 3.10.2 on the Raspberry pi 4
> and have found a couple of things that need to be adjusted.
> 
> The 3.10.2 release does not boot becuase it is missing a couple of new
> files required by the Raspberry pi 4. These two files are:
> 
> start4.elf
> fixup4.dat
> 
> They can be retrieved from the official raspberry pi repository:
> 
> https://github.com/raspberrypi/firmware/tree/master/boot
> 
> They go in the top level of the fat32(boot) partition of the 3.10.2
> release. I do not see an aport that can be patched to include these and
> I can not figure out how the releases are generated to create a
> patch.
> 
> The config.txt needs a couple of modifications, arm_control is being
> depreciated, so
> 
> arm_control=0x200 needs to be changed to arm_64bit=1
> 
> and the following needs to be added
> 
> enable_gic=1
> 
> I have tested the above changes, and they allow the raspberry pi 4
> to boot with current release 3.10.2. However, no usb devices work. This
> is because the kernel is not built with the correct defconfig for the
> raspberry pi 4. The new defconfig is:
> 
> bcm2711_defconfig
> 
> I looked at the aport for main/linux-rpi and find it too confusing.
> I created an abuild chroot on a 64-bit arm and tried to build it using
> bcm2711_defconfig but cannot get past patching. The raspberry pi
> specific changes from alpine linux seem to fail when I try to build.
> 
> Could these changes be included in the next release to allow the
> raspberry pi 4 to work?
> 
> Thank you so much for an amazing distro
> 
> Sources of information for changes:
> 
> Raspberry pi 4 on Ubuntu
> https://jamesachambers.com/raspberry-pi-ubuntu-server-18-04-2-installation-guide/
> 
> Raspberry pi 4 on Manjaro relase
> https://www.manjaro.org/download/arm8-raspberry-pi-4-minimal/
> I mounted the fat32 (boot) of the image to see what was going on
> I am currently using this and it works flawlessly
> 
> Official Raspberry pi documentation
> https://www.raspberrypi.org/documentation/configuration/
> specifically
> https://www.raspberrypi.org/documentation/configuration/boot_folder.md