Removing old references to ChibiOS/GFX in documentation
This commit is contained in:
parent
379878a013
commit
4bafff3ea5
2 changed files with 2 additions and 2 deletions
|
@ -12,7 +12,7 @@
|
||||||
*
|
*
|
||||||
* @brief Module to abstract the very variable ADC interfaces of the underlying systems
|
* @brief Module to abstract the very variable ADC interfaces of the underlying systems
|
||||||
*
|
*
|
||||||
* @details The reason why ChibiOS/GFX has it's own ADC abstraction is because
|
* @details The reason why uGFX has it's own ADC abstraction is because
|
||||||
* the Chibi-OS drivers are very CPU specific and do not
|
* the Chibi-OS drivers are very CPU specific and do not
|
||||||
* provide a way across all hardware platforms to create periodic
|
* provide a way across all hardware platforms to create periodic
|
||||||
* ADC conversions. There are also issues with devices with different
|
* ADC conversions. There are also issues with devices with different
|
||||||
|
|
|
@ -12,7 +12,7 @@
|
||||||
*
|
*
|
||||||
* @brief Module which provides software based timers for user-space applications
|
* @brief Module which provides software based timers for user-space applications
|
||||||
*
|
*
|
||||||
* @details The reason why ChibiOS/GFX has it's own timer abstraction is because
|
* @details The reason why uGFX has it's own timer abstraction is because
|
||||||
* virtual timers provided by ChibiOS/RT are interrupt context only.
|
* virtual timers provided by ChibiOS/RT are interrupt context only.
|
||||||
* While great for what they are designed for, they make coding of the input
|
* While great for what they are designed for, they make coding of the input
|
||||||
* drivers much more complex.
|
* drivers much more complex.
|
||||||
|
|
Loading…
Add table
Reference in a new issue