steelman

Yup, a warning (and an option to suppress it of sort `--i-know-what-i-am-doing-and-i-take-full-responsibility`) would also have helped me. > run multiple instances of labgrid-exporter targeting different test setups from the same...

I haven't thought about connecting to many different exporters at once, indeed. In such case, I suppose, each exporter should advertise the interpreter it uses and clients need to discover...

I've got [patches](https://github.com/steelman/labgrid/commit/fa5ce260d581df686cc48949c64001302bfea324) to introduce support for FTDI chips in bitbanging mode to control relays (which enables using 8 pins instead of 3-4 when controlled via Linux gpio driver). For...

> Thanks for the PR! > > Yes, guess this would be a good new feature, we even have a related ticket #4549. > > I only had a quick...

> Quite a lot of tests are failing. This is because fido2 related code gets used even if it was not explicitly requested (and there usually is no fido2 device...

> sheetmetal is only for constant thickness of material. OK. > I am familiar with FT Mini Power Pod (-: Do you have any recommendation for digital modelling of foamboard...

If you're fine, I am fine. Do you think this could/should be tested somehow?

> we would have to find a way of making it without breaking existing objects Even if the ILP32 ABI is currently marked as **(Beta)**, which [allows](https://github.com/ARM-software/abi-aa/blob/ee6b627a58988b56a761d1a3d545fc01b9b78241/aapcs64/aapcs64.rst?plain=1#L171) such changes?

As you wrote, the ABI hasn't been accepted neither in linux nor in glibc and was recently [deprecated](https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=625ea3c6ea1811388d030eddff57cd46c209d49a) in gcc. I don't know how much legacy binaries are out there,...

> It's generally wrong to make assumptions about size_t Alas these assumptions are already everywhere starting with glibc, gcc and [llvm](https://github.com/llvm/llvm-project/blob/82404e3c69168b9fdb779174d3499f5f87f818d2/llvm/include/llvm/ADT/SmallBitVector.h). > do you actually use ILP32? We are building...