From upstream commit 35100785e2c4 ("ctx: rasterizer, micro optimizations
in rasterizer_fill_rect").

The integration is mostly a copy of pippin's original integration with
the biggest change being the use of a monospace default font.  This font
is autogenerated from lib/ctx/fira-mono.ttf at build-time so it can be
easily replaced with a different one (just overwrite said file).

git-url: https://ctx.graphics/.git


Co-developed-by: Øyvind Kolås <pippin@gimp.org>

Don't lint vendored sources...

This will result in more reliably reaching a clean state.

Co-Authored-By: schneider <schneider@muc.ccc.de>
Signed-off-by: Rahix <rahix@rahix.de>

Also auto generate the header during build time.

The poor-profiler scripts allow profiling card10 (to some degree).

Signed-off-by: Rahix <rahix@rahix.de>

Rewrite image-convert script to more easily change the version splash
screen.

Signed-off-by: Rahix <rahix@rahix.de>

Add a --set-time flag to allow setting card10 system time via the
USB-Serial connection.  Use like this:

    ./tools/pycard10.py --set-time

Signed-off-by: Rahix <rahix@rahix.de>

Serge Bazanski authored 5 years ago and dx committed 5 years ago

We update the documentaiton and CI tooling to remove references to the jailbreak firmware.

We also slightly update the docs to mention USB mode in a separate page, for unification purposes.

Signed-off-by: Rahix <rahix@rahix.de>

Signed-off-by: Rahix <rahix@rahix.de>

Signed-off-by: Rahix <rahix@rahix.de>

Signed-off-by: Rahix <rahix@rahix.de>

swym authored 5 years ago and rahix committed 5 years ago

Co-authored-by: Rahix <rahix@rahix.de>

This commit adds a script to embed the git-version of the firmware into
the bootloader, epicardium, and pycardium.  All three binaries will
display their version on startup.

Signed-off-by: Rahix <rahix@rahix.de>

Co-authored-by: Mateusz Zalega <mateusz@appliedsourcery.com>
Signed-off-by: Rahix <rahix@rahix.de>

Signed-off-by: Rahix <rahix@rahix.de>

We want to run a linter on CI submission.

We also want to display nice error messages to the user. Thus,
annoyatron is born.

The flow is as follows:
 - a MR is submitted and triggers the 'lint' pipeline
 - annoyatron gets pinged over https that an MR requires attention
 - annoyatron starts running and waits until the MR's pipeline run
   succeeds or fails
 - the lint jobs either succeeds or fails
 - annoyatron notices the pipeline passed, and inspects its results to
   see if the lint pipeline failed or not.
 - annoyatron posts a comment, if necessary

Signed-off-by: Rahix <rahix@rahix.de>

Signed-off-by: Rahix <rahix@rahix.de>

Signed-off-by: Rahix <rahix@rahix.de>

Signed-off-by: Rahix <rahix@rahix.de>

Signed-off-by: Rahix <rahix@rahix.de>