Talk:INES Mapper 150: Difference between revisions
From NESdev Wiki
Jump to navigationJump to search
(→Physical vs. logical ordering: new section) |
(sorta) |
||
| Line 2: | Line 2: | ||
Is this like the difference between [[iNES Mapper 087]] and [[iNES Mapper 101]]/[[iNES Mapper 140|140]], where one is ordered as in the mask ROM and the other as it is presented logically to the program? --[[User:Tepples|Tepples]] ([[User talk:Tepples|talk]]) 21:07, 17 May 2014 (MDT) | Is this like the difference between [[iNES Mapper 087]] and [[iNES Mapper 101]]/[[iNES Mapper 140|140]], where one is ordered as in the mask ROM and the other as it is presented logically to the program? --[[User:Tepples|Tepples]] ([[User talk:Tepples|talk]]) 21:07, 17 May 2014 (MDT) | ||
: Sort of. Unlike m101, where its order is sensible (even if in disagreement with the ROM), both orders are pretty illogical for m150/243. Someone should check with Санчез, though. This mapper really feels like Sachen specifically designed it to be maximally annoying for cloners to implement using discrete logic (Two 74'74s, two 74'75s, two 74'138s, one 74'368, one 74'00), even though it only provides GNROM plus mirroring control. —[[User:Lidnariq|Lidnariq]] ([[User talk:Lidnariq|talk]]) 22:59, 17 May 2014 (MDT) | |||
Revision as of 04:59, 18 May 2014
Physical vs. logical ordering
Is this like the difference between iNES Mapper 087 and iNES Mapper 101/140, where one is ordered as in the mask ROM and the other as it is presented logically to the program? --Tepples (talk) 21:07, 17 May 2014 (MDT)
- Sort of. Unlike m101, where its order is sensible (even if in disagreement with the ROM), both orders are pretty illogical for m150/243. Someone should check with Санчез, though. This mapper really feels like Sachen specifically designed it to be maximally annoying for cloners to implement using discrete logic (Two 74'74s, two 74'75s, two 74'138s, one 74'368, one 74'00), even though it only provides GNROM plus mirroring control. —Lidnariq (talk) 22:59, 17 May 2014 (MDT)
