Filipe Laíns 🇵🇸

Do you have libftdi installed? It installs udev rules. ``` $ cat /usr/lib/udev/rules.d/69-libftdi.rules # FTDI Devices: FT232BM/L/Q, FT245BM/L/Q, FT232RL/Q, FT245RL/Q, VNC1L with VDPS Firmware SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001", TAG+="uaccess" #...

No support here yet. My plan was to create a custom loader (https://docs.python.org/3/library/importlib.html#importlib.abc.TraversableResources) that would run the build process when anyone tries to access the files provided by the package,...

My proposal here is to do essentially the same thing as #32 does for dependencies -- allow to pass include files via the dependency constructor.

This should be possible, but someone needs to actually write the code :stuck_out_tongue:. Over the next few weeks I'll be working on the documentation, so that newcomers can easily understand...

Yes, because the firmware has many different targets, from different vendors. The protocol code is shared, and each platform/target must implement a few HALs. I will work on documentation explain...

FYI, I have added a bit of documentation, but it's still a bit scarce. - [Code structure](https://openinput.readthedocs.io/en/latest/contributing/structure.html) - [Porting checklist](https://openinput.readthedocs.io/en/latest/contributing/porting.html) - [HALs definition](https://openinput.readthedocs.io/en/latest/reference/hals.html) Also some [overall guidelines for contributing](https://openinput.readthedocs.io/en/latest/contributing/index.html).

Can you elaborate how your debugging setup works? I think ideally we would have something built on the build system which you could then easily plug into vscode or any...