From: Brent Harding <bharding@doorpi.net>
To: blinux-list@redhat.com
Subject: Re: Digital Talking Book Standard
Date: Mon, 19 Nov 2001 23:19:57 -0600 [thread overview]
Message-ID: <3.0.6.32.20011119231957.00aaa240@mail.doorpi.net> (raw)
In-Reply-To: <Pine.LNX.4.33.0111191409370.3206-100000@toccata.grg.afb.ne t>
Wonder why that port is there. I heard a tivo can be made to support
logins. If it has audio in, maybe it could be adapted to do sound
processing with, but adjusting parameters would be one thing, getting it's
buttons to tell sox to increase different values depending what you press,
probably not possible.
At 02:10 PM 11/19/01 -0500, you wrote:
>On Mon, 19 Nov 2001, Nicolas Pitre wrote:
>
>>
>> And... just to please everyone on this list: Victor is runing Linux inside.
>>
>And, it has a most tantalizing db9 port on the back. Sure looks like a
>serial port to me. Don't suppose it supports login over that port, now,
>does it?? <grin>
>
> >
>> Nicolas
>>
>>
>>
>> _______________________________________________
>> Blinux-list mailing list
>> Blinux-list@redhat.com
>> https://listman.redhat.com/mailman/listinfo/blinux-list
>>
>
>--
>
> Janina Sajka, Director
> Technology Research and Development
> Governmental Relations Group
> American Foundation for the Blind (AFB)
>
>Email: janina@afb.net Phone: (202) 408-8175
>
>Chair, Accessibility SIG
>Open Electronic Book Forum (OEBF)
>http://www.openebook.org
>
>Will electronic books surpass print books? Read our white paper,
>Surpassing Gutenberg, at http://www.afb.org/ebook.asp
>
>Download a free sample Digital Talking Book edition of Martin Luther
>King Jr's inspiring "I Have A Dream" speech at
>http://www.afb.org/mlkweb.asp
>
>Learn how to make accessible software at
>http://www.afb.org/accessapp.asp
>
>
>
>_______________________________________________
>Blinux-list mailing list
>Blinux-list@redhat.com
>https://listman.redhat.com/mailman/listinfo/blinux-list
>
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
Martin G. McCormick
` Saqib Shaikh
` Peter Toneby
` Janina Sajka
` Peter Toneby
` Nicolas Pitre
` Peter Toneby
` Lloyd G. Rasmussen
` Nicolas Pitre
` Nicolas Pitre
` Peter Toneby
` Janina Sajka
` Nicolas Pitre
` Janina Sajka
` Nicolas Pitre
` Brent Harding
` Nicolas Pitre
[not found] ` <Pine.LNX.4.33.0111191409370.3206-100000@toccata.grg.afb.ne t>
` Brent Harding [this message]
[not found] ` <Pine.LNX.4.33.0111191147560.2815-100000@toccata.grg.afb.ne t>
` Brent Harding
` Nicolas Pitre
` Joel Zimba
` Brent Harding
` Brent Harding
` Nicolas Pitre
` philwh
` Janina Sajka
` Brent Harding
` Buddy Brannan
` Brent Harding
[not found] ` <Pine.LNX.4.33.0111191114500.2815-100000@toccata.grg.afb.ne t>
` Brent Harding
` Luke Davis
` cbowman
` ssh A. R. Vener
` ssh cbowman
` ssh Luke Davis
` ssh Andor Demarteau
` ssh Luke Davis
` ssh Fredrik Larsson
` ssh Luke Davis
` ssh Fredrik Larsson
` ssh cbowman
` ssh A. R. Vener
` ssh A. R. Vener
` ssh Luke Davis
` Digital Talking Book Standard Brent Harding
` cbowman
` Luke Davis
` cbowman
` Janina Sajka
` Pratik Patel
` Brent Harding
-- strict thread matches above, loose matches on Subject: below --
Janina Sajka
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.20011119231957.00aaa240@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).