fix: Regenerate yaml, carryTrim => trimSource cleanup (#3121)
PR #2995 didn't take into account the data model storage actually does change when you change a variable name. Boxer yaml generation was missed in earlier PR. * chore: Run `generate-yaml.sh` * chore(cpn): carryTrim -> trimSource * fix(build): Boxer missing from `generate-yaml` * dodgy attempt to read old carryTrim * fix: Don't break the byte boundary + reorder * fix(yaml): indentation for attributes that should not be output * chore: Regenerate YAML after rebase --------- Co-authored-by: raphaelcoeffic <raphael.coeffic@frafos.com>
This commit is contained in:
co-authored by
raphaelcoeffic
parent
4e09bd7b8c
commit
46cc979875
@@ -1944,6 +1944,13 @@ static void r_jitterFilter(void* user, uint8_t* data, uint32_t bitoffs,
|
||||
yaml_put_bits(data, i, bitoffs, 1);
|
||||
}
|
||||
|
||||
static void r_carryTrim(void* user, uint8_t* data, uint32_t bitoffs,
|
||||
const char* val, uint8_t val_len)
|
||||
{
|
||||
int32_t i = yaml_str2int(val, val_len);
|
||||
yaml_put_bits(data, i, bitoffs, 6);
|
||||
}
|
||||
|
||||
static void r_rotEncDirection(void* user, uint8_t* data, uint32_t bitoffs,
|
||||
const char* val, uint8_t val_len)
|
||||
{
|
||||
|
||||
Reference in New Issue
Block a user