Allocation for serial blockdriver

Just supposing my USB serial module + blockdriver is successful… who assigns the number for a new serial blockdriver?

Serial blockdrivers have been at or near death for a few years now, I realise; but there is still a small requirement, in my view. For example, a Raspberry Pi should be able to erase/programme embedded chips via serial, given a suitable serial port.

Is there anything in !Allocate that sounds like it might fit? If not, try emailing the allocate address directly (it is a human, not a machine).

There are still uses for serial. Connecting older hardware, for instance. Plus it is also one of the simplest ways to connect two devices (using Ethernet is more flexible but it has much higher demands). It is such a shame that some sort of serial was pretty ubiquitous back in the home micro era, but the ones on the SoC boards are the absolute bare minimum (if that).

It is such a shame that some sort of serial was pretty ubiquitous back in the home micro era, but the ones on the SoC boards are the absolute bare minimum (if that).

It’s a pain in the nether when you need to connect to a network switch by serial to do the initial setup and manufacturer after manufacturer is removing the serial port. As for tablets with no USB to patch in a USB-serial…

who assigns the number for a new serial blockdriver?

Nothing to do with ROOL, try this page ?

Nothing to do with ROOL, try this page

Perhaps an approach from ROOL to XAT to transfer the resource (and source) is in order?
Certainly less chasing around for users.

Guys from ROOL: please check your info@ mail.