From: Skip Tavakkolian <skip.tavakkolian@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] Plan9 on Raspberry Pi 400?
Date: Sat, 16 Jan 2021 13:24:09 -0800 [thread overview]
Message-ID: <CAJSxfmLOTxaHh46e5WGoV+QeVpofctOzCzn_B5TF+9UkY4OUdA@mail.gmail.com> (raw)
In-Reply-To: <c107175e8cadce82f0acf564bb6978a9@hamnavoe.com>
[-- Attachment #1: Type: text/plain, Size: 1392 bytes --]
regarding /dev/serial, this should be helpful for anyone wanting to set up
netboot.
If you have a number of RPI's that netboot, the way that the common
config.txt is segmented for each board is by using the '[serial number in
hex]' section headers. Unfortunately, netboot also requires changing the
BOOT_ORDER parameter in EEPROM, which requires access to /dev/mmcblk* and
some way of generating the proper .bin format. So Linux is still needed for
the initial setup.
On Sat, Jan 16, 2021 at 9:13 AM Richard Miller <9fans@hamnavoe.com> wrote:
> > I didn't realise the 9pi image was not up to date.
> > I'll put a new one on 9p.io today.
>
> I've done that. Sorry for letting it get out of sync with the kernel
> source.
>
> The new contrib/miller/9pi.img.gz has
> - the latest firmware files from the raspberry pi github
> - the update to initialise xhci firmware for pi400 and recent pi4 boards
> - a tweak to the pi4 gigabit ethernet driver to allow jumbo packets
> - a new /dev/serial device from which you can read the board serial number
> (I forget why)
>
> Nothing outside the kernel has changed from the previous image.
>
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Tfcf12cca3a14dc8a-Mc3da71e0e76edae80cc21b17
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #2: Type: text/html, Size: 2745 bytes --]
next prev parent reply other threads:[~2021-01-16 21:24 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-16 17:12 Richard Miller
2021-01-16 21:24 ` Skip Tavakkolian [this message]
2021-01-16 22:14 ` Bakul Shah
2021-01-17 7:11 ` Skip Tavakkolian
-- strict thread matches above, loose matches on Subject: below --
2021-01-14 21:34 Mack Wallace
2021-01-14 23:05 ` Stuart Morrow
2021-01-14 23:37 ` Mack Wallace
2021-01-15 1:15 ` Skip Tavakkolian
2021-01-15 18:44 ` Mack Wallace
2021-01-15 19:54 ` Mack Wallace
2021-01-15 21:17 ` Michael Engel
2021-01-15 21:58 ` Stuart Morrow
2021-01-15 22:32 ` Bakul Shah
2021-01-15 22:52 ` Michael Engel
2021-01-16 0:31 ` Mack Wallace
2021-01-16 1:01 ` Michael Engel
2021-01-16 10:24 ` Richard Miller
2021-01-16 11:28 ` Michael Engel
2021-01-18 14:51 ` Richard Miller
2021-01-18 15:42 ` Mack Wallace
2021-01-18 16:54 ` ori
2021-01-19 8:20 ` hiro
2021-01-19 0:54 ` Stuart Morrow
2021-01-19 4:13 ` Lucio De Re
2021-01-19 9:52 ` Richard Miller
2021-01-20 15:25 ` Mack Wallace
2021-01-16 3:03 ` Bakul Shah
2021-01-16 7:19 ` Skip Tavakkolian
2021-01-16 16:15 ` Skip Tavakkolian
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=CAJSxfmLOTxaHh46e5WGoV+QeVpofctOzCzn_B5TF+9UkY4OUdA@mail.gmail.com \
--to=skip.tavakkolian@gmail.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).