MIDI Driver + Kernel Extension, combine?
MIDI Driver + Kernel Extension, combine?
- Subject: MIDI Driver + Kernel Extension, combine?
- From: "daniel åkerud" <email@hidden>
- Date: Fri, 31 Mar 2006 10:17:45 +0200
Hi,
I have made a Kernel Extension that communicates with a MIDIServer
MIDI Driver. The Kernel Extension is sending messages using an IO
queue over share memory. The MIDI Driver creates a MIDI input
(Endpoint) for use in MIDI sequencers. So far so good. The kernel
extension actually is not communicating with a hardware device, but is
"listening" to devices already present (or added) which is the reason
it need to run in kernelspace.
Currently these are two completely separate entities, and need to be
installed separately in two different locations. I was wondering, is
there some way to combine the two? What enters my mind is:
(1) the Kernel Extension can BE a MIDIServer MIDI Driver (really good,
but possible?)
(2) the MIDIServer can actually BE a kernel extension also (really
good also... possible)
(3) the MIDIServer MIDI Driver can load and unload the kernel
extension when loaded (bad, still better than what I have now).
Thanks for any help,
/Daniel Åkerud
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden