From: William Hubbs <w.d.hubbs@gmail.com>
To: speakup mailing list <speakup@braille.uwo.ca>
Subject: Re: Which hardware synthesizer to buy?
Date: Mon, 13 Apr 2009 18:10:50 -0500 [thread overview]
Message-ID: <20090413231050.GA20710@linux1> (raw)
In-Reply-To: <18915.45617.500577.132483@ccs.covici.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi John,
On Mon, Apr 13, 2009 at 05:44:17PM -0400, John covici wrote:
> Could not you have an option to accept that change of numbering, and
> let the user decide whether he wants that sort of thing? I thought
> there were other issues involved. Since I always built the kernels
> the same I got used to the numbering and let it go -- or what I was
> thinging of was to have theearly boot work as before and do a
> switcheru once the serial driver came up so the speakup port would get
> its number again. Does that make any sense?
Yes, it does make sense, but the issue is not just that the number is
different. If speakup grabs the first port first, the kernel serial driver
does not see the port at all; that is why the second port gets numbered
ttyS0. So, the kernel only sees one port until you reboot and do not
start speakup, even if you disable the synth in speakup.
William
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.10 (GNU/Linux)
iEYEARECAAYFAknjxnoACgkQblQW9DDEZThu7ACeLZE3Vupdk1mYwT3fHN8kIo/t
14UAnjUjTcydWRdLh3lKjo4g5l67NKMn
=lBYv
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
Gaijin
` Nick Stockton
` Gaijin
` Kirk Reiser
` John covici
` al Sten-Clanton
` Gregory Nowak
` William Hubbs
` John covici
` William Hubbs [this message]
` John covici
` Gregory Nowak
` William Hubbs
` Chris Brannon
` Gregory Nowak
` Chris Brannon
` Gregory Nowak
` Alex Snow
` virtualization, was: " Gregory Nowak
` Alex Snow
` Gregory Nowak
` Gaijin
` Garrett Klein
` Janina Sajka
` Gaijin
` William Hubbs
` Tony Baechler
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=20090413231050.GA20710@linux1 \
--to=w.d.hubbs@gmail.com \
--cc=speakup@braille.uwo.ca \
/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).