[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v2 0/8] hm/mips/fuloong2e fixes
|
From: |
Gerd Hoffmann |
|
Subject: |
Re: [PATCH v2 0/8] hm/mips/fuloong2e fixes |
|
Date: |
Mon, 21 Dec 2020 10:52:08 +0100 |
> > 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
- [PATCH v2 5/8] hw/mips/fuloong2e: Remove unused env entry, (continued)
- [PATCH v2 5/8] hw/mips/fuloong2e: Remove unused env entry, Jiaxun Yang, 2020/12/19
- [PATCH v2 6/8] hw/mips/fuloong2e: Correct cpuclock env, Jiaxun Yang, 2020/12/19
- [PATCH v2 7/8] hw/mips/fuloong2e: Add highmem support, Jiaxun Yang, 2020/12/19
- [PATCH v2 8/8] tests/acceptance: Test boot_linux_console for fuloong2e, Jiaxun Yang, 2020/12/19
- Re: [PATCH v2 0/8] hm/mips/fuloong2e fixes, BALATON Zoltan, 2020/12/19