public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Kitty Litter" <n8kl@insightbb.com>
To: "Speakup is a screen review system for Linux."
	<speakup@linux-speakup.org>
Subject: Re: Serial ports with 32-bit vs. 64-bit processors
Date: Thu, 16 May 2013 05:55:57 -0400	[thread overview]
Message-ID: <CF75A398CB6C4A5BAEF392D32E502509@randy3> (raw)
In-Reply-To: <5194A1E8.2070300@baechler.net>

I recently compiled kernel version 3.9.2 and got speakup working with my 
audapter serial synth on a debian 32 bit system. I removed the error 
checking about stealing ports and also modified spk_serial_release by 
commenting out synth_release_region. This fixed a problem where the synth 
wouldn't get released and speakup-soft wouldn't work. I don't care enough to 
try this on a 64 bit system.


  reply	other threads:[~ UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Slack 13.37 and 14.0 Mitchell D. Lynn
 ` Tony Baechler
   ` Mitchell D. Lynn
     ` Tony Baechler
       ` Mitchell D. Lynn
         ` Tony Baechler
           ` Mitchell D. Lynn
           ` covici
             ` Mitchell D. Lynn
               ` covici
                 ` Mitchell D. Lynn
                   ` Onboard serial ports Tony Baechler
                     ` John G. Heim
                       ` Mitchell D. Lynn
                       ` Jason White
                   ` Slack 13.37 and 14.0 John G. Heim
             ` Adam Myrow
               ` Mitchell D. Lynn
               ` Serial ports with 32-bit vs. 64-bit processors Tony Baechler
                 ` Kitty Litter [this message]
                 ` John G. Heim
                   ` Ryan Hutchings
                     ` John G. Heim
                   ` Tony Baechler
                 ` covici
                   ` Keith Wessel
           ` Slack 13.37 and 14.0 Gregory Nowak
             ` Tony Baechler
   ` Ryan Hutchings
     ` Debian Squeeze CDs Tony Baechler
       ` Ryan Hutchings
   ` Slack 13.37 and 14.0 Alex Snow
     ` Mitchell D. Lynn

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=CF75A398CB6C4A5BAEF392D32E502509@randy3 \
    --to=n8kl@insightbb.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).