archives/pebble
2
0
Fork 0
mirror of https://github.com/google/pebble.git synced 2025-04-30 15:21:41 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions

spelling: independent

Browse source 
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
This commit is contained in:
Josh Soref 2025-01-28 14:49:10 -05:00
parent 423a462ce0
commit 294f626792
3 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/tasks.txt
View file

@ -1,4 +1,4 @@
FreeRTOS lets us create tasks, which are independant threads of execution. We create a few ourselves, and more are created internally by FreeRTOS. We have pre-emption enabled in our FreeRTOS configuration, so we must be mindful of which other tasks are mucking with the same data. This document describes the tasks that exist in our system. FreeRTOS lets us create tasks, which are independent threads of execution. We create a few ourselves, and more are created internally by FreeRTOS. We have pre-emption enabled in our FreeRTOS configuration, so we must be mindful of which other tasks are mucking with the same data. This document describes the tasks that exist in our system.
FreeRTOS Tasks FreeRTOS Tasks
============== ==============

2
src/fw/applib/graphics/framebuffer.c
View file

@ -15,7 +15,7 @@
*/ */
//! @file framebuffer.c //! @file framebuffer.c
//! Bitdepth independant routines for framebuffer.h //! Bitdepth independent routines for framebuffer.h
//! Bitdepth dependent routines can be found in the 1_bit & 8_bit folders in their //! Bitdepth dependent routines can be found in the 1_bit & 8_bit folders in their
//! respective framebuffer.c files. //! respective framebuffer.c files.

2
src/fw/apps/prf_apps/recovery_first_use_app/getting_started_button_combo.h
View file

@ -33,7 +33,7 @@
//! registering a long click handler for a combination of buttons like up+down. //! registering a long click handler for a combination of buttons like up+down.
//! //!
//! I tried to split this out from a seperate file from the recovery_first_use.c file so I could //! I tried to split this out from a seperate file from the recovery_first_use.c file so I could
//! test this behaviour in a unit test independant in the UI. I think it turned out /okay/. The //! test this behaviour in a unit test independent in the UI. I think it turned out /okay/. The
//! callback specification is a little odd (only for select but not for the other ones, should we //! callback specification is a little odd (only for select but not for the other ones, should we
//! be blowing memory on static behaviour like this?) but it was worth a shot. //! be blowing memory on static behaviour like this?) but it was worth a shot.