Overhaul of the API #73
kdschlosser
announced in
Announcements
Replies: 1 comment 4 replies
-
Just one proposal. For the i8080 bus I recommend to include the rd pin in the defintion. I have faced a long term problem with a display having that pin connected. Finally I realised that I had to set that pin into a defined high state to get your great job running. I might be able to help in getting the read routines running to check status registers and read the display ram for test purposes. |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am going to be overhauling the API for the SPI, I8080, RGB bus drivers. I really do not care for how it is currently done and I want to unify everything into the machine module with an understandable hierarchy.
my plan is to have the organization be as follows. This is going to be located in the
machine
moduleMy purpose to doing it this way it to keep the API the same across all of the bus types which will make it easier for the user to use and it will also make it easier on the development side of things because the API will be the same.
The above is a rough draft and I didn't put in what function parameters are keyword only and positional only.
I am looking for thoughts and or suggestion...
Beta Was this translation helpful? Give feedback.
All reactions