fantemp

avr/fantemp

0 Fork 0

...

Author	SHA1	Message	Date
BlackMarkandClaude Opus 5	0e9060db69	build: the libavr pin advances past the consumer-report fixes timer::engine gains stop()/start() and a runtime TOP, adc gains disable()/enable(), and libavr_programming_targets() stops leaving .fuse bytes in the flash HEX. Every one of them is additive, and this port adopts none of them yet: its 3 built images come out byte-identical across the pin change, which is what the advance is here to keep true. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-08-01 23:18:55 +02:00
BlackMarkandClaude Opus 5	3fbbcdade9	build: the libavr pin advances to the v9 era Built and tested against it in a clean checkout of this port, through its own submodule rather than a working-tree override, so the pin is what was proved. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-08-01 18:46:36 +02:00

Author

SHA1

Message

Date

BlackMarkandClaude Opus 5

0e9060db69

build: the libavr pin advances past the consumer-report fixes

timer::engine gains stop()/start() and a runtime TOP, adc gains
disable()/enable(), and libavr_programming_targets() stops leaving .fuse bytes
in the flash HEX. Every one of them is additive, and this port adopts none of
them yet: its 3 built images come out byte-identical across the pin change,
which is what the advance is here to keep true.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

2026-08-01 23:18:55 +02:00

BlackMarkandClaude Opus 5

3fbbcdade9

build: the libavr pin advances to the v9 era

Built and tested against it in a clean checkout of this port, through its own
submodule rather than a working-tree override, so the pin is what was proved.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

2026-08-01 18:46:36 +02:00

1 changed files with 1 additions and 1 deletions

libavr

+1 -1

Submodule libavr updated: 71cfb2f1ae...b719ed74d8.

Compare commits