Talk:INES Mapper 001: Difference between revisions
From NESdev Wiki
Jump to navigationJump to search
(what the MMC1 needs M2 for) |
No edit summary |
||
| Line 6: | Line 6: | ||
:Anyway, I'm not clear how edge triggered behavior causes what's happening here, unless the MMC1 ignores M2 altogether. —[[User:Lidnariq|Lidnariq]] ([[User talk:Lidnariq|talk]]) 01:33, 19 March 2013 (MDT) | :Anyway, I'm not clear how edge triggered behavior causes what's happening here, unless the MMC1 ignores M2 altogether. —[[User:Lidnariq|Lidnariq]] ([[User talk:Lidnariq|talk]]) 01:33, 19 March 2013 (MDT) | ||
::It's likely that the writing mechanism might be ignoring M2. The only thing M2 is really needed for is enabling the PRG RAM chip. --[[User:Tepples|Tepples]] ([[User talk:Tepples|talk]]) 06:51, 19 March 2013 (MDT) | ::It's likely that the writing mechanism might be ignoring M2. The only thing M2 is really needed for is enabling the PRG RAM chip. --[[User:Tepples|Tepples]] ([[User talk:Tepples|talk]]) 06:51, 19 March 2013 (MDT) | ||
::Maybe someone should ask Disch, if he's easy to reach. I personally wouldn't mind people correcting mistakes in documents that are still credited to me. ;) --[[User:Ulfalizer|Ulfalizer]] ([[User talk:Ulfalizer|talk]]) 13:22, 19 March 2013 (MDT) | |||
Revision as of 19:22, 19 March 2013
Would it be okay to add a note to Disch's note explaining the "too close together" behavior? Kev says it's due to edge-triggering.
The note would clearly indicate that it's an edit and not part of the original notes. -Ulfalizer (talk) 00:14, 19 March 2013 (MDT)
- I'm torn about what to do with Disch's notes, especially when they're wrong. Sometimes I've just completely replaced them (iNES Mapper 234). Sometimes I've completely rewritten them (iNES Mapper 072). Sometimes I just put a big warning label at the top of the article (iNES Mapper 019). We don't have a standing policy of not editing Disch's notes, although I've accidentally caused confusion by not marking it when I've done so... oops.
- Anyway, I'm not clear how edge triggered behavior causes what's happening here, unless the MMC1 ignores M2 altogether. —Lidnariq (talk) 01:33, 19 March 2013 (MDT)
- It's likely that the writing mechanism might be ignoring M2. The only thing M2 is really needed for is enabling the PRG RAM chip. --Tepples (talk) 06:51, 19 March 2013 (MDT)
- Maybe someone should ask Disch, if he's easy to reach. I personally wouldn't mind people correcting mistakes in documents that are still credited to me. ;) --Ulfalizer (talk) 13:22, 19 March 2013 (MDT)
