All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bill Adair" <adair@gotadsl.co.uk>
To: alsa-devel@lists.sourceforge.net
Subject: Serial port MIDI devices - Opcode Studio 64X
Date: Tue, 07 Dec 2004 17:20:10 -0000	[thread overview]
Message-ID: <opsinefwk1n0kn27@biotracedesign.com> (raw)

I'm about to have a look at developing an ALSA serial port driver
for the Opcode Studio 64X. Does anyone else have an interest in this
device, or similar hardware?

The Roland Sound Canvas and Midiator devices seem to be similar to the
specification I have. There are four stages Detection, Sign-On,  
MIDI-Transfer
and Sign-Off. The interface toggles the CTS and the PC responds on RTS  
during
detection and then the two lines are used during MIDI-Transfer to prevent  
buffer
overflow.

Where would be the best place to add this code? I'm a little confused by  
the
way all the functionality is laid out. The following is a list of routines  
 from the
serial-u16650.c file. Is there a guide anywhere that says which routines  
are called by
ALSA to "do" operations i.e. if I want to detect my hardware I need check  
a port
for response. Which routine should this be done in? Is this triggered by  
loading a driver?
etc.

snd_uart16550_add_timer()
snd_uart16550_del_timer()
snd_uart16550_buffer_output()
snd_uart16550_io_loop()
snd_uart16550_interrupt()
snd_uart16550_buffer_timer()
snd_uart16550_detect()
snd_uart16550_do_open()
snd_uart16550_do_close()
snd_uart16550_input_open()
snd_uart16550_input_close()
snd_uart16550_input_trigger()
snd_uart16550_output_open()
snd_uart16550_output_close()
snd_uart16550_buffer_can_write()
snd_uart16550_write_buffer()
snd_uart16550_output_byte()
snd_uart16550_output_write()
snd_uart16550_output_trigger()
snd_rawmidi_ops_t snd_uart16550_output =
snd_rawmidi_ops_t snd_uart16550_input =
snd_uart16550_free()
snd_uart16550_dev_free()
snd_uart16550_create()
snd_uart16550_rmidi()
snd_serial_probe()
alsa_card_serial_init()
alsa_card_serial_exit()
module_init()
module_exit()

Bill


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/

                 reply	other threads:[~2004-12-07 17:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=opsinefwk1n0kn27@biotracedesign.com \
    --to=adair@gotadsl.co.uk \
    --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.