Category talk:Mappers with IRQs: Difference between revisions
From NESdev Wiki
Jump to navigationJump to search
Rainwarrior (talk | contribs) |
Rainwarrior (talk | contribs) (clarify) |
||
| Line 3: | Line 3: | ||
I don't think it makes sense to say that "if it's clocked by M2, regardless of how general it is, it belongs in [[:Category:Mappers with cycle IRQs]]". 1- With such a constraint, the only thing that could possibly make sense in the overarching category would be things that used analog effects for timing ... or the way IRQs are used on "real" computers, where they signal asynchronous events. 2- Because these are not general, it ''can't'' be used for arbitrary timing. At best, they're far more crippled than Tepples's demonstration of using the DPCM for mid-screen splits. —[[User:Lidnariq|Lidnariq]] ([[User talk:Lidnariq|talk]]) 13:10, 18 May 2015 (MDT) | I don't think it makes sense to say that "if it's clocked by M2, regardless of how general it is, it belongs in [[:Category:Mappers with cycle IRQs]]". 1- With such a constraint, the only thing that could possibly make sense in the overarching category would be things that used analog effects for timing ... or the way IRQs are used on "real" computers, where they signal asynchronous events. 2- Because these are not general, it ''can't'' be used for arbitrary timing. At best, they're far more crippled than Tepples's demonstration of using the DPCM for mid-screen splits. —[[User:Lidnariq|Lidnariq]] ([[User talk:Lidnariq|talk]]) 13:10, 18 May 2015 (MDT) | ||
:Ah, I didn't understand why those 3 were left out of the cycle category. That sounds like a [[:Category:Mappers with fixed-timing IRQs|new category]] to me, then. Since they're all still cycle counters (even though the timing isn't configurable) I made that a subcategory of cycle IRQs, but we can move it if there are other kinds. - [[User:Rainwarrior|Rainwarrior]] ([[User talk:Rainwarrior|talk]]) 14:06, 18 May 2015 (MDT) | :Ah, I didn't understand why those 3 were left out of the cycle category. That sounds like a [[:Category:Mappers with fixed-timing IRQs|new category]] to me, then. Since they're all still cycle counters (even though the timing isn't configurable) I made that a subcategory of cycle IRQs for now, but we can move it back to the parent category if there are other kinds (you mention it on the scanline IRQ category description, but do any exist?). Better to just keep all the fixed ones in their own category, since that's a far more important property than either cycle or scanline counting. - [[User:Rainwarrior|Rainwarrior]] ([[User talk:Rainwarrior|talk]]) 14:06, 18 May 2015 (MDT) | ||
Revision as of 20:13, 18 May 2015
Where to file fixed-timing IRQ-sources
I don't think it makes sense to say that "if it's clocked by M2, regardless of how general it is, it belongs in Category:Mappers with cycle IRQs". 1- With such a constraint, the only thing that could possibly make sense in the overarching category would be things that used analog effects for timing ... or the way IRQs are used on "real" computers, where they signal asynchronous events. 2- Because these are not general, it can't be used for arbitrary timing. At best, they're far more crippled than Tepples's demonstration of using the DPCM for mid-screen splits. —Lidnariq (talk) 13:10, 18 May 2015 (MDT)
- Ah, I didn't understand why those 3 were left out of the cycle category. That sounds like a new category to me, then. Since they're all still cycle counters (even though the timing isn't configurable) I made that a subcategory of cycle IRQs for now, but we can move it back to the parent category if there are other kinds (you mention it on the scanline IRQ category description, but do any exist?). Better to just keep all the fixed ones in their own category, since that's a far more important property than either cycle or scanline counting. - Rainwarrior (talk) 14:06, 18 May 2015 (MDT)
