Talk:Input devices: Difference between revisions
From NESdev Wiki
Jump to navigationJump to search
No edit summary |
(→Draft revision to table: revision posted) |
||
| (4 intermediate revisions by 2 users not shown) | |||
| Line 4: | Line 4: | ||
Isn't $4016:2 connected to controller 2 on the Famicom for the microphone? -[[User:Ulfalizer|Ulfalizer]] ([[User talk:Ulfalizer|talk]]) 00:01, 15 April 2013 (MDT) | Isn't $4016:2 connected to controller 2 on the Famicom for the microphone? -[[User:Ulfalizer|Ulfalizer]] ([[User talk:Ulfalizer|talk]]) 00:01, 15 April 2013 (MDT) | ||
: Yes, but it didn't fit fluidly into the description, and debatably is unnecessary on the general "input devices" page. The more places we describe something, the more places we have a chance of accidentally contradicting ourselves.—[[User:Lidnariq|Lidnariq]] ([[User talk:Lidnariq|talk]]) 01:37, 15 April 2013 (MDT) | |||
== "Usage of port pins by hardware type" table == | |||
In the "Usage of port pins by hardware type" table, I believe I've spotted some errors, but I want to make sure I understand correctly: | |||
* The Power Pad and Family Trainer Mat use writes to $0416 (OUT2/1/0), not reads from $0416 ($0416 D2/1/0). | |||
* Devices that use sequential reads to get bit data (Arkanoid controllers) or button data (Power Pad<del>/Family Trainer Mat</del>) also use the corresponding CLK signal. | |||
--[[User:Bavi H|Bavi H]] ([[User talk:Bavi H|talk]]) 11:02, 31 December 2021 (UTC) | |||
Edit: Upon re-reading the [[Power Pad#Family Trainer Mat|Family Trainer Mat]] protocol, my current understanding is that it doesn't use the CLK signal. --[[User:Bavi H|Bavi H]] ([[User talk:Bavi H|talk]]) 20:36, 1 January 2022 (UTC) | |||
=== Draft revision to table === | |||
I've [[User:Bavi H/Input devices table|drafted a revision to table]] that makes these changes: | |||
* putting the output columns on the left so that a left-to-right reading order matches up with an output-then-input sequence of operations | |||
* putting clock columns (/OE1 and /OE2) to the left of their respective data columns (D4 to D0), for the same reason | |||
* adding an initial row that explains how to access the signals ("write $4016", "read $4016", "read $4017") | |||
* adding more initial rows that explain which signals are available at which ports. | |||
Any comments? --[[User:Bavi H|Bavi H]] ([[User talk:Bavi H|talk]]) 20:36, 1 January 2022 (UTC) | |||
: Well, if nothing else, I like your formatting better. —[[User:Lidnariq|Lidnariq]] ([[User talk:Lidnariq|talk]]) 04:21, 7 January 2022 (UTC) | |||
I boldly posted the draft version. Feel free to discuss, modify, revert(?). --[[User:Bavi H|Bavi H]] ([[User talk:Bavi H|talk]]) 14:01, 10 February 2022 (UTC) | |||
Latest revision as of 14:01, 10 February 2022
I guess the discussion at the beginning could be NES-specific. Could someone fill in the details for Famicom? -Ulfalizer (talk) 04:39, 14 April 2013 (MDT)
Isn't $4016:2 connected to controller 2 on the Famicom for the microphone? -Ulfalizer (talk) 00:01, 15 April 2013 (MDT)
- Yes, but it didn't fit fluidly into the description, and debatably is unnecessary on the general "input devices" page. The more places we describe something, the more places we have a chance of accidentally contradicting ourselves.—Lidnariq (talk) 01:37, 15 April 2013 (MDT)
"Usage of port pins by hardware type" table
In the "Usage of port pins by hardware type" table, I believe I've spotted some errors, but I want to make sure I understand correctly:
- The Power Pad and Family Trainer Mat use writes to $0416 (OUT2/1/0), not reads from $0416 ($0416 D2/1/0).
- Devices that use sequential reads to get bit data (Arkanoid controllers) or button data (Power Pad
/Family Trainer Mat) also use the corresponding CLK signal.
--Bavi H (talk) 11:02, 31 December 2021 (UTC)
Edit: Upon re-reading the Family Trainer Mat protocol, my current understanding is that it doesn't use the CLK signal. --Bavi H (talk) 20:36, 1 January 2022 (UTC)
Draft revision to table
I've drafted a revision to table that makes these changes:
- putting the output columns on the left so that a left-to-right reading order matches up with an output-then-input sequence of operations
- putting clock columns (/OE1 and /OE2) to the left of their respective data columns (D4 to D0), for the same reason
- adding an initial row that explains how to access the signals ("write $4016", "read $4016", "read $4017")
- adding more initial rows that explain which signals are available at which ports.
Any comments? --Bavi H (talk) 20:36, 1 January 2022 (UTC)
I boldly posted the draft version. Feel free to discuss, modify, revert(?). --Bavi H (talk) 14:01, 10 February 2022 (UTC)
