Decouple front-io functionality from sidecar-seq #2161
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Aaron-Hartwig
force-pushed
the
front-io-decouple-oops
branch
from
1274755 to
5f47ebf
Compare
Aaron-Hartwig
force-pushed
the
front-io-decouple-oops
branch
from
54164d6 to
920b881
Compare
|
This commit is deployed to |
Aaron-Hartwig
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
All the logic about how to interact with the front I/O board (power control, FPGA programming/communication, I2C comms) was very tightly coupled with Sidecar's business logic. The goal of this PR is to separate that stuff out into a dedicated front-io-server which can then handle all of the relevant details while exposing an API for other tasks. The big forcing factor here is working on the Medusa design (finally). Switching the medusa app to utilizing the front-io-server will be a separate PR.