Teacup_Firmware

Commit Graph

Author	SHA1	Message	Date
Markus Hitter	fe398d84ce	displaybus.h: note the different #include strategies. Yes, these strategies feel a lot like heading into uncharted territory, because I can't find notable textbook examples on how to select between various "classes" at compile time. Nevertheless, it works fine, binaries are small and fast and as such it can't be _that_ wrong.	2016-05-18 18:03:36 +02:00
Markus Hitter	a97ec8a376	Display: introduce displaybus.h. This is a broker for mapping display bus calls to the bus actually in use.	2016-04-26 14:13:15 +02:00

Author

SHA1

Message

Date

Markus Hitter

fe398d84ce

displaybus.h: note the different #include strategies.

Yes, these strategies feel a lot like heading into uncharted
territory, because I can't find notable textbook examples on how
to select between various "classes" at compile time. Nevertheless,
it works fine, binaries are small and fast and as such it can't
be _that_ wrong.

2016-05-18 18:03:36 +02:00

Markus Hitter

a97ec8a376

Display: introduce displaybus.h.

This is a broker for mapping display bus calls to the bus actually
in use.

2016-04-26 14:13:15 +02:00

2 Commits