Re: Status update

I hadn't really looked into the 'V2' version of the module much after=20
the checkin.
I know that using the same code using my AWE64, it would go into KDL=20
right after the=20
the open hook was called.  I couldn't really think of a reason that=20
would require a=20
different method.   I'll take another look at it.

Not sure about the midi parser either.  It looked like it was a=20
carryover that doesn't=20
have much purpose anyway.=20
 If you have any ideas, let me know,
Greg

> MPU401 AND THE KERNEL MODULES
>=20
> I know that it has been in the CVS for quite a while now, but I=20
> finally
> looked over the MPU401 module code that was submitted by Greg Crain :
> -)
> Thanks again for your contribution, Greg. The missing "v2" interface=20
> support
> is not a major disaster, as far as I am concerned. Our kernel may not=20
> be
> binary compatible with the old R5 drivers anyway, in which case we=20
> will have
> to rely on new drivers -- none of them is likely to use v2.
>=20
> I think we will drop the midi parser kernel module. As far as I can=20
> tell, no
> one is using it, so why bother supporting it. It looks like something=20
> that
> was intended for the Media Kit anway ;-)
>=20
> DRIVERS AND THE MIDI PARSER
>=20
> A little while ago, Christian Packmann contributed an improved parser=20
> for
> raw MIDI streams. I integrated this with the midi_server. This code=20
> is used
> to read MIDI messages from from device drivers, i.e. from MIDI IN=20
> ports. Now
> it should handle "running status" and "realtime data in non-sysex=20
> messages"
> properly. Thanks Christian! I tested this code in a separate=20
> application and
> it worked very well; I hope it works as well in the midi_server :-) I=20
> did
> make a few small changes here and there, but nothing extensive.
>=20