From: Takashi Iwai <tiwai@suse.de>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: Paul Davis <paul@linuxaudiosystems.com>,
Mark Knecht <markknecht@attbi.com>,
Alsa-Devel <alsa-devel@lists.sourceforge.net>
Subject: Re: HDSP 9652 MIDI - A timing disaster?
Date: Mon, 13 Jan 2003 16:28:53 +0100 [thread overview]
Message-ID: <s5h1y3hvzka.wl@alsa2.suse.de> (raw)
In-Reply-To: <Pine.HPX.4.33n.0301131514430.24645-100000@studcom.urz.uni-halle.de>
At Mon, 13 Jan 2003 15:28:58 +0100 (MET),
Clemens Ladisch wrote:
>
> Paul Davis wrote:
> > >The hdsp driver doesn't send more than one MIDI byte per timer tick.
> > >IMHO it should be modified to send in a loop until the FIFO is full
> >
> > that's what this tried to do:
> > (...)
> > how does this end up writing only a single byte? unless n_pending is
> > always either 0 or 1, which on closer inspection, i see that it is
> > ... yikes.
> >
> > >sending in output_trigger() instead of delaying it to the next timer tick.
> >
> > hmm. i modelled this code on another PCI driver that had MIDI
> > support. is there an example you can point me to that starts from
> > within the equivalent output_trigger?
>
> e.g. isa/sb/sb8_midi.c or drivers/mpu401/mpu401_uart.c
>
> And both output one byte at a time in a loop until the output fails.
> (However, snd_sb8dsp_midi_output_write() doesn't check for a full FIFO.)
well, generally it's not a good style to process in such a loop in the
primary interrupt handler. we should rewrite them using tasklet...
Takashi
-------------------------------------------------------
This SF.NET email is sponsored by: FREE SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
next prev parent reply other threads:[~2003-01-13 15:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-11 15:49 HDSP 9652 MIDI - A timing disaster? Mark Knecht
2003-01-13 9:04 ` Clemens Ladisch
2003-01-13 13:15 ` Paul Davis
2003-01-13 14:28 ` Clemens Ladisch
2003-01-13 15:28 ` Takashi Iwai [this message]
2003-01-14 5:16 ` Mark Knecht
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=s5h1y3hvzka.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=clemens@ladisch.de \
--cc=markknecht@attbi.com \
--cc=paul@linuxaudiosystems.com \
/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.