James Bowman

Yes, that is correct. SPIDriver only runs in mode 0. What device do you have that runs in another mode?

Sure, added 3-clause BSD.

This blog entry explains their naming conventions: https://blogs.msdn.microsoft.com/wsl/2017/04/14/serial-support-on-the-windows-subsystem-for-linux/ So I would expect ``COM16`` to appear under WSL as ``/dev/ttyS16`` - does this make sense?

Trying the same operations on one of the standard image works fine, so seems that something in the original exr's header is causing the problem. Please can you show ``h``?...

Hard to say what's happening. That header looks fine. You can send me a problem .exr privately - [email protected]

Yes, did you get my email reply with the result? On Tue, Jan 23, 2018 at 2:00 PM, Mel Massadian wrote: > Did you managed to deal with the sent...

OK... please mail me directly at [email protected] and we'll continue there

Walkthough: http://juusosalonen.com/post/139067064745/demystifying-pkgbuild-in-os-x

Aha, thanks, so running this: ``` ls -RUx | gawk -F '\n' '{ match($1, /(drivers|helpers)\/(.+)\/(.+)\:/, arr) ; if (length(arr[0]) > 0 && match(arr[3], arr[2]) > 0) printf "%s, ", arr[3]...

Shall I make a PR for CircuitPython_Community_Bundle with a shell script ``build.sh`` to do the above, and use it in the README?