When designing generic interfaces that could be used to easily allow developers to build their drivers for embedded displays. Generic embedded display interfaces.What kinds of interface-level features would you expect an interface to have when using it to develop a driver (in C++)? Considering that I know what generic interfaces are, but just want to get an idea of API features that you would expect interfaces to have that you might use when developing your driver for an embedded display, like the SSD1331 display.Another thing is I don't mean the serial communication portion, rather I mean specifically the interfaces that just need to focus on the actual generic display interfaces to be used for developing the drivers.As to what you expect these interfaces to contain, what they should provide you to develop your drivers. An example is, having a class called DisplayAdapter class that allows users to define their display adapter allowing them to send data across multiple displays, almost like a bridging for embedded displays.What other features and APIs would expected of these generic embedded display interfaces?
When designing generic interfaces that could be used to easily allow developers to build their drivers for embedded displays. Generic embedded display interfaces.
What kinds of interface-level features would you expect an interface to have when using it to develop a driver (in C++)? Considering that I know what generic interfaces are, but just want to get an idea of API features that you would expect interfaces to have that you might use when developing your driver for an embedded display, like the SSD1331 display.
Another thing is I don't mean the serial communication portion, rather I mean specifically the interfaces that just need to focus on the actual generic display interfaces to be used for developing the drivers.
As to what you expect these interfaces to contain, what they should provide you to develop your drivers.
An example is, having a class called DisplayAdapter class that allows users to define their display adapter allowing them to send data across multiple displays, almost like a bridging for embedded displays.
What other features and APIs would expected of these generic embedded display interfaces?
Step by step
Solved in 2 steps
