Question about which tools to use, bugs, the best way to implement a function, etc should go here. Don't forget to see if your question is answered in the wiki first! When in doubt post here.
abcd1996 wrote:Thanks! I just found the same suggestion on google.
Why are they not doing this for default
From my personal experience, QEMU 2.0+ does this by default on Linux, but all versions of QEMU for Windows default to -vga cirrus, which only supports true color as a 24-bit mode.
You know your OS is advanced when you stop using the Intel programming guide as a reference.
abcd1996 wrote:Thanks! I just found the same suggestion on google.
Why are they not doing this for default
From my personal experience, QEMU 2.0+ does this by default on Linux, but all versions of QEMU for Windows default to -vga cirrus, which only supports true color as a 24-bit mode.
The bpp in mode_info struct is still 24
-vga qxl doesn't work either, 0x118 mode still has bpp24
abcd1996 wrote:The bpp in mode_info struct is still 24
-vga qxl doesn't work either, 0x118 mode still has bpp24
Very common mistake: NEVER, EVER assume video mode numbers.
QEMU with -vga std supports 32-bit modes but the mode number is not 0x118. Asking the BIOS for supported video modes is your homework today. I've written this tutorial on VESA back then. It should clarify things and has example code for reference.
You know your OS is advanced when you stop using the Intel programming guide as a reference.
abcd1996 wrote:The bpp in mode_info struct is still 24
-vga qxl doesn't work either, 0x118 mode still has bpp24
Very common mistake: NEVER, EVER assume video mode numbers.
QEMU with -vga std supports 32-bit modes but the mode number is not 0x118. Asking the BIOS for supported video modes is your homework today. I've written this tutorial on VESA back then. It should clarify things and has example code for reference.
I've read your articles before(many times) , but still assume the mode number because I was lazy. i will do it now