From: Brent Harding <bharding@doorpi.net>
To: blinux-list@redhat.com
Subject: RE: Doubletalk Lt and Re: DEC PC1 Support
Date: Sun, 18 Nov 2001 19:36:33 -0600 [thread overview]
Message-ID: <3.0.6.32.20011118193633.00a99460@mail.doorpi.net> (raw)
In-Reply-To: <LOBBIDKCMJJAJGPMIIAAOEDLEDAA.gena@gena-j.net>
Yes, I discovered that on compiling my system kernel. I eliminated all of
them but what I use, double talk Pc and maybe dectalk express for my
laptop, if I decide to use the kernel there.
At 02:28 PM 11/18/01 -0000, you wrote:
>Hi
>
>True for pre 2.2.18 kernels but specific kernels for each synth is not
>necessary now. Kernels can support all of the synths that Speakup supports
>and the synth is selected by passing parameters to the kernel at boot time
>in kernels later than 2.2.17..
>
>
>-----Original Message-----
>From: blinux-list-admin@redhat.com
>[mailto:blinux-list-admin@redhat.com]On Behalf Of Brent Harding
>Sent: 18 November 2001 04:45
>To: blinux-list@redhat.com
>Subject: Re: Doubletalk Lt and Re: DEC PC1 Support
>
>
>Think speakup does, ltlk.bin, remember finding it on the sight in disks
>somewhere.
>At 11:25 PM 11/17/01 -0500, you wrote:
>>I was afraid of that. Any alternatives?
>>
>>What supports the Doubletalk LT?
>>
>>Luke
>>
>>On Sun, 18 Nov 2001, Saqib Shaikh wrote:
>>
>>> Emacspeak
>>> ----- Original Message -----
>>> From: "Luke Davis" <ldavis@shellworld.net>
>>> To: <blinux-list@redhat.com>
>>> Sent: Sunday, November 18, 2001 4:18 AM
>>> Subject: DEC PC1 Support
>>>
>>>
>>> > What Linux screen reading software is currently supporting the DEC PC1
>>> > boards?
>>> >
>>> > Thanks
>>> >
>>> > Luke
>>> >
>>> >
>>> >
>>> > _______________________________________________
>>> > Blinux-list mailing list
>>> > Blinux-list@redhat.com
>>> > https://listman.redhat.com/mailman/listinfo/blinux-list
>>>
>>>
>>>
>>> _______________________________________________
>>> Blinux-list mailing list
>>> Blinux-list@redhat.com
>>> https://listman.redhat.com/mailman/listinfo/blinux-list
>>>
>>
>>
>>
>>_______________________________________________
>>Blinux-list mailing list
>>Blinux-list@redhat.com
>>https://listman.redhat.com/mailman/listinfo/blinux-list
>>
>>
>
>
>
>_______________________________________________
>Blinux-list mailing list
>Blinux-list@redhat.com
>https://listman.redhat.com/mailman/listinfo/blinux-list
>
>
>
>_______________________________________________
>Blinux-list mailing list
>Blinux-list@redhat.com
>https://listman.redhat.com/mailman/listinfo/blinux-list
>
>
prev parent reply other threads:[~ UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
Luke Davis
` Saqib Shaikh
` Doubletalk Lt and " Luke Davis
` Saqib Shaikh
[not found] ` <Pine.BSF.4.41.0111172324160.56493-100000@server1.shellworl d.net>
` Brent Harding
` Georgina
` Brent Harding [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=3.0.6.32.20011118193633.00a99460@mail.doorpi.net \
--to=bharding@doorpi.net \
--cc=blinux-list@redhat.com \
/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).