> Cameron Grant:
> |you should be aware that the voxware code will need extensive renovation
> |conversion to newbus. already it will not cope with pnp devices, and
> |compatibility shims it relies on will shortly be gone.
> |in my opinion it would be far better to divert any effort you would be
> |willing to put in towards newpcm.
> That sounds fine in the abstract. But we should be concrete about the
> details before we go nixing code.
> - Have we identified exactly what functionality is missing in the new
> sound driver but supported by Voxware?
to my knowledge, midi is the only functionality missing. also, multiple
opens of /dev/dsp are not yet implemented. both will be soon.
> - Have we got volunteers with time on their hands signed up to provide
> each piece of this functionality with estimated completion dates?
> IMO, the cut-over to PCM should be tied to the last of these completion
> dates, revised forward or backward as actual completion dates slip.
> Why would we transition any other way?
because various functionality voxware uses is now optional and will be gone
in the coming weeks. the kernel does not revolve around sound, and voxware
is an acceptable loss. once the isa shims are gone, voxware will not
compile without being newbusified which is a task of great magnitude.
at this time, the point is moot. unless someone comes forward with a
newbusified voxware, it will be removed soon. i, and others, will want to
see code, not promises.
-cg, not meaning to sound harsh
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message