Skip to content
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

konami/gticlub.cpp: Split class per hardware configuration, Use set_format for palette format/entries, Separate palette per Video board #11787

Merged
merged 2 commits into from Dec 7, 2023

Conversation

cam900
Copy link
Contributor

@cam900 cam900 commented Nov 27, 2023

No description provided.

…or palette format/entries, Separate palette per Video board
@cam900 cam900 changed the title gticlub.cpp: Split class per hardware configuration, Use set_format for palette format/entries, Separate palette per Video board konami/gticlub.cpp: Split class per hardware configuration, Use set_format for palette format/entries, Separate palette per Video board Nov 28, 2023
Copy link
Member

@cuavas cuavas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry, I made the review comments ages ago, but forgot to submit the review, so they were left pending.

Comment on lines -477 to +515
map(0x74010000, 0x7401ffff).ram().w(FUNC(gticlub_state::paletteram32_w)).share(m_generic_paletteram_32);
m_cg_view[0](0x74010000, 0x7401ffff).ram().w(m_palette[0], FUNC(palette_device::write32)).share("palette1");
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why did you put this into the view? Previously this was overlaying work RAM when the view was disabled, while now it is only active when the view is enabled. Is there a test case where this corrects or improves behaviour?

Comment on lines -498 to +540
m_cg_view[1](0x74000000, 0x740000ff).rw(m_k001604[1], FUNC(k001604_device::reg_r), FUNC(k001604_device::reg_w));
map(0x74010000, 0x7401ffff).ram().w(FUNC(gticlub_state::paletteram32_w)).share(m_generic_paletteram_32);
m_cg_view[0](0x74010000, 0x7401ffff).ram().w(m_palette[0], FUNC(palette_device::write32)).share("palette1");
m_cg_view[0](0x74020000, 0x7403ffff).rw(m_k001604[0], FUNC(k001604_device::tile_r), FUNC(k001604_device::tile_w));
m_cg_view[0](0x74040000, 0x7407ffff).rw(m_k001604[0], FUNC(k001604_device::char_r), FUNC(k001604_device::char_w));
m_cg_view[1](0x74000000, 0x740000ff).rw(m_k001604[1], FUNC(k001604_device::reg_r), FUNC(k001604_device::reg_w));
m_cg_view[1](0x74010000, 0x7401ffff).ram().w(m_palette[1], FUNC(palette_device::write32)).share("palette2");
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here – what’s the basis for only enabling palette 1 writes in view entry 0 now?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

because each video board has independent color RAM, and it fixes hangplt per-screen color palette entries.

src/mame/konami/gticlub.cpp Outdated Show resolved Hide resolved
@cuavas cuavas merged commit ddccb2b into mamedev:master Dec 7, 2023
5 checks passed
Luigi30 pushed a commit to Luigi30/mame that referenced this pull request Dec 16, 2023
mamedev#11787)

* Split up driver state class for different hardware configurations.
* Use palette format utilities.
* Use separate palettes for multiple video boards.
* Only enable palette RAM access when video board is mapped over system RAM.
einstein95 pushed a commit to einstein95/mame that referenced this pull request Mar 2, 2024
mamedev#11787)

* Split up driver state class for different hardware configurations.
* Use palette format utilities.
* Use separate palettes for multiple video boards.
* Only enable palette RAM access when video board is mapped over system RAM.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants