From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 7815 invoked from network); 17 Jul 2021 00:32:37 -0000 Received: from 1ess.inri.net (216.126.196.35) by inbox.vuxu.org with ESMTPUTF8; 17 Jul 2021 00:32:37 -0000 Received: from duke.felloff.net ([216.126.196.34]) by 1ess; Fri Jul 16 20:09:46 -0400 2021 Message-ID: Date: Sat, 17 Jul 2021 02:09:37 +0200 From: cinap_lenrek@felloff.net To: 9front@9front.org In-Reply-To: <86B08BFCE9B22713EE95F68E0AB28576@smtp.pobox.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: advanced responsive metadata TOR over HTTP software-oriented map/reduce manager Subject: Re: [9front] release candidate Reply-To: 9front@9front.org Precedence: bulk > So I would have to deliberately copy /arm64/pi3 to pi4 to > mess things up, or change config.txt directly. what? theres no pi3 or pi4 file in /arm64. the kernel files are named /arm64/9pi3 and /arm64/9pi4. why would you override them with each other? that doesnt make any sense. the pi3 kernel is for the raspberry pi 3. and the pi4 kernel is for raspberry pi 4. a raspberry pi 3 wont work with the pi 4 kernel. and the raspberry pi 4 wont work with the pi 3 kernel. both files are build in the images. the same as with the 32 bit pi image, which has kernels for pi1, and pi2. the raspi's bootloader allows you to specify different kernel files for each model by using different sections in the ini file. all this is documented on the raspberry pi site, this is out of scope for us to document their bootloader configuration. -- cinap