From: Gerd Hoffmann <kraxel@redhat.com>
To: BALATON Zoltan <balaton@eik.bme.hu>
Cc: chenhuacai@kernel.org, qemu-devel@nongnu.org,
wainersm@redhat.com, f4bug@amsat.org, crosa@redhat.com
Subject: Re: [PATCH v2 0/8] hm/mips/fuloong2e fixes
Date: Mon, 21 Dec 2020 10:52:08 +0100 [thread overview]
Message-ID: <20201221095208.rmv3pvdy76vj7f7f@sirius.home.kraxel.org> (raw)
In-Reply-To: <b3e15e5d-2ecf-9364-1963-3d6dae5b7b7@eik.bme.hu>
> > To be more specified, our x86emu in PMON can handle i386 real mode,
> > however vgabios-ati uses INT15h when INT10h ax=0x4f01 (Get VESA Mode)
> > is called. And x86emu won't process INT15h properly.
> >
> > My workround[1] is to allow 0x4f01 to be failed in PMON, as ax=0x4f02
> > (Set VESA Mode) do work, it won't be a actual problem.
>
> Adding Gerd who is the vgabios maintainer and added the VESA mode support so
> he knows about this even if no fix is needed but maybe he knows a simple way
> to work around it anyway.
Hmm, memcpy_high() uses int15. memcpy_high() is used to access the
framebuffer, and there isn't a way around it. From a quick scan of the
source code I can't see why "get mode" uses that though. "set mode" will
call it to clear the screen (unless the noclearmem flag is set).
take care,
Gerd
prev parent reply other threads:[~2020-12-21 9:53 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-19 7:12 [PATCH v2 0/8] hm/mips/fuloong2e fixes Jiaxun Yang
2020-12-19 7:12 ` [PATCH v2 1/8] hw/mips/fuloong2e: Remove define DEBUG_FULOONG2E_INIT Jiaxun Yang
2020-12-22 0:26 ` Huacai Chen
2020-12-19 7:12 ` [PATCH v2 2/8] hw/mips/fuloong2e: Relpace fault links Jiaxun Yang
2020-12-19 17:52 ` Philippe Mathieu-Daudé
2020-12-22 0:30 ` Huacai Chen
2020-12-19 7:18 ` [PATCH v2 3/8] hw/pci-host/bonito: Fixup IRQ mapping Jiaxun Yang
2020-12-21 21:06 ` Philippe Mathieu-Daudé
2020-12-19 7:18 ` [PATCH v2 4/8] hw/pci-host/bonito: Fixup pci.lomem mapping Jiaxun Yang
2020-12-21 20:45 ` Philippe Mathieu-Daudé
2020-12-22 0:36 ` Jiaxun Yang
2020-12-22 12:13 ` Philippe Mathieu-Daudé
2020-12-19 7:21 ` [PATCH v2 5/8] hw/mips/fuloong2e: Remove unused env entry Jiaxun Yang
2020-12-22 0:27 ` Huacai Chen
2020-12-22 14:42 ` Philippe Mathieu-Daudé
2020-12-19 7:21 ` [PATCH v2 6/8] hw/mips/fuloong2e: Correct cpuclock env Jiaxun Yang
2020-12-19 18:22 ` Philippe Mathieu-Daudé
2020-12-22 0:28 ` Huacai Chen
2020-12-19 7:23 ` [PATCH v2 7/8] hw/mips/fuloong2e: Add highmem support Jiaxun Yang
2020-12-19 19:02 ` Philippe Mathieu-Daudé
2020-12-21 20:34 ` Philippe Mathieu-Daudé
2020-12-22 1:13 ` Huacai Chen
2020-12-19 7:23 ` [PATCH v2 8/8] tests/acceptance: Test boot_linux_console for fuloong2e Jiaxun Yang
2020-12-19 18:57 ` Philippe Mathieu-Daudé
2020-12-21 21:17 ` Wainer dos Santos Moschetta
2020-12-21 21:35 ` Willian Rampazzo
2020-12-22 0:24 ` Huacai Chen
2020-12-19 12:13 ` [PATCH v2 0/8] hm/mips/fuloong2e fixes BALATON Zoltan via
2020-12-19 12:37 ` Jiaxun Yang
2020-12-19 16:03 ` BALATON Zoltan via
2020-12-21 9:52 ` Gerd Hoffmann [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=20201221095208.rmv3pvdy76vj7f7f@sirius.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=balaton@eik.bme.hu \
--cc=chenhuacai@kernel.org \
--cc=crosa@redhat.com \
--cc=f4bug@amsat.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).