Closed Uri0533 closed 4 months ago
Hello -- I would think this is pretty straight forward.
I'll be updating the main codebase to the 4in2v2 driver soon. it looks like it has a lot of common syntax with the 2in9v2, so you might be able to drop it in, modify some resolution code / characters per line, and be done with it.
I don't have a 2in9v2 myself to test, and I am not interested in this, so someone else may have to do the testing there... but it shouldn't be too bad.
Not sure if you have been following, but there is a 2.2 branch that should have very similar driver code you could build from now.
Is this something that can be done easily? Can you give guidance on what needs to be changed in the code?
Thanks in advance!