From: William Hubbs <w.d.hubbs@gmail.com>
To: speakup@braille.uwo.ca
Subject: Re: floating serial ports issue fixed
Date: Mon, 21 Jul 2008 07:26:53 -0500 [thread overview]
Message-ID: <20080721122653.GA23450@linux1> (raw)
In-Reply-To: <18564.13056.60362.622775@ccs.covici.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
All,
I replied to John privately, but this was meant to go to the list.
There is a way for speakup to get the port once the serial driver has
seen it, so there is not an issue with speakup or the accessibility
drivers loading after the serial port driver is loaded. This is also
how speakup gets the port if it is loaded as modules.
Thanks,
William
On Mon, Jul 21, 2008 at 02:56:00AM -0400, John covici wrote:
> If the accessibility drivers are loaded later than the serial drivers,
> how does speakup ever get a port at all since its already taken by the
> drivers?
>
> on Sunday 07/20/2008 William Hubbs(w.d.hubbs@gmail.com) wrote
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > All,
> >
> > as of this message, I made a change to the way speakup installs to
> > kernels 2.6.25 and lower which should fix the floating serial ports
> > issue when speakup and the serial driver are built into the kernel.
> >
> > The issue was that when both speakup and the 8250 serial driver were
> > built in, speakup would initialize first and reserve the serial port for
> > the synthesizer. Then, the 8250 driver would initialize and since
> > speakup would have one port already reserved, the 8250 driver would
> > renumber the ports with higher numbers to one lower than they would be
> > if speakup was not running.
> >
> > If you are using speakup installed into the kernel source and not
> > building as external modules and using a kernel before 2.6.26, you need
> > to start with a fresh kernel tree before doing the update.
> >
> > For 2.6.26, this should not be an issue, since the accessibility drivers
> > are loaded later than the serial driver.
> >
> > Thanks,
> >
> > William
> >
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v2.0.9 (GNU/Linux)
> >
> > iEYEARECAAYFAkiEEKQACgkQblQW9DDEZThYUwCfQJelIMinqoJClMGya4JRN/Vc
> > BkcAmQGlkTUfEF1kmSHSCjpVWaIctFxL
> > =aJy4
> > -----END PGP SIGNATURE-----
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
> --
> Your life is like a penny. You're going to lose it. The question is:
> How do
> you spend it?
>
> John Covici
> covici@ccs.covici.com
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
iEYEARECAAYFAkiEgI0ACgkQblQW9DDEZTiIFQCfWdcCBDEdj7YH+g+YY0wmj/Pd
7/oAnjNadcK17v/uel7nIJb9q2b0/zwc
=bi3V
-----END PGP SIGNATURE-----
prev parent reply other threads:[~ UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
William Hubbs
` John covici
` William Hubbs [this message]
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=20080721122653.GA23450@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).