Skip to content

Update the init for the depacketizer - #53

Merged
cbrisebois-lasp merged 1 commit into
mainfrom
feature/depacketizer-init
Oct 21, 2026
Merged

cbrisebois-lasp merged 1 commit into
mainfrom
feature/depacketizer-init

Conversation

@cbrisebois-lasp

Copy link
Copy Markdown
Collaborator

Latest adamant adds new init items for the depacketizer. This update reflects that change

@cbrisebois-lasp
cbrisebois-lasp force-pushed the feature/depacketizer-init branch from 19b7a32 to 367086a Compare October 21, 2026 15:55
@cbrisebois-lasp
cbrisebois-lasp force-pushed the feature/depacketizer-init branch 2 times, most recently from ebda105 to 7ac20a1 Compare October 21, 2026 18:56
…lies

The depacketizer now takes init parameters that choose whether the secondary header checksum is checked and where the count of trailing bytes behind a command comes from, and its defaults differ from the behavior these assemblies were built on. Setting both parameters keeps the example checking the checksum and reading the pad byte count from the function code, exactly as before.
@cbrisebois-lasp
cbrisebois-lasp force-pushed the feature/depacketizer-init branch from 7ac20a1 to 91c87e7 Compare October 21, 2026 19:24
@cbrisebois-lasp
cbrisebois-lasp merged commit af77a63 into main Oct 21, 2026
6 checks passed
@cbrisebois-lasp
cbrisebois-lasp deleted the feature/depacketizer-init branch October 21, 2026 19:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants