From: William Hubbs <w.d.hubbs@gmail.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: quick fix for 2.6.34 problem with serial synths
Date: Tue, 29 Jun 2010 10:58:06 -0500 [thread overview]
Message-ID: <20100629155806.GA11958@linux1> (raw)
In-Reply-To: <655143C87515406DA13CF0DF52E1AC47@randy3>
On Sun, Jun 27, 2010 at 01:52:01PM -0400, Kitty Litter wrote:
> In speakup/src/serialio.c comment out the return (NULL); line just below
> __release_region.
> Looking at the kernel source in kernel/resource.c it seems that if
> __release_region fails you would get a kernel message. So speakup seems to
> think it fails but the kernel doesn't.
> Someone with more smarts than me maybe can figure this all out.
Actually the failure was happening on the line below that in the call to
synth_request_region.
I don't have a fix for that yet, but now the code is set up to log the
error code and port number if that fails so hopefully we can see what is
going on.
Are you comfortable with pulling from git and testing with that code?
Any help would be appreciated.
Thanks,
William
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
Kitty Litter
` William Hubbs [this message]
` Steve Holmes
` Steve Holmes
` Joshua Lambert
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=20100629155806.GA11958@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).