Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow compilation to wasm32-wasi target #64

Closed
rahul-thakoor opened this issue Jan 28, 2021 · 2 comments
Closed

Allow compilation to wasm32-wasi target #64

rahul-thakoor opened this issue Jan 28, 2021 · 2 comments

Comments

@rahul-thakoor
Copy link
Contributor

Hello!

I have a use case where I would like to use a subset of the functionality of rust-sysfs-gpio. I am compiling a was--compatible module that can access gpio pins via a webassembly runtime.

@proohit
Copy link

proohit commented May 5, 2021

Hi, I've stumbled over this issue. Is there any news on GPIO via WASI? Afaik, WASI doesn't include hardware abstractions for peripherals, but that knowledge may be old :).

@nastevens
Copy link
Member

Closing as @posborne's statement from gpio-cdev applies here as well

This crate is very much so only intended to target Linux and wasm/wasi is not that. I think a more interesting approach in general would for there to be some project which seeks to provide an implementation of the https://github.com/rust-embedded/embedded-hal traits that could execute within an environment like wasm32-wasi which would proxy requests through some mechanism to an implementation in the host environment. At least, that's my intuition while not having extensive experience with wasm. This would seem to be much more well suited to implementing things portably and securely across platforms which is one of the reasons that people often are deciding to target wasm.

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

No branches or pull requests

3 participants