From: David <david.a.borowski@gmail.com>
To: speakup@linux-speakup.org
Subject: using system serial drivers
Date: Sat, 19 Nov 2016 11:28:34 -0500 [thread overview]
Message-ID: <20161119162834.GA2026@db> (raw)
I have not measured the performance of doing bulk vs one char transfers.
Have any of you bothered to read the code in the driver you are calling
and see what overhead is imposed on entry/exit? It is quite abit.
Some synths already have their own catch up handlers, so it would be quite
easy to write a new do_catchup that used the new serial
i/o and each synth could call the new one when appropriate.
With respect to isa cards, I wrote the dec pc driver for the
old long isa card so I am aware of the fact that
all drivers do not use serial ports.
next reply other threads:[~ UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
David [this message]
` Samuel Thibault
` Samuel Thibault
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=20161119162834.GA2026@db \
--to=david.a.borowski@gmail.com \
--cc=speakup@linux-speakup.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).