Stepping in here to answer some of the recent questions regarding 2.3.6.
2.3.6 works on all boards and is compatible with all hardware in the field, as will all software going forward. We can auto-detect all hardware revisions and the software knows how to do the right thing. For those who are aware of how software releases work, there was never a separate branch that needed to be merged, the new driver was just added to our main branch.
To answer some other questions:
- The change was to a chip on the display board that actually controls the five button nav cluster. It has no affect on sound and this chip is not even on the main digital board. It’s on a separate board (the display board) that is isolated from the main board.
- This is not a temporary change, we have approved multiple chips to handle the button cluster input. We took this approach due to the supply chain/ parts availability issues, to insure we had multiple paths to building units in production. The parts are from the same manufacture and are cousins, so the underlying driver technology is almost identical. We just have to identify which chip we are talking to and take some slightly different steps during communication.
- The change is transparent to the functionality of the unit. When you press a button that input gets sent to a GPIO chip that eventually gets communicated back to our main processor chip. That signal path is the same regardless of which chip we use.