public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Nick Gawronski" <nick@nickgawronski.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: dectalk express drivers
Date: Thu, 5 Apr 2007 21:02:16 -0600	[thread overview]
Message-ID: <003901c777f7$ff15e180$270110ac@CHIHUAHUAL1> (raw)
In-Reply-To: <20070404140041.GA21146@lava-net.com>

Hi, possibley that is why I am not able to use the dectalk express in the 
kernel 2.6.20 with fedora core 6.  Will this problem get fixed as not able 
to use the newer kernels will leave my system open to security bugs that are 
sometimes fixed in redhat's kernels and other distributions will also be 
upgrading to the latest kernels.
----- Original Message ----- 
From: "Igor Gueths" <igueths@lava-net.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Wednesday, April 04, 2007 8:00 AM
Subject: Re: dectalk express drivers


> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> Hi. You're going to have to downgrade your kernel and Speakup revision to 
> that of which was committed when 2.6.19.2 was released. In the later 
> kernel (s), the dectlk driver is currently
> broken.
> On Wed, Apr 04, 2007 at 02:15:55AM -0400, josh@techlab.cviatlanta.org 
> wrote:
>> Hi all,
>> Could someone help me get the dectalk express driver working under 
>> 2.6.20x?  I'm working with two servers that run
>> 2.6.20x kernels and need the express to work.  Neither my coleague nor I 
>> have been able to figure out why the current
>> code for probing for dectalk won't work.  Any help would be appreciated.
>> Cheers,
>> Josh
>>
>>
>> _______________________________________________
>> Speakup mailing list
>> Speakup@braille.uwo.ca
>> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>>
>> -- 
>> This message has been scanned for viruses and
>> dangerous content by MailScanner, and is
>> believed to be clean.
>>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2.2 (GNU/Linux)
>
> iQIVAwUBRhOviae2pgKIdGq4AQpNlxAAju5g8Nd4bBP/GOok++kz+SKuXZfGGiV9
> wQEMp0GOI9BWLJoR+5Ko6Fw/Buwh6WzisKJeShHl4nnmg7id+qWiQQp1B7xSHalp
> rfzk2zv7qJQtdGlkgW2914N33WXXhipnqmTIzzTrp9X8tED8PZ6tmTCicfVr/NVI
> wGinEdso1nqJrWKFt0JmBJ8RfV+mcN/xSBot0jJX+mGZd9GmPLJzffqKF2FdadQ/
> K4XlDD2Jc511anw8cWNwAtB8GtZcFnNruw1twFo5gK6X42LVJTXr79n4OHNJWhr3
> 0zfLbPJ7aicxBwUnBd0Ez85YA/zXcbg15yjSye581hFaHtWkybDpHKj9RafX1D92
> O7G22BLXD3eWgDuOVH5Pm2AeM3Uj0FAbVTyE4AmDutrakFk9+hx/Ykhk21jFPXCP
> 27Wm+sf7ibrFj+aROMLwfC7MvXBTnxp+fqjBp5Ibjf1lY4wxWY6jEHoQZNq9i/55
> s3lE60aJw0nYQRhjrJAvIVoe4iRWQwXSikeQ+kCOVimJgnaj5fNd7md2fsfTG+Lx
> HsgQODwwQna3KZVvQtSHEmvKOqiUXCHdxaFFCOaQXwFJg67dqvwEtIHK9KMY1MSh
> yKJkUjmJDVlDUIUQMYtB14Na8yCghLa6frML8jQ9UxdwjZ4+LTAuSEcpiNZhBVoZ
> ULKudR0H/Jg=
> =6YC6
> -----END PGP SIGNATURE-----
>
> -- 
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 



      reply	other threads:[~ UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 josh
 ` Igor Gueths
   ` Nick Gawronski [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='003901c777f7$ff15e180$270110ac@CHIHUAHUAL1' \
    --to=nick@nickgawronski.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).