Peter Newman

> Can you also have a look at that linked thread and see if you can fix it by changing a permission externally to OLA? https://stackoverflow.com/questions/9313428/getting-eperm-when-calling-pthread-create-for-sched-fifo-thread-as-root-on-lin

> For easier maintainability (since it is just a normal build with an extra step or two at the end) should it go in `lint.yaml`? We already have a pipline...

Well it works fine with no containers involved, despite them saying they shouldn't be an issue: https://github.com/OpenLightingProject/ola/pull/1882 It found a small handful of problems but nothing too exciting IMHO. Most...

That's a fair point, feel free to open a PR. :) The port ID is generally less important than the Description, although it looks like the current code names them...

See my related issue regarding naming here https://github.com/OpenLightingProject/ola/issues/975

@Keeper-of-the-Keys I think this is what you were referring to regarding FTDI port naming?

Ah, that sounds like AllowMultiPortPatching() is set wrong: http://docs.openlighting.org/ola/doc/latest/classola_1_1_device.html#aa2e036c37dea36394570618613368f08 And indeed the code supports that. Lets get #1422 sorted and merged in first, then look at that and the other...

See also (for historic reference) https://github.com/OpenLightingProject/ola/pull/394

Hi @Keeper-of-the-Keys , Please see and test https://github.com/OpenLightingProject/ola/pull/1435 . If you're happy we'll merge, and that should fix your specific request here.

So in terms of unique naming of individual ports @Keeper-of-the-Keys , see my comments here: https://github.com/OpenLightingProject/ola/issues/1219#issuecomment-294134338 Essentially adding an i into the port's description should solve the issue. But we...