qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: BALATON Zoltan <balaton@eik.bme.hu>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org, qemu-ppc@nongnu.org,
	 Nicholas Piggin <npiggin@gmail.com>,
	 Daniel Henrique Barboza <danielhb413@gmail.com>,
	clg@kaod.org,  philmd@linaro.org,
	Bernhard Beschow <shentey@gmail.com>,
	 Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
	 Rene Engel <ReneEngel80@emailn.de>,
	vr_qemu@t-online.de
Subject: Re: [PATCH v8 2/3] hw/ppc: Add emulation of AmigaOne XE board
Date: Tue, 7 Nov 2023 19:28:43 +0100 (CET)	[thread overview]
Message-ID: <a40d1036-7343-2e38-cd8f-478f3d5c607e@eik.bme.hu> (raw)
In-Reply-To: <CAFEAcA_fcfTcD_bbtgK8W2V65ks9wgChA0gnT=cHjb0fZ48HLQ@mail.gmail.com>

On Tue, 7 Nov 2023, Peter Maydell wrote:
> On Tue, 7 Nov 2023 at 18:21, BALATON Zoltan <balaton@eik.bme.hu> wrote:
>>
>> The AmigaOne is a rebranded MAI Teron board that uses U-Boot firmware
>> with patches to support AmigaOS and is very similar to pegasos2 so can
>> be easily emulated sharing most code with pegasos2. The reason to
>> emulate it is that AmigaOS comes in different versions for AmigaOne
>> and PegasosII which only have drivers for one machine and firmware so
>> these only run on the specific machine. Adding this board allows
>> another AmigaOS version to be used reusing already existing peagasos2
>> emulation. (The AmigaOne was the first of these boards so likely most
>> widespread which then inspired Pegasos that was later replaced with
>> PegasosII due to problems with Articia S, so these have a lot of
>> similarity. Pegasos mainly ran MorphOS while the PegasosII version of
>> AmigaOS was added later and therefore less common than the AmigaOne
>> version.)
>> +    filename = qemu_find_file(QEMU_FILE_TYPE_BIOS, fwname);
>> +    if (!filename) {
>> +        error_report("Could not find firmware '%s'", fwname);
>> +        /* qtest/test-hmp expects to be able to run the machine without -bios */
>> +        if (!qtest_enabled()) {
>> +            exit(1);
>> +        }
>
> You should put the error_report() line inside the if() as well,
> to stop the error line turning up in the logfiles/stdout. This
> is what we do for the various MIPS boards that ordinarily
> need a BIOS blob.

OK, I'll do a v9 then...

Regards,
BALATON Zoltan


  reply	other threads:[~2023-11-07 18:28 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-27 11:54 [PATCH v7 0/3] Add emulation of AmigaOne XE board BALATON Zoltan
2023-10-27 11:54 ` [PATCH v7 1/3] hw/pci-host: Add emulation of Mai Logic Articia S BALATON Zoltan
2023-11-07 18:53   ` Daniel Henrique Barboza
2023-10-27 11:54 ` [PATCH v7 2/3] hw/ppc: Add emulation of AmigaOne XE board BALATON Zoltan
2023-11-07 18:21   ` [PATCH v8 " BALATON Zoltan
2023-11-07 18:25     ` Peter Maydell
2023-11-07 18:28       ` BALATON Zoltan [this message]
2023-11-07 18:40     ` [PATCH v9 " BALATON Zoltan
2023-11-07 18:52       ` Daniel Henrique Barboza
2023-10-27 11:54 ` [PATCH v7 3/3] tests/avocado: Add test for amigaone board BALATON Zoltan
2023-11-07 18:53   ` Daniel Henrique Barboza
2023-10-28 14:52 ` [PATCH v7 0/3] Add emulation of AmigaOne XE board Bernhard Beschow
2023-10-28 18:20   ` BALATON Zoltan
2023-11-06 10:30 ` BALATON Zoltan
2023-11-07  8:50   ` BALATON Zoltan
2023-11-07 14:42     ` BALATON Zoltan
2023-11-07 16:20       ` Daniel Henrique Barboza
2023-11-07 16:41         ` BALATON Zoltan
2023-11-07 17:20 ` Daniel Henrique Barboza
2023-11-07 17:33   ` BALATON Zoltan
2023-11-07 17:42     ` Daniel Henrique Barboza
2023-11-07 17:49       ` BALATON Zoltan
2023-11-07 18:03         ` BALATON Zoltan
2023-11-07 18:14           ` Peter Maydell
2023-11-07 18:18             ` BALATON Zoltan
2023-11-07 18:21               ` Peter Maydell
2023-11-07 18:25       ` BALATON Zoltan
2023-11-07 18:41         ` BALATON Zoltan
2023-11-07 17:44     ` BALATON Zoltan
2023-11-07 18:53 ` Daniel Henrique Barboza

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=a40d1036-7343-2e38-cd8f-478f3d5c607e@eik.bme.hu \
    --to=balaton@eik.bme.hu \
    --cc=ReneEngel80@emailn.de \
    --cc=clg@kaod.org \
    --cc=danielhb413@gmail.com \
    --cc=mark.cave-ayland@ilande.co.uk \
    --cc=npiggin@gmail.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=shentey@gmail.com \
    --cc=vr_qemu@t-online.de \
    /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).