From: Finn Thain <fthain@linux-m68k.org>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Hervé Poussineau" <hpoussin@reactos.org>
Cc: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
qemu-devel@nongnu.org, Laurent Vivier <laurent@vivier.eu>
Subject: Re: [PATCH v3 0/8] dp8393x: fixes and improvements
Date: Tue, 13 Jul 2021 17:08:52 +1000 (AEST) [thread overview]
Message-ID: <ea9453bc-d31c-4a8e-608a-e6da9bcbe2e9@linux-m68k.org> (raw)
In-Reply-To: <b6d444e1-eb3e-b21e-d0d6-5e8a5581b623@linux-m68k.org>
[-- Attachment #1: Type: text/plain, Size: 1086 bytes --]
On Mon, 12 Jul 2021, Finn Thain wrote:
> On Sun, 11 Jul 2021, Philippe Mathieu-Daudé wrote:
>
> >
> > > If I'm right that the big_endian flag should go away, commit
> > > b1600ff195 ("hw/mips/jazz: specify correct endian for dp8393x
> > > device") has already taken mainline in the wrong direction and
> > > amounts to churn.
> >
> > We might figure out with a BE guest image, the remove the endian flag.
>
> Yes, it's hard to make progress without a BE guest. However, for testing
> dp8393x we probably don't need a disk image. I think we only need
> working firmware, since the RISC/os firmware appears to implement BOOTP
> and TFTP and appears to contain a SONIC driver.
I think we probably can install RISC/os once the firmware can be made to
work.
The file "RISCos_5.01.iso", found in the Bitsavers archive, contains
several kernel binaries, one of which is "unix.r4030eb_std".
From the "r4030" in its name, and from the symbol names and string
constants it contains, this binary appears to have all the drivers for the
MIPS Magnum 4000.
prev parent reply other threads:[~2021-07-13 7:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-10 17:49 [PATCH v3 0/8] dp8393x: fixes and improvements Philippe Mathieu-Daudé
2021-07-10 17:49 ` [PATCH v3 1/8] dp8393x: Replace address_space_rw(is_write=1) by address_space_write() Philippe Mathieu-Daudé
2021-07-10 21:16 ` Mark Cave-Ayland
2021-07-10 17:49 ` [PATCH v3 2/8] dp8393x: Replace 0x40 magic value by SONIC_REG16_COUNT definition Philippe Mathieu-Daudé
2021-07-10 17:53 ` Philippe Mathieu-Daudé
2021-07-10 21:17 ` Mark Cave-Ayland
2021-07-10 17:49 ` [PATCH v3 3/8] dp8393x: Only shift the device registers mapping by 1 bit Philippe Mathieu-Daudé
2021-07-10 21:23 ` Mark Cave-Ayland
2021-07-10 17:49 ` [PATCH v3 4/8] dp8393x: Store CAM registers as 16-bit Philippe Mathieu-Daudé
2021-07-10 21:24 ` Mark Cave-Ayland
2021-07-10 17:49 ` [PATCH v3 5/8] dp8393x: Migrate registers as array of uint16 Philippe Mathieu-Daudé
2021-07-10 21:25 ` Mark Cave-Ayland
2021-07-10 17:49 ` [PATCH v3 6/8] dp8393x: Store CRC using device configured endianess Philippe Mathieu-Daudé
2021-07-10 21:28 ` Mark Cave-Ayland
2021-07-10 17:49 ` [NOTFORMERGE PATCH v3 7/8] dp8393x: Rewrite dp8393x_get() / dp8393x_put() Philippe Mathieu-Daudé
2021-07-10 21:31 ` Mark Cave-Ayland
2021-07-10 17:49 ` [NOTFORMERGE PATCH v3 8/8] dp8393x: don't force 32-bit register access Philippe Mathieu-Daudé
2021-07-10 21:48 ` Mark Cave-Ayland
2021-07-11 2:08 ` [PATCH v3 0/8] dp8393x: fixes and improvements Finn Thain
2021-07-11 10:33 ` Philippe Mathieu-Daudé
2021-07-12 7:09 ` Finn Thain
2021-07-13 7:08 ` Finn Thain [this message]
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=ea9453bc-d31c-4a8e-608a-e6da9bcbe2e9@linux-m68k.org \
--to=fthain@linux-m68k.org \
--cc=f4bug@amsat.org \
--cc=hpoussin@reactos.org \
--cc=laurent@vivier.eu \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=qemu-devel@nongnu.org \
/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).