From: Don Bailey <don.bailey@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] RPi in QEMU
Date: Fri, 1 Sep 2023 11:38:55 -0400 [thread overview]
Message-ID: <CAL_X0tCqV4YqY-O+Rm4LbgpdjWS0ApJenY+TdqS+VeaZG1XQ5g@mail.gmail.com> (raw)
In-Reply-To: <cfd704fc91ed2c2fdc80baea31e81d9e@hamnavoe.com>
[-- Attachment #1: Type: text/plain, Size: 1176 bytes --]
Took a minute to snarf your 9pi2.qemu off of contrib and run it on my
8.0.0... (it wasn't there last night; depends on when 9pio syncs the web
interface, I suppose)
It runs just peachy. 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? I suspect we have a slight deviation that is
enough to cause this kernel not to boot. Otherwise, I've added your changes
to my tree...
Thanks for your time! This is helpful.
D
On Fri, Sep 1, 2023 at 10:07 AM Richard Miller <9fans@hamnavoe.com> wrote:
> > I'm using version 8.0.0 of QEMU. What version are you using, Mr. Miller?
>
> I've now reinstalled QEMU from debian unstable, which gives me v8.0.4.
> Using the 9pi2.qemu in my contrib, it still boots for me, without any
> loop at 0xffff000c.
>
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T5da5467097e4eab2-Mee8ae1299edb6dfc07f4cdf4
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #2: Type: text/html, Size: 2496 bytes --]
next prev parent reply other threads:[~2023-09-01 15:39 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 [this message]
2023-09-01 19:37 ` Richard Miller
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=CAL_X0tCqV4YqY-O+Rm4LbgpdjWS0ApJenY+TdqS+VeaZG1XQ5g@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).