9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Don Bailey <don.bailey@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] RPi in QEMU
Date: Fri, 1 Sep 2023 23:25:54 -0400	[thread overview]
Message-ID: <CAL_X0tDKeqet=ta8FEeohK73J23rZXzXJo-4Hz0ZiduLbu1=CQ@mail.gmail.com> (raw)
In-Reply-To: <CAL_X0tBBnQoT0Q3WekjOpbQ_qGHtX3b2tqftO7feDg27j45RaQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2302 bytes --]

Ok I pulled a 9legacy ISO, applied your patch set from this thread above,
and built a 9pi2 kernel. My build now runs as the kernel on a QEMU
raspi2b system.

I didn't realize 9legacy actually had a distribution for some reason I
thought it was only a patch set applied against the old main line. Glad I
don't have to pick apart the patch set that (works)...

It looks like on boot with both the kernel you built and my kernel (the
sizes are different so I presume you added on things in a custom config?)
the system loads into the GUI but then hangs moments later and stops
updating the frame buffer, or the system is hung. Any thoughts on why that
might have occurred? Is this to do with the watchdog...?

Thanks, this is excellent and useful.
D


On Fri, Sep 1, 2023 at 10:01 PM Don Bailey <don.bailey@gmail.com> wrote:

> Yeah it must be patches in 9legacy.... because pulling the bcm from
> contrib and using that does not alone fix the kernel.
>
> Interestingly, I can get a kernel to boot in a raspi1ap emulated image,
> but it faults on what I presume is the jump to userland, resets, and
> auto-boots the kernel again in an infinite loop. I cannot get raspi2b to
> boot at all (same deadlock as before).
>
> The thing about 9legacy is I'm not sure what patches to pull and what is
> or isn't stable.... do you have any recommendations?
>
> Thanks again,
> D
>
>
> On Fri, Sep 1, 2023 at 3:38 PM Richard Miller <9fans@hamnavoe.com> wrote:
>
>> > 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-M0fe94460eed29c4f77883688
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

[-- Attachment #2: Type: text/html, Size: 4064 bytes --]

  reply	other threads:[~2023-09-02  3:26 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
2023-09-02  2:01                     ` Don Bailey
2023-09-02  3:25                       ` Don Bailey [this message]
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='CAL_X0tDKeqet=ta8FEeohK73J23rZXzXJo-4Hz0ZiduLbu1=CQ@mail.gmail.com' \
    --to=don.bailey@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).