public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "tyler" <compgeek13@gmail.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Linux on BrailleNotes
Date: Wed, 1 Feb 2006 15:23:55 -0800	[thread overview]
Message-ID: <003001c62786$926f33a0$ae1dae48@dataplus4puarg> (raw)
In-Reply-To: <20060201142351.GA31252@tomass.dyndns.org>

there are a lot of processors that are built into linux rite now that I am 
sure weren't supported a long time ago. If you say "No, we can't do it", 
then we can't. Same thing with every day life. If someone puts you on a 
computer for your first time, and you say "no, I can't do it," then you 
can't, personally, who ever thought of the idea of taking the text to speech 
was a freaken genious! And, he didn't let himself get held back, he didn't 
say I can't use a computer, just because someone hasn't done it for me. He 
got off his butt and did it!

Tyler Littlefield.
Check out our website:
http://tysplace.the-leetest.net
check out my blog:
livejournal.com/~tylerrl
[my programs don't have bugs, just randomly added features]
[failure is not an option, it comes bundled with windows!]
----- Original Message ----- 
From: "Thomas Stivers" <stivers_t@tomass.dyndns.org>
To: <speakup@braille.uwo.ca>
Sent: Wednesday, February 01, 2006 6:23 AM
Subject: Re: Linux on BrailleNotes


> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: RIPEMD160
>
> On Wed, Feb 01, 2006 at 08:32:05 AM -0500, Ann K. Parsons wrote:
>> Hi all,
>>
>> No, the BrailleNote's OS is Window-CE, but it's interface is
>> proprietory.  You cannot put Linux on it.  You can, however use BrlTTY
>> with a PC running Linux.  Sorry, but that's the story.
>
> Well when I got it my pc's OS was windows 98 and its interface was
> claimed to pe proprietary. Windows CE isn't magic or anything, it runs
> on processors just like linux. I believe the bn uses an xscale processor
> or some such which if it isn't supported yet likely will be at some
> point. A big difficulty likely to be encountered is with geting
> specifications for the hardware out of humanware without them wanting an
> NDA signed. That was IIRC a big part of the problem in supporting the
> keynote synthesizers with speakup. Without specifications its left to
> developers to reverse engineer protocols and such for using the
> hardware. Given that we have a very limited group of developers, myself
> definitely excluded, with the skills to do all this work and we don't
> have the whole big world of linux developers hacking on braillenotes
> linux on a bn isn't impossible by any means, but will take a lot of time
> and interest from people with knowhow.
>
> Well there's my take, and now its time for me to work on getting more of
> that knowhow I was talking about.
>
> P.S. if you really want linux, brltty, and speakup on a braillenote send
> a BN to Linus, Kirk, and whoever the brltty guy is, and hell if you have
> that kind of money you can send one my way too. *grin*
>
> - -- 
> "Debugging is twice as hard as writing the code in the first place.
> Therefore, if you write the code as cleverly as possible, you are,
> by definition, not smart enough to debug it." - Brian W. Kernighan
>
> Thomas Stivers e-mail: stivers_t@tomass.dyndns.org
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2 (GNU/Linux)
>
> iD8DBQFD4MR35JK61UXLur0RA0+NAJ0YeQT8tiHvpm5yAKOoGIRbcC+1xQCdHNii
> vn9NT8ryyKR85a97RG4ehJA=
> =l/gT
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup 



  reply	other threads:[~ UTC|newest]

Thread overview: 79+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Thomas Stivers
 ` tyler [this message]
  -- strict thread matches above, loose matches on Subject: below --
 Dawes, Stephen
 Terry D. Cudney
 ` tyler
 Chris Norman
 ` Luke Yelavich
   ` BlindTech of BlindTechs.Net
     ` Ann K. Parsons
       ` BlindTech of BlindTechs.Net
       ` David Poehlman
         ` BlindTech of BlindTechs.Net
           ` Gregory Nowak
         ` tyler
           ` David Poehlman
   ` Travis Siegel
     ` tyler
 ` David Poehlman
   ` Charles Hallenbeck
     ` Glenn at home
       ` tyler
         ` Glenn at home
           ` tyler
 ` BlindTech of BlindTechs.Net
   ` David Poehlman
     ` BlindTech of BlindTechs.Net
     ` hank smith
       ` David Poehlman
         ` tyler
           ` Gregory Nowak
             ` David Poehlman
     ` Garrett Klein
       ` BlindTech of BlindTechs.Net
         ` Gregory Nowak
           ` tyler
             ` David Poehlman
         ` tyler
       ` tyler
         ` Gregory Nowak
           ` Luke Yelavich
             ` Gregory Nowak
             ` Willem van der Walt
               ` tyler
                 ` Willem van der Walt
                 ` Travis Siegel
                   ` tyler
                   ` Willem van der Walt
           ` tyler
             ` tyler
               ` David Poehlman
                 ` tyler
 ` Ann K. Parsons
   ` Jim Kutsch
   ` BlindTech of BlindTechs.Net
   ` BlindTech of BlindTechs.Net
     ` tyler
       ` Travis Siegel
       ` BlindTech of BlindTechs.Net
         ` tyler
       ` Glenn at home
         ` tyler
   ` Glenn at home
     ` Gregory Nowak
       ` Glenn at home
 ` David Csercsics
   ` BlindTech of BlindTechs.Net
     ` tyler
 ` Gregory Nowak
   ` BlindTech of BlindTechs.Net
     ` tyler
       ` BlindTech of BlindTechs.Net
         ` tyler
       ` David Poehlman
         ` tyler
           ` David Poehlman
             ` Dan Murphy
               ` David Poehlman
               ` tyler
 ` David Csercsics

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='003001c62786$926f33a0$ae1dae48@dataplus4puarg' \
    --to=compgeek13@gmail.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).