9front - general discussion about 9front
 help / color / mirror / Atom feed
From: unobe@cpan.org
To: 9front@9front.org
Subject: Re: [9front] release candidate
Date: Fri, 16 Jul 2021 12:47:36 -0700	[thread overview]
Message-ID: <86B08BFCE9B22713EE95F68E0AB28576@smtp.pobox.com> (raw)
In-Reply-To: <DF12B6BD9CC4300F9D0256B774E880BF@felloff.net>

Quoth cinap_lenrek@felloff.net:
> because the raspberry pi4 is sufficiently different
> from the pi3 so it has its own kernel config.
> 
> for example, the pi4 has a built in ethernet controller
> and pci attached xhci.
> 
> also memory addresses for peripherals are quite
> different.
> 
> both pi3 and pi4 are arm64, so they can all share
> the same root filesystem and binaries. but need
> different kernels.

I had never tried using CONF=pi3, but I suppose what is really
controlling which kernel is being used is config.txt which I hadn't
looked at closely until you pointed out the image you build has both
kernels.  So I would have to deliberately copy /arm64/pi3 to pi4 to
mess things up, or change config.txt directly.


  reply	other threads:[~2021-07-16 23:37 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 [this message]
2021-07-17  0:09           ` cinap_lenrek
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=86B08BFCE9B22713EE95F68E0AB28576@smtp.pobox.com \
    --to=unobe@cpan.org \
    --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).