From: list@phasorlab.de (Matthias König)
To: alsa-devel@lists.sourceforge.net
Subject: Ego Sys, Miditerminal 4140 Driver
Date: Thu, 30 Mar 2006 18:48:47 +0200 [thread overview]
Message-ID: <87psk3ubdc.fsf@zebra.localdomain> (raw)
Hello alsa-devel,
I own a Miditerminal 4140 by ESI, which is a 4 In 4 Out Midi interface
with SMPTE timecode generation for the parallel port. Since I want
this device to work under Linux, I've been working on a driver for
ALSA.
It seems that I have some success now. At least I can receive and
transmit Midi bytes on all 4 In/Out ports. Maybe someone with more
experience in driver development could take a look at the driver?
A preliminary version is available from
www.phasorlab.de/alsa/mts64.tar.bz2
Any comments and critics would be highly appreciated.
There is still some work to do, the SMPTE timecode generation will
need some kind of control for start/stop of timecode generation and
setting the time (timecode generation is done by hardware). I'm not
yet sure how to do this; can this be done by ALSA control elements
or do I have to create a hwdep device, which would use ioctl?
Again, suggestions would be welcome.
Regards,
Matthias
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
next reply other threads:[~2006-03-30 16:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-30 16:48 Matthias König [this message]
2006-03-30 17:01 ` Ego Sys, Miditerminal 4140 Driver Clemens Ladisch
2006-03-31 18:53 ` Matthias Koenig
2006-04-04 16:10 ` Clemens Ladisch
2006-04-05 11:36 ` Matthias Koenig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87psk3ubdc.fsf@zebra.localdomain \
--to=list@phasorlab.de \
--cc=alsa-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.