| Age | Commit message (Collapse) | Author |
|
Signed-off-by: Daniel Thompson <daniel@redfelineninja.org.uk>
|
|
The original approach is *really* bad at drawing vertical lines (it ends
up working a pixel at a time and works the chip select for each one.
Optimize both the pixel fill and the use of the line buffer. The result
is 20% faster for quarter screen fills, 3x for horizontal lines and 6x
for vertical lines.
Signed-off-by: Daniel Thompson <daniel@redfelineninja.org.uk>
|
|
Measure the performance of the quarter screen fill, horizontal lines and
vertical lines.
Signed-off-by: Daniel Thompson <daniel@redfelineninja.org.uk>
|
|
Signed-off-by: Daniel Thompson <daniel@redfelineninja.org.uk>
|
|
Signed-off-by: Daniel Thompson <daniel@redfelineninja.org.uk>
|
|
Signed-off-by: Daniel Thompson <daniel@redfelineninja.org.uk>
|
|
... and enable persistant code loading.
Fixes: #37
Signed-off-by: Daniel Thompson <daniel@redfelineninja.org.uk>
|
|
Fixes: 9eb9b74 ("Update preprocess to use $(BOARD)").
Signed-off-by: Daniel Thompson <daniel@redfelineninja.org.uk>
|
|
Signed-off-by: Steve Amor <steveamor@users.noreply.github.com>
[daniel@redfelineninja.org.uk: Adopt corresponding bootloader version]
|
|
The preprocess to create watch.py was hard coded for PineTime so changed to $(BOARD)
This will be required for other watches like the P8
Signed-off-by: Steve Amor <steveamor@users.noreply.github.com>
|
|
We also change the colour scheme slightly because the increased size of
the clock interferes visually with the main display when it is bright
white.
Signed-off-by: Daniel Thompson <daniel@redfelineninja.org.uk>
|
|
Signed-off-by: Daniel Thompson <daniel@redfelineninja.org.uk>
|
|
There nothing in the docs to give the delay time required after a
reset. Currently we use 200ms because that appears on some older
code for BMA423 but is removed in more recent drivers. 50ms is still
a long time (for hardware) and has held up in testing.
Signed-off-by: Daniel Thompson <daniel@redfelineninja.org.uk>
|
|
Signed-off-by: Daniel Thompson <daniel@redfelineninja.org.uk>
|
|
Currently when the the bootloader is modified if fails to build because
the wildcard in the hex merge picks up both the old and new binaries.
Fix this by explicitly deleting the old one.
Signed-off-by: Daniel Thompson <daniel@redfelineninja.org.uk>
|
|
Signed-off-by: Fuji Pebri <pebri86@gmail.com>
[daniel@redfelineinja.org.uk: removed leading underscore from method
arguments, removed redundant state tracking, adopt i2c.writeto_mem]
Signed-off-by: Daniel Thompson <daniel@redfelineninja.org.uk>
|
|
Signed-off-by: Daniel Thompson <daniel@redfelineninja.org.uk>
|
|
|
|
|
|
|
|
Signed-off-by: Daniel Thompson <daniel@redfelineninja.org.uk>
|
|
Signed-off-by: Daniel Thompson <daniel@redfelineninja.org.uk>
|
|
Currently there's no fancy algorithms to estimate stride length. Just
pure simple step counting directly from the hardware's "intelligence
engine".
Signed-off-by: Daniel Thompson <daniel@redfelineninja.org.uk>
|
|
Fixes: #32
|
|
|
|
Fixes: #28
|
|
|
|
|
|
|
|
Currently the slider doesn't actually slide (because we process touch
events rather than swipe events) but we've called is a slider anyway.
|
|
This allows some interesting manipulations of 2-bit images.
|
|
|
|
|
|
|
|
Fixes: #16
|
|
|
|
Fixes: #1
Fixes: #3
|
|
Update README.rst
|
|
|
|
This is an incompatible change... older 2-bit images will need to be
re-encoded to display correctly.
|
|
Fixes: #25
|
|
The logo module is currently unused but it simply sits there consuming
flash. Let's shift it to the demo app to is can consume RAM instead (but
only when we upload the demo to the watch).
|
|
sx is measured in pixels (2-bytes) and len(display.linebuffer) gives
a value in bytes so the divisor isn't right.
Whilst we are here let's make sure we use integer division too.
Fixes: #18
|
|
|
|
Clarification based on #9
|
|
|
|
|
|
|
|
|
|
|