9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Richard Miller <9fans@hamnavoe.com>
To: 9fans@9fans.net
Subject: pi4 firmware update breaks 9pi, and how to fix it
Date: Tue, 17 Dec 2019 15:00:17 +0000	[thread overview]
Message-ID: <381bf5711a2b49e37b4ba4a82046a57e@hamnavoe.com> (raw)

If you're thinking of updating the firmware (fixup*.dat, start*.elf)
on a raspberry pi 4, for example to experiment with the (beta) network
booting support, watch out!  A series of commits by the Pi Foundation
on https://github.com/raspberrypi/firmware in September and October
managed to mess up 9pi in various ways.  The latest firmware (as of
11 December) is better, except that the gic (interrupt controller) is
no longer enabled by default for non-devicetree operating systems.
(This has to be done in secure mode before the OS starts.)

To counteract this, add the parameter 'enable_gic=1' to the pi4
section in config.txt.

I think this won't affect 9front, which uses devicetree, as long
as you update the .dtb files when updating firmware.


                 reply	other threads:[~2019-12-17 15:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=381bf5711a2b49e37b4ba4a82046a57e@hamnavoe.com \
    --to=9fans@hamnavoe.com \
    --cc=9fans@9fans.net \
    /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).