tepples wrote:Yes, we can deprecate things by consensus.
In such a case, it would be good to note (perhaps with another mapper category!) which mappers got re-assigned.
One could argue that principle
NES2.0 wrote:1.Retain 100% backwards compatibility with existing emulators/ROMs/etc. (*this includes "dirty ROMs" with crap such as "DiskDude!" in the header and other
atrocities*)
precludes this, though. If one really wanted to clean up plane 0, contra NES2principle 1 [hereafter
N2P1]
tepples wrote:So you can either pin-swap it to 87 or just emulate the 101 dump as 140 and call it a day.
I'd think moving toward Register-Transfer language* or a netlist* for mapper descriptions would be superior; there are a good many mappers that are just address-pin swaps (or mirroring-swaps), are there not? (Submappering pinswaps, alternately...but disrecommended.)
lidnariq wrote:Myask wrote:- BIOS ROMs
- 'reserved'/private use mappers (e.g. 100, proposed:248)
- Disk-copier mappers?
Almost all of those are singletons; what's the point it having a category with a single entry?
Classification; navigation; information. Perhaps it is more suited to a database, but...it seems odd that "FDS BIOS", "reserved for private use" and "duplicate pirate baddump" are lumped together.
(Also: What number did the Game Genie ROM have? I keep thinking it had one and got de-allocated, {contra
N2P1} thus, 2 "BIOS"/tool-ROMs. FFE's got 3-5 on the board.)
lidnariq wrote:
I mean this the nicest way I possibly can, but: good luck.
I've already gone through FCEUX/Nestopia/Nintendulator's source to set the icons on nesdevwiki:Mapper[...]There never was a central repository[...]
None of this is meaningfully resolvable without collecting all the hardware.
tepples wrote:lidnariq wrote:"unassigned" and "Needs more info" are two sides of the same coin.
I think "needs more info" was intended to mean "one of the emulators has an implementation of it" or likewise.
Yeah. Am a little sick, sorry. For a number to be assigned, it must have been [decided to be] implemented in an emulator; otherwise there is just the circuitboard un-allocated. So, then, I ask of you, who have done quite a lot of good on mappers from where I've been watching nesdevWiki:RecentChanges...
Mappers 81, 102, 109-111, 122, 127-131, 135, 160-161, 181, 190, 239, 247, 251 are not, then, implemented in any of those, yes?
Also, as of the implementation(s) of NES2.0
when? one could have asserted that the other 14† planes were unassigned, but the tables show the same question-block as plane 0's. I don't know how good NESdev's contact is with other-language internet communities for to see how far this remains true.
Further proposals, then:Category:
- RE-assigned mappers.
- Unassigned Plane 0 Mappers seems like a good category, should one be able to actually nail it down: it is small.
Icons
- the ?-block seems more apropos of "details unknown, but assigned" mapper; a plain SMB brick for "not known-assigned" then? SMB3's if you want to keep similar-hued.
- "authorized claim staked" [SMB-flag?] is also a possible icon-addition, but would see very little use.
- Poison mushroom seems more in-theme for 'bad', but ok.
Do the other categories (those that you did not specifically object to) seem like good ideas to you? That's kind of the point of this, to seek consensus‡.
*
ugh, it's been so long since I did circuit design I had to look up the names of these things
†
Plane 15 being reserved instead
‡Don't s'pose you could auth my fresh wiki-account? It's
bad that, for instance, NES2.0 isn't bluelinked anywhere on Mapper.