From: Richard Miller <9fans@hamnavoe.com>
To: 9fans@9fans.net
Subject: Re: [9fans] RPi in QEMU
Date: Fri, 1 Sep 2023 20:37:20 +0100 [thread overview]
Message-ID: <96c54f12e16b3628266d3a3b7a577bdc@hamnavoe.com> (raw)
In-Reply-To: <CAL_X0tCqV4YqY-O+Rm4LbgpdjWS0ApJenY+TdqS+VeaZG1XQ5g@mail.gmail.com>
> Based on the diffs you supplied, it looks like my bcm
> sources (from the latest r4 ISO) are not the same as yours. I don't use
> 9front. What is the best way to make sure my bcm (and 9) kernel trees are
> the same as your current tree?
A lot has changed in the bcm kernel since the 4th edition ISO, because
of the release of newer Raspberry Pi models. Current source is in
contrib/miller/9/bcm - just copy those files into /sys/src/9/bcm (or use
the 9legacy ISO instead, which is kept up to date and has other useful
patches too).
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T5da5467097e4eab2-Me83a2442fc4a034b67c85cec
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2023-09-01 19:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-26 4:22 Don Bailey
2023-08-26 9:23 ` Philip Silva via 9fans
2023-08-26 11:39 ` hiro
2023-08-26 10:44 ` mkf
2023-08-26 11:48 ` hiro
2023-08-26 12:52 ` Philip Silva via 9fans
2023-08-26 19:38 ` Don A. Bailey
2023-08-31 18:47 ` Richard Miller
2023-09-01 2:11 ` Don Bailey
2023-09-01 8:18 ` Richard Miller
2023-09-01 8:47 ` fgergo
2023-09-01 8:56 ` quiekaizam via 9fans
2023-09-01 14:06 ` Richard Miller
2023-09-01 15:38 ` Don Bailey
2023-09-01 19:37 ` Richard Miller [this message]
2023-09-02 2:01 ` Don Bailey
2023-09-02 3:25 ` Don Bailey
2023-09-02 8:25 ` hiro
2023-09-02 15:20 ` Richard Miller
2023-09-14 11:52 ` adr via 9fans
2023-09-14 17:11 ` Richard Miller
2023-09-14 17:25 ` adr via 9fans
2023-09-02 15:17 ` Richard Miller
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=96c54f12e16b3628266d3a3b7a577bdc@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).