From: BALATON Zoltan <balaton@eik.bme.hu>
To: luigi burdo <intermediadc@hotmail.com>
Cc: "qemu-ppc@nongnu.org" <qemu-ppc@nongnu.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: R: [RFC PATCH 0/5] ppc/Pegasos2 VOF
Date: Thu, 10 Jun 2021 14:52:51 +0200 (CEST) [thread overview]
Message-ID: <a117c452-ee3b-c3f1-2932-2b1740a71fc@eik.bme.hu> (raw)
In-Reply-To: <AM7PR03MB6579DA01C8834EFD9EFC97F0C8359@AM7PR03MB6579.eurprd03.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1488 bytes --]
On Thu, 10 Jun 2021, luigi burdo wrote:
> i dont know if you know and if in the docs is described the pegasos II can support smp dual G4 cpu.
I think theoretically the Marvell Discovery II chip can support dual CPU
and meybe even a G5, this is described in its docs. However in practice
this was never implemented for Pegasos2 and there was only either a G3 or
G4 single CPU card available for it. It probably does not make much sense
to emulate anything else than the G4 version as that's what has the most
features that guest OSes can use. The current emulation is just enough for
that and I don't plan to implement more of the MV64361 chip to emulate non
existent SMP configs as probably nothing would run on it anyway so it does
not worth the extra effort.
> Here some hystorical info about this great machine from the past Phase 5 A\BOX (kosmoplovci.net)<https://www.kosmoplovci.net/hc/hc4/tech/phase5-abox.html>.
> i remember really good that period (when i was young man)... the caipirinha become one of my best cocktail 🙂
Maybe interesting for history behind Pegasos2 only but otherwise probably
not too relevant to how it was actually implemented at the end which is
what counts if you want to run existing guests OSes. This doc seems to
describe a system that wasn't implemented but instead a similar system was
made from off the shelf components available at the time so for emulation
a better reference are the docs of those chips.
Regards.
BALATON Zoltan
prev parent reply other threads:[~2021-06-10 12:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-06 15:46 [RFC PATCH 0/5] ppc/Pegasos2 VOF BALATON Zoltan
2021-06-06 15:46 ` [RFC PATCH 2/5] ppc/pegasos2: Introduce Pegasos2MachineState structure BALATON Zoltan
2021-06-06 19:04 ` Philippe Mathieu-Daudé
2021-06-06 20:35 ` BALATON Zoltan
2021-06-06 15:46 ` [RFC PATCH 4/5] ppc/pegasos2: Use Virtual Open Firmware as firmware replacement BALATON Zoltan
2021-06-15 7:09 ` Alexey Kardashevskiy
2021-06-15 9:44 ` BALATON Zoltan
2021-06-16 4:58 ` Alexey Kardashevskiy
2021-06-16 10:38 ` BALATON Zoltan
2021-06-06 15:46 ` [RFC PATCH 5/5] ppc/pegasos2: Implement some RTAS functions with VOF BALATON Zoltan
2021-06-06 15:46 ` [RFC PATCH 1/5] Misc VOF fixes BALATON Zoltan
2021-06-06 15:46 ` [RFC PATCH 3/5] target/ppc: Allow virtual hypervisor on CPU without HV BALATON Zoltan
2021-06-09 7:39 ` [RFC PATCH 0/5] ppc/Pegasos2 VOF Alexey Kardashevskiy
2021-06-09 10:28 ` BALATON Zoltan
2021-06-10 7:14 ` Alexey Kardashevskiy
2021-06-10 8:25 ` David Gibson
2021-06-10 10:04 ` BALATON Zoltan
2021-06-10 10:37 ` David Gibson
2021-06-10 12:33 ` R: " luigi burdo
2021-06-10 12:52 ` BALATON Zoltan [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=a117c452-ee3b-c3f1-2932-2b1740a71fc@eik.bme.hu \
--to=balaton@eik.bme.hu \
--cc=david@gibson.dropbear.id.au \
--cc=intermediadc@hotmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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 read-only IMAP folder(s) and NNTP newsgroup(s).