From: BALATON Zoltan <balaton@eik.bme.hu>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>,
qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [RFC PATCH 0/5] ppc/Pegasos2 VOF
Date: Thu, 10 Jun 2021 12:04:59 +0200 (CEST) [thread overview]
Message-ID: <b87683ec-675f-51d5-e3cb-f4f932fb2ba8@eik.bme.hu> (raw)
In-Reply-To: <YMHMbVo2zrV6EsZ8@yekko>
On Thu, 10 Jun 2021, David Gibson wrote:
> On Thu, Jun 10, 2021 at 05:14:45PM +1000, Alexey Kardashevskiy wrote:
>>
>>
>> On 6/9/21 20:28, BALATON Zoltan wrote:
>>> On Wed, 9 Jun 2021, Alexey Kardashevskiy wrote:
>>>> On 6/7/21 01:46, BALATON Zoltan wrote:
>>>>> Based-on: <20210520090557.435689-1-aik@ozlabs.ru>
>>>>> ^ That is v20 of Alexey's VOF patch
>>>>>
>>>>> Hello,
>>>>>
>>>>> Posting these for early review now. I plan to rebase on the next VOF
>>>>> patch that hopefully fixes those points that I had to circumvent in
>>>>> patch 1 for now. I've reported these before but now all of those that
>>>>> are needed for pegasos2 are in one place. Other points I've reported
>>>>> could be clean ups but not sttictly needed.
>>>>>
>>>>> With this series on top of VOF v20 I can now boot Linux and MorphOS on
>>>>> pegasos2 without needing a firmware blob so I hope this is enough to
>>>>> get this board in 6.1 and also have it enabled so users can start
>>>>> using it. That means that VOF will also be merged by then. This now
>>>>> gives VOF another use case that may help it getting finished.
>>>>>
>>>>> I've also updated my development tree with this series here:
>>>>>
>>>>> https://osdn.net/projects/qmiga/scm/git/qemu/tree/pegasos2/
>>>>>
>>>>> Please review so I can do any needed changes together with the rebase
>>>>> on next VOF patch so we don't miss 6.1 this time.
>>>>
>>>>
>>>> It would help if you provided the disk or/and kernel or/and
>>>> initramdisk images and the example command line to give this a try.
>>>> And said a few words who is this Pegasos2 guy :) The series looks ok
>>>> to me otherwise. Thanks,
>>>
>>> These were in the original series adding this board:
>>>
>>> https://patchew.org/QEMU/cover.1616680239.git.balaton@eik.bme.hu/
>>
>>
>> Ah ok. Thanks!
>>
>>
>>> For testing I've used the kernel from debian 8.11.0 powerpc iso which is
>>> known to work on real hardware and MorphOS demo iso available from
>>> www.morphos-team.net. For debian look into install/pegasos to find the
>>> right vmlinuz-chrp.initrd kernel, for MorphOS use the boot.img from root
>>> of the iso as -kernel.
>>>
>>> What's still missing is some rtas functions like get-time-of-day. Are
>>> these any kind of standard and is there a doc about their parameters and
>>> returns or I'll heave to find out from kernel sources? I plan to add
>>> these later but not needed to get it boot.
>>
>> pseries guests use what the LoPAPR spec (derived from sPAPR - "server PAPR")
>> describes:
>>
>> https://openpowerfoundation.org/?resource_lib=linux-on-power-architecture-platform-reference
>
> Of course pegasos won't remotely be PAPR, but you could look at how
> the RTAS functions are defined there.
>
> I'm not really sure of the origins of RTAS. It's not in plain
> IEEE1275 (the original OF spec), but the fact pegasos uses it suggests
> it's not purely a PAPR thing, either.
Pegasos is supposed to be a CHRP platform so maybe there's something on it
in that doc, I haven't checked yet but now you mentioned these I should
probably look there.
Thenks,
BALATON Zoltan
next prev parent reply other threads:[~2021-06-10 10:05 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 5/5] ppc/pegasos2: Implement some RTAS functions with VOF BALATON Zoltan
2021-06-06 15:46 ` [RFC PATCH 3/5] target/ppc: Allow virtual hypervisor on CPU without HV 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 1/5] Misc VOF fixes 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-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 [this message]
2021-06-10 10:37 ` David Gibson
2021-06-10 12:33 ` R: " luigi burdo
2021-06-10 12:52 ` BALATON Zoltan
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=b87683ec-675f-51d5-e3cb-f4f932fb2ba8@eik.bme.hu \
--to=balaton@eik.bme.hu \
--cc=aik@ozlabs.ru \
--cc=david@gibson.dropbear.id.au \
--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).