Jacom Meuser responded to Oko's post on the mailing list, he said that OSSv4 is different from OSSv3.. which is implemented via
ossaudio(3).
Having OSSv4 as a port would be problematic, it would have to be distributed as a kernel module.. unfortunately it would conflict with the other audio drivers, so users would have to disable them all prior to using it.. making their kernel unsupported by the OpenBSD developers.
http://marc.info/?l=openbsd-misc&m=124321644617877&w=2
Personally, I don't think a OSSv4 port is needed.. the current audio framework and drivers work well, a bonus is that they've been audited along with the rest of the code base.. I'm really excited about the new sndio API, most of the major ports have already been modified to utilize it now, so this fulfils the mixing feature that many people mistakenly believe should be done in the kernel.
Quote:
Originally Posted by vermaden
This should not be such serious case IMHO, similar thing happened with kqemu accelration module, while OpenBSD does not support loadable modules, they can link modules before boot, so OSS4 should also work with this IMHO.
|
OpenBSD supports the LKM framework, kernel modules can be loaded.. securelevel must be <= 0 for it to work though, not sure what you mean about "linking modules before boot", it surely does no such thing.. but as said above, OSSv4 would conflict with the current audio drivers.