From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
To: Jiaxun Yang <jiaxun.yang@flygoat.com>, qemu-devel@nongnu.org
Cc: Aleksandar Rikalo <aleksandar.rikalo@syrmia.com>,
Huacai Chen <chenhuacai@kernel.org>,
Aurelien Jarno <aurelien@aurel32.net>,
Wainer dos Santos Moschetta <wainersm@redhat.com>,
Cleber Rosa <crosa@redhat.com>
Subject: Re: [PATCH v3 0/8] hw/mips/fuloong2e fixes
Date: Sun, 3 Jan 2021 21:51:48 +0100 [thread overview]
Message-ID: <d7a6b3e7-d0fb-e559-486d-259b5aab74b9@amsat.org> (raw)
In-Reply-To: <20201224031750.52146-1-jiaxun.yang@flygoat.com>
On 12/24/20 4:17 AM, Jiaxun Yang wrote:
> It can now boot Debian installer[1] as well as a custom PMON bootloader
> distribution[2].
>
> Note that it can't boot PMON shipped with actual machine as our ATI vgabios
> is using some x86 hack that can't be handled by x86emu in original PMON.
>
>
> Tree avilable at: https://gitlab.com/FlyGoat/qemu/-/tree/fuloong_fixes_v2
>
> v2:
> - Collect review tags.
> - Get CPU clock via elegant method. (philmd)
> - Add boot_linux_console scceptance test
>
> v3:
> - Collect review tags
> - Typo corrections
> - Rewrite PCI Lomem
>
> Jiaxun Yang (8):
> hw/mips/fuloong2e: Remove define DEBUG_FULOONG2E_INIT
> hw/mips/fuloong2e: Relpace fault links
> hw/pci-host/bonito: Fixup IRQ mapping
> hw/pci-host/bonito: Fixup pci.lomem mapping
> hw/mips/fuloong2e: Remove unused env entry
> hw/mips/fuloong2e: Correct cpuclock env
> hw/mips/fuloong2e: Add highmem support
> tests/acceptance: Test boot_linux_console for fuloong2e
>
> hw/mips/fuloong2e.c | 84 +++++++++++++++++---------
> hw/pci-host/bonito.c | 42 ++++---------
> tests/acceptance/boot_linux_console.py | 21 +++++++
> 3 files changed, 89 insertions(+), 58 deletions(-)
Patches 1, 2, 5, 6 and 8 queued to mips-next.
prev parent reply other threads:[~2021-01-03 21:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-24 3:17 [PATCH v3 0/8] hw/mips/fuloong2e fixes Jiaxun Yang
2020-12-24 3:17 ` [PATCH v3 1/8] hw/mips/fuloong2e: Remove define DEBUG_FULOONG2E_INIT Jiaxun Yang
2020-12-24 3:17 ` [PATCH v3 2/8] hw/mips/fuloong2e: Relpace fault links Jiaxun Yang
2020-12-24 3:17 ` [PATCH v3 3/8] hw/pci-host/bonito: Fixup IRQ mapping Jiaxun Yang
2020-12-24 8:36 ` BALATON Zoltan via
2020-12-24 8:40 ` BALATON Zoltan via
2020-12-25 1:46 ` Jiaxun Yang
2020-12-24 3:17 ` [PATCH v3 4/8] hw/pci-host/bonito: Fixup pci.lomem mapping Jiaxun Yang
2021-01-01 11:07 ` Philippe Mathieu-Daudé
2021-01-01 13:03 ` Jiaxun Yang
2020-12-24 3:17 ` [PATCH v3 5/8] hw/mips/fuloong2e: Remove unused env entry Jiaxun Yang
2020-12-24 8:24 ` BALATON Zoltan via
2021-01-01 18:05 ` Philippe Mathieu-Daudé
2021-01-01 20:51 ` Philippe Mathieu-Daudé
2020-12-24 3:17 ` [PATCH v3 6/8] hw/mips/fuloong2e: Correct cpuclock env Jiaxun Yang
2020-12-24 3:17 ` [PATCH v3 7/8] hw/mips/fuloong2e: Add highmem support Jiaxun Yang
2020-12-24 3:17 ` [PATCH v3 8/8] tests/acceptance: Test boot_linux_console for fuloong2e Jiaxun Yang
2021-01-03 13:35 ` Philippe Mathieu-Daudé
2021-01-03 20:51 ` Philippe Mathieu-Daudé [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=d7a6b3e7-d0fb-e559-486d-259b5aab74b9@amsat.org \
--to=f4bug@amsat.org \
--cc=aleksandar.rikalo@syrmia.com \
--cc=aurelien@aurel32.net \
--cc=chenhuacai@kernel.org \
--cc=crosa@redhat.com \
--cc=jiaxun.yang@flygoat.com \
--cc=qemu-devel@nongnu.org \
--cc=wainersm@redhat.com \
/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).