Talk:Mapper: Difference between revisions
From NESdev Wiki
Jump to navigationJump to search
(→Allocations: Plane system) |
No edit summary |
||
| Line 5: | Line 5: | ||
::Rule of thumb: once you have final hardware, then you can get a mapper #. Before then, pick something arbitrary and otherwise unusable such as m100, or use UNIF. There's more theoretical possible mappers than there will ever be space for. —[[User:Lidnariq|Lidnariq]] ([[User talk:Lidnariq|talk]]) 14:40, 29 August 2014 (MDT) | ::Rule of thumb: once you have final hardware, then you can get a mapper #. Before then, pick something arbitrary and otherwise unusable such as m100, or use UNIF. There's more theoretical possible mappers than there will ever be space for. —[[User:Lidnariq|Lidnariq]] ([[User talk:Lidnariq|talk]]) 14:40, 29 August 2014 (MDT) | ||
::In the plan as described by KH in the original NES 2.0 doc, 256-511 were to be filled after 0-255 had been filled. Because of the continuing pace of new Chinese discoveries since then, a revised, Unicode-inspired plan splits this into 256-511 for western games and 512-767 for eastern games. Presently, 3840-4095 are reserved for private use, as well as [[iNES Mapper 100|100]] and [[iNES Mapper 248|248]]. --[[User:Tepples|Tepples]] ([[User talk:Tepples|talk]]) 15:34, 29 August 2014 (MDT) | ::In the plan as described by KH in the original NES 2.0 doc, 256-511 were to be filled after 0-255 had been filled. Because of the continuing pace of new Chinese discoveries since then, a revised, Unicode-inspired plan splits this into 256-511 for western games and 512-767 for eastern games. Presently, 3840-4095 are reserved for private use, as well as [[iNES Mapper 100|100]] and [[iNES Mapper 248|248]]. --[[User:Tepples|Tepples]] ([[User talk:Tepples|talk]]) 15:34, 29 August 2014 (MDT) | ||
:::Cool, thanks for the info! This should be helpful to future readers, as well. I found out that blargg is working on a similar project so I'm waiting for a PM response. I also need to get a working NES to test the hardware out on. [[User:Alphamule|alphamule]] ([[User talk:Alphamule|talk]]) 07:42, 30 August 2014 (MDT) | |||
Revision as of 13:42, 30 August 2014
Allocations
By FCEUX 2.2.1, they allocated mapper 160 to describe an undersize NINA-003-006 board (32k PRG, 16k CHR). This seems superfluous. They also allocated mapper 181 to describe another board like iNES Mapper 185 that didn't fit with the existing heuristic. It would be nice to take the opportunity to promote NES 2.0 submappers#iNES Mapper 185. —Lidnariq (talk) 21:41, 23 June 2013 (MDT)
- Also, wasn't 256-511 supposed to be for developers or debugging use? I need to request a reserved number for future hardware designs. I'll probably go find the IRC channel for that. ;) BTW: The documentation for NES 2.0 header format has different allocation planes. It's best to fix this BEFORE someone goes and tries to update/make any mapper code libraries. Again, going to bring this to attention of mods in chat. alphamule (talk) 13:51, 29 August 2014 (MDT)
- Rule of thumb: once you have final hardware, then you can get a mapper #. Before then, pick something arbitrary and otherwise unusable such as m100, or use UNIF. There's more theoretical possible mappers than there will ever be space for. —Lidnariq (talk) 14:40, 29 August 2014 (MDT)
- In the plan as described by KH in the original NES 2.0 doc, 256-511 were to be filled after 0-255 had been filled. Because of the continuing pace of new Chinese discoveries since then, a revised, Unicode-inspired plan splits this into 256-511 for western games and 512-767 for eastern games. Presently, 3840-4095 are reserved for private use, as well as 100 and 248. --Tepples (talk) 15:34, 29 August 2014 (MDT)
