public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "John Heim" <jheim@math.wisc.edu>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: 2.6.22 kernel
Date: Wed, 26 Sep 2007 15:59:47 -0500	[thread overview]
Message-ID: <099001c80080$2c0fb560$4ba65c90@vv507j> (raw)
In-Reply-To: <20070926194536.GD5277@hittsjunk.net>

I  don't get a default synth anymore in kernel config.   The last thing is 
something about a dummy synth.

If there's no /proc/speakup/synth_name, then do you still specify your synth 
as a kernel parameter with the synth_name  parameter?



----- Original Message ----- 
From: "Kenny Hitt" <kenny@hittsjunk.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Wednesday, September 26, 2007 2:45 PM
Subject: Re: 2.6.22 kernel


> Hi.  Yes I have compiled a 2.6.22 kernel and no you shouldn't see a 
> synth_name entry in /proc/speakup.
> Either modprobe the module for your synth driver or set the default synth 
> during config if you build in the driver.
>
> ***Worning*** don't build in more than one driver or you will have 
> problems.  Building as modules is the best way to go.
>
>          Kenny
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
> 



  parent reply	other threads:[~ UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 John Heim
 ` John Heim
   ` Chuck Hallenbeck
   ` Kenny Hitt
     ` Sean M McMahon
     ` John Heim [this message]
       ` using the Braillenote Pk as a hardware synth for speakupmodified fadora Scott Ford
         ` Gregory Nowak
       ` 2.6.22 kernel Kirk Reiser
         ` John Heim

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='099001c80080$2c0fb560$4ba65c90@vv507j' \
    --to=jheim@math.wisc.edu \
    --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).