From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] release candidate
Date: Sat, 17 Jul 2021 02:09:37 +0200 [thread overview]
Message-ID: <CAEAEFBFF1528344AA4950CEB3309C19@felloff.net> (raw)
In-Reply-To: <86B08BFCE9B22713EE95F68E0AB28576@smtp.pobox.com>
> 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
next prev parent reply other threads:[~2021-07-17 0:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-15 20:15 cinap_lenrek
2021-07-16 4:47 ` unobe
2021-07-16 5:40 ` Rodrigo G. López
2021-07-16 6:04 ` unobe
2021-07-16 8:24 ` theinicke
2021-07-16 8:36 ` cinap_lenrek
2021-07-16 19:47 ` unobe
2021-07-17 0:09 ` cinap_lenrek [this message]
2021-07-17 0:52 ` unobe
2021-07-16 8:41 ` cinap_lenrek
2021-07-16 9:21 ` Kurt H Maier
2021-07-16 14:10 ` [9front] German changelog and stuff (was: release candidate) sirjofri
2021-07-16 14:47 ` Stanley Lieber
2021-07-16 17:35 ` hiro
2021-07-16 18:16 ` ori
2021-07-17 3:08 ` Eli Cohen
2021-07-17 4:59 ` Alexander Shendi
2021-07-17 5:16 ` Eli Cohen
2021-07-17 13:35 ` cinap_lenrek
2021-07-16 19:42 ` [9front] release candidate unobe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAEAEFBFF1528344AA4950CEB3309C19@felloff.net \
--to=cinap_lenrek@felloff.net \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).