From: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
To: "BALATON Zoltan" <balaton@eik.bme.hu>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Aleksandar Rikalo <aleksandar.rikalo@syrmia.com>,
qemu-block@nongnu.org, Huacai Chen <chenhuacai@kernel.org>,
qemu-devel@nongnu.org,
Wainer dos Santos Moschetta <wainersm@redhat.com>,
Artyom Tarasenko <atar4qemu@gmail.com>,
Cleber Rosa <crosa@redhat.com>, John Snow <jsnow@redhat.com>,
Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [RFC PATCH 0/5] hw/mips: Fix Fuloong2E to boot Linux guest again
Date: Sun, 3 Jan 2021 14:27:42 +0000 [thread overview]
Message-ID: <e6f09fc9-0247-d99d-4823-9cae8f7a568f@ilande.co.uk> (raw)
In-Reply-To: <eb1af512-943e-f65c-d867-3ead1eccb5d5@eik.bme.hu>
On 01/01/2021 23:56, BALATON Zoltan via wrote:
> But Mark still considered that a horrible hack but after looking more closely he also
> found the difficulty of implementing a more faithful emulation so he would accept the
> flag at the end but still wanted registers to be set more consistently matching what
> the data sheet and whatever ideals would dictate. However I've spent a lot of time
> before finding these values that work with all clients and found some of these
> clients have assumptions instead of working in an ideal world following what data
> sheets say and I don't want to make any changes to this now before we also have
> pegasos2 upstreamed so any change can be more throughly tested and I don't have to
> retest everything for every small change just to find something broke,
I'll reply briefly to this: from the latest analysis the part that's missing from
QEMU is the ability to disable/enable PCI BARs. But this is only something that has
come to light during the past week from Guenter's bug reports, as it is now clear the
Gentoo image you were using for a test case (which you also provided to me) was not
sufficient to test the VIA IDE functionality.
I've already said that we can make use of a temporary hack for now, but the patch in
its current form is still not right. I'll send a follow-up again to this thread so it
is in one place for Phil's reference.
ATB,
Mark.
next prev parent reply other threads:[~2021-01-03 14:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-01 23:12 [RFC PATCH 0/5] hw/mips: Fix Fuloong2E to boot Linux guest again Philippe Mathieu-Daudé
2021-01-01 23:12 ` [RFC PATCH 1/5] ide: Make room for flags in PCIIDEState and add one for legacy mode Philippe Mathieu-Daudé
2021-01-01 23:12 ` [RFC PATCH 2/5] via-ide: Fix fuloong2e support Philippe Mathieu-Daudé
2021-01-03 15:14 ` Mark Cave-Ayland
2021-01-03 18:31 ` BALATON Zoltan via
2021-01-01 23:12 ` [RFC PATCH 3/5] hw/pci-host/bonito: Remap PCI "lo" regions when PCIMAP reg is modified Philippe Mathieu-Daudé
2021-01-01 23:19 ` Peter Maydell
2021-01-02 10:44 ` Philippe Mathieu-Daudé
2021-01-02 10:56 ` Philippe Mathieu-Daudé
2021-01-02 11:22 ` BALATON Zoltan via
2021-01-02 13:10 ` Peter Maydell
2021-01-02 14:12 ` BALATON Zoltan via
2021-01-01 23:12 ` [RFC PATCH 4/5] tests/acceptance: Test boot_linux_console for fuloong2e Philippe Mathieu-Daudé
2021-01-01 23:12 ` [RFC PATCH 5/5] tests/integration: Test Fuloong2E IDE drive, run userspace commands Philippe Mathieu-Daudé
2021-01-06 12:49 ` Willian Rampazzo
2021-01-01 23:56 ` [RFC PATCH 0/5] hw/mips: Fix Fuloong2E to boot Linux guest again BALATON Zoltan via
2021-01-03 14:27 ` Mark Cave-Ayland [this message]
2021-01-03 16:04 ` BALATON Zoltan via
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=e6f09fc9-0247-d99d-4823-9cae8f7a568f@ilande.co.uk \
--to=mark.cave-ayland@ilande.co.uk \
--cc=aleksandar.rikalo@syrmia.com \
--cc=atar4qemu@gmail.com \
--cc=aurelien@aurel32.net \
--cc=balaton@eik.bme.hu \
--cc=chenhuacai@kernel.org \
--cc=crosa@redhat.com \
--cc=f4bug@amsat.org \
--cc=jsnow@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-block@nongnu.org \
--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).