package pyftdi #4

Closed
opened 2019-04-19 13:24:08 +08:00 by sb10q · 4 comments

To be used for Kasli I2C.

To be used for Kasli I2C.

Added in b44cb6c. Where to integrate?

Added in b44cb6c. Where to integrate?
Poster
Owner

Ideally, that would go upstream nixpkgs.

Ideally, that would go upstream nixpkgs.
Poster
Owner

The only code using it right now is this:
https://github.com/quartiq/kasli-i2c
which isn't currently integrated in ARTIQ (and I'm still wondering if it should).

The only code using it right now is this: https://github.com/quartiq/kasli-i2c which isn't currently integrated in ARTIQ (and I'm still wondering if it should).

Ideally, that would go upstream nixpkgs.

0971a04

The only code using it right now is this: https://github.com/quartiq/kasli-i2c which isn’t currently integrated in ARTIQ (and I’m still wondering if it should).

Questions that may help find reasons:

  • Can we run tests with kasli-i2c in any way?
  • Can we produce documentation or a package from it?
> Ideally, that would go upstream nixpkgs. 0971a04 > The only code using it right now is this: https://github.com/quartiq/kasli-i2c which isn’t currently integrated in ARTIQ (and I’m still wondering if it should). Questions that may help find reasons: * Can we run tests with kasli-i2c in any way? * Can we produce documentation or a package from it?
sb10q closed this issue 2020-06-05 12:18:10 +08:00
Sign in to join this conversation.
No Label
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: M-Labs/nix-scripts#4
There is no content yet.