|
Yep, I mentioned the standard API issue before... That opportunity was missed with the clockport, and as a result drivers have to probe the hardware themselves, with the potential to upset other hardware and drivers, and with things like clockport splitters having to be explicitly supported by the driver instead of simply attempting to open the clockport with a relevant unit number.
As for whether this interface would work with a clockport splitter, that depends on how the driver is written. It *should* work with a Prisma in most cases since the Prisma can be used on any port whereas non-splitter-aware drivers will only work on port 0. The only issue might be funky behaviour of either board from probing reads/writes of the other's driver.
|