Till Harbaum

Yes, the plans are there. But I don't know when this will be added.

Have you added pullups to the i2c lines? If not the firmware will wait forever for the lines to go into high/idle state.

What exactly do you think is the problem? Are other digispark based projects also affected by this?

It's not the hardware nor the driver that does the bus enumeration but imho the i2c subsystem of the Linux kernel. And yes, you can simply plug multiple devices into...

Other possible solution: Add an i2c eeprom to each bus with some unique ID. Then read the IDs from eeprom to know which bus you are talking to.

The driver recognizes the device by USB IDs. Changing the name should not hurt.

You can also distinguish the devices by their position in the physical USB device tree. This information can be gathered from the sysfs or indirectly using tools line usb-devices.

That's not a problem with the lcd2usb itself. Lcd2usb just forwards commands from the pc. And this part works just fine. Otherwise you wouldn't get any output. So your display...

So your 1*16 display is slightly 'odd'. But this sounds like you can easily work around this.

Did you actually try that? I did. It works but has some odd side-effects like the thread running the manager then receiving exceptions like ctrl-c and not the main thread...