BFPOWER/physical
2
0
Fork 0
Code Issues 2 Pull Requests Releases Activity

Make core functionality work in no-std environment #2

New Issue
Closed
opened 2023-01-17 01:58:50 +00:00 by zack · 1 comment
zack commented 2023-01-17 01:58:50 +00:00
Owner
Copy Link

The biggest current issue is with async APIs like channels. We may end up picking out a RTOS like Embassy as the only no-std target.

The biggest current issue is with async APIs like channels. We may end up picking out a RTOS like Embassy as the only no-std target.
zack added the
enhancement
accepted
label 2023-01-17 01:58:50 +00:00
zack commented 2023-02-24 23:22:59 +00:00
Author
Owner
Copy Link

We are targetting Embassy and no-std for nodes, master devices based on std will come later.

We are targetting Embassy and no-std for nodes, master devices based on std will come later.
zack closed this issue 2023-02-24 23:22:59 +00:00
zack added the
implementation
complete
 label 2023-04-09 15:08:47 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
build / deploy
packaging and deployment of repository contents
duplicate
This issue or pull request already exists
enhancement
accepted
Enhancement that has been accepted for inclusion in the project
enhancement
proposed
Enhancement proposal to be reviewed and discussed
enhancement
rejected
Enhancement proposal that has been reviewed and rejected
error
confirmed
Bug report that has been investigated and confirmed
error
invalid
Bug report that has been reviewed and found that reported behavior was expected or caused by a different issue
error
suspected
Bug report that needs confirmation it isn't intended behavior or result of misconfiguration or external factors
implementation
complete
Solution has been fully implemented and merged into master
implementation
in progress
Someone is currently implementing this issue
implementation
needs assignee
Implementation has either not been started yet or has been abandoned by the previous builder, need someone to take on this issue
implementation
pending dependency
The solution to this issue is dependent on something else being done
implementation
pending review
Solution implemented, needs further review or merger
meta
Issues about project management
question / discussion
More information is needed
No Label
enhancement
accepted
implementation
complete
Milestone
No items
No Milestone
Assignees
Clear assignees
shan zack
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: BFPOWER/physical#2
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?