> I will be glad to read it then. I would also like, if my aruments > convinced you that at least a basic treatment of the architecture of > alsa is necessary, assist you in writing something up.
Thanks, any help wil be wellcome. And, yes, i am convinced: a basic treatment of the vertical view of the architecture will be present, but not as the key structure of the document, i prefer an horizontal division. In fact, i think that a block diagram is perfect for give the reader both ideas. > The question to your answer about virmidi is partly a question of hw/sw > layer. As far as i know, virmidi installs a virtual soundcard in the > system that has nothing but some "physical" midi ports. It works on the > kernel module layer, because a normal seq-client cannot create a > physical port. This is useful to interconnect alsa apps, that explicitly > request a physical midi port to read/write to.. That one was on the source code virmidi.c (funny place for documenting that :-) So, the summary statement will be: 'virmidi is a virtual rawmidi device that allows old applications that only support rawmidi (are no sequencer ready) to be connected using the sequencer.' So, what it wraps are legacy applications not legacy drivers as I missunderstood. Great! One more question solved. Now only 8 of 10 questions remaining. :-) -- David García Garzón <[EMAIL PROTECTED]> Phone: 034 93 542 21 99 Music Technology Group, Institut Universitari de l'Audiovisual Universitat Pompeu Fabra ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Alsa-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-user
