-
Notifications
You must be signed in to change notification settings - Fork 15
+ MCGA in no-EGA/VGA mode #17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Summary of Changes
Hello @DnCraptor, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!
This pull request significantly improves the emulation accuracy for MCGA (Multi-Color Graphics Array) when a full EGA/VGA card is not present. It addresses how the emulator reports its display capabilities via BIOS calls and refines the handling of I/O port writes to align with the specific characteristics of MCGA hardware.
Highlights
- MCGA Capability Reporting: I've updated the BIOS interrupt 10h, function 1Ah (Get Display Combination Code) handler in
src/emulator/cpu.cto correctly report MCGA capabilities. When EGA/VGA is not enabled, the emulator will now returnBL=0x05to indicate MCGA support, ensuring compatibility with software that queries display types. - Refined VGA/MCGA Port Handling: In
src/emulator/ports.c, I've adjusted the I/O port write logic for VGA/MCGA. Specifically, writes to ports0x3C4and0x3CEare now ignored if EGA/VGA is not enabled, as these ports are not present in MCGA. Other common VGA ports (like0x3C0,0x3C5-3C9,0x3CF) are now always processed by thevga_portoutfunction, regardless of whether full EGA/VGA is enabled, allowing for proper MCGA-specific register access.
Using Gemini Code Assist
The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.
Invoking Gemini
You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.
| Feature | Command | Description |
|---|---|---|
| Code Review | /gemini review |
Performs a code review for the current pull request in its current state. |
| Pull Request Summary | /gemini summary |
Provides a summary of the current pull request in its current state. |
| Comment | @gemini-code-assist | Responds in comments when explicitly tagged, both in issue comments and review comments. |
| Help | /gemini help |
Displays a list of available commands. |
Customization
To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.
Limitations & Feedback
Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.
You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.
Footnotes
-
Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
The pull request adds support for MCGA video mode. There's a critical issue in the I/O port handling that could lead to incorrect emulation, which has been addressed in the review comments.
| case 0x3C4: // no such ports in MCGA | ||
| case 0x3CE: | ||
| if (!ega_vga_enabled) break; | ||
| case 0x3C0: | ||
| case 0x3C4: | ||
| case 0x3C5: | ||
| case 0x3C6: | ||
| case 0x3C7: | ||
| case 0x3C8: | ||
| case 0x3C9: | ||
| case 0x3CE: | ||
| case 0x3CF: | ||
| if (ega_vga_enabled) | ||
| return vga_portout(portnum, value); | ||
| return vga_portout(portnum, value); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The logic for handling MCGA ports is not entirely correct. MCGA does not have a Sequencer (ports 0x3C4, 0x3C5) or a Graphics Controller (ports 0x3CE, 0x3CF). The current code correctly ignores writes to the index registers 0x3C4 and 0x3CE in MCGA mode, but it incorrectly allows writes to the data registers 0x3C5 and 0x3CF to fall through to vga_portout. This can lead to incorrect emulation behavior. All four of these ports should be ignored when !ega_vga_enabled.
case 0x3C4: // Sequencer registers (not on MCGA)
case 0x3C5:
case 0x3CE: // Graphics Controller registers (not on MCGA)
case 0x3CF:
if (!ega_vga_enabled) {
break;
}
/* fallthrough for EGA/VGA */
case 0x3C0:
case 0x3C5:
case 0x3C6:
case 0x3C7:
case 0x3C8:
case 0x3C9:
case 0x3CF:
return vga_portout(portnum, value);
tested on Space Quest 3 - uses linear VGA mode (MCGA)
tested on SysInfo - shows CGA (EGA/VGA not detected as expected)