Nick Stevens

Seems logical to me as well :+1:

It's possible that the Debian Raspberry Pi image doesn't have sysfs GPIO enabled by default. What do you get if you `ls /sys/class/gpio`?

This sounds similar to https://github.com/rust-embedded/meta-rust-bin/issues/94 - could you please double-check that you've updated to the latest `master`?

> Yes, however, I believe we cannot use it stable until it is release. Am I wrong? You're correct for how things work at present. You can work around it...

@hellow554 You can use `PREFERRED_VERSION` for the `rust-bin-cross-*` and `cargo-bin-cross-*` recipes. For example, if my target is ARM: ``` PREFERRED_VERSION_rust-bin-cross-arm ?= "1.43.0" PREFERRED_VERSION_cargo-bin-cross-arm ?= "${PREFERRED_VERSION_rust-bin-cross-arm}" ```

Related to #64

@jameshilliard Am I missing something or doesn't this still require a nightly version of cargo? I understand it works with stable rustc, but it's still a problem to include nightly...

Yeah unfortunately `pred && pred` isn't possible because it requires a `bool` be returned immediately. Currently `&&` doesn't appear to be overloadable. I came from C++ where operator overloading got...

The Linux sysfs interface for GPIOs (which is the lower-level interface that rust-sysfs-gpio uses) is not the right interface for doing anything with any sort of timing constraints, such as...

I still wouldn't count on that code - it may work some percent of the time but then fail other times. The sysfs interface does not have any sort of...