From: Richard Miller <9fans@hamnavoe.com>
To: 9fans@9fans.net
Subject: [9fans] Raspberry Pi 4
Date: Thu, 18 Jul 2019 14:32:06 +0100 [thread overview]
Message-ID: <8deaad266843532118443aaab926902a@hamnavoe.com> (raw)
The 9pi kernel source in /n/sources/contrib/miller/9/bcm on 9p.io has been
updated with (very limited) support for the new pi4.
Reminder: 'srv -nq tcp!9p.io sources /n/sources' to get access to this mirror.
Or point a browser at https://9p.io/sources/contrib/miller/9/bcm
I'm not suggesting anyone should rush out to buy a pi4 just yet. Unlike
previous releases of the board, this incarnation has some very big changes,
so a lot of new driver writing will be needed before it's at all useful
under Plan 9. It's quite daunting actually.
Quoting 9/bcm/words.pi4:
raspberry pi 4 -- work in progress!
broadcom 2838 SoC (based on 2711 cpu)
4 x cortex-a72 (1500Mhz, out-of-order pipeline)
Boots as far as the root prompt, but there are too many new
peripherals without driver support (or documentation so far)
to do anything useful.
- usb host sockets are all connected to new usb3 controller
- sdcard is connected to new emmc controller (can't use sdhost)
- ethernet is connected to new native gbe controller
Wifi is unchanged from 3B+, but currently fails intermittently
with emmc IO_RW_EXTENDED data corruption.
Needs firmware from 5 July 2019 or later.
config.txt for pi4 should include 'core_freq=250' for
the mini-uart console, and 'device_tree=' to ensure that
the loader passes an ATAG list to the kernel instead of
a device tree.
next reply other threads:[~2019-07-18 13:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-18 13:32 Richard Miller [this message]
2019-07-19 9:19 ` hiro
2019-07-19 9:41 ` Richard Miller
2019-07-19 9:45 ` hiro
2019-07-19 9:49 ` Richard Miller
2019-07-25 7:37 cinap_lenrek
2019-07-25 9:15 ` Richard Miller
2019-07-25 9:35 cinap_lenrek
2019-07-25 10:02 ` Richard Miller
2019-07-25 10:04 ` Richard Miller
2019-07-25 11:19 cinap_lenrek
2019-07-25 11:41 cinap_lenrek
2019-08-25 11:09 Richard Miller
2019-09-25 20:58 Richard Miller
2019-09-29 20:32 ` David du Colombier
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=8deaad266843532118443aaab926902a@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).