Re: speakup question

['Georgina' <gena@gena-j.net>]

Hi

As I asked.  Have you asked Kirk your question?  Maybe such a question
is a little advanced for the scope of a user list.  But you never know
there are some very tallented people on the list.

Gena



Blindness Advocacy and Self Help Online www.bashonline.org

>Hi. This is true. I just odn't have my box here right now so I can look =
>at the sourcecode. However, what I was looking for was exactly how =
>Speakup initializes itself during the boot process. For example, how is =
>Speakup able to start first in the boot sequence? Are the routines for =
>rs232 communication for external synths defined in speakup.h?=20
>----- Original Message -----=20
>From: 'Georgina' <gena@gena-j.net>
>To: <speakup@braille.uwo.ca>
>Sent: Monday, June 17, 2002 6:19 AM
>Subject: Re: speakup question=20
>
>
>> Hi
>>=20
>> I don't understand, you can view the source and for those synthesisers
>> that are not supported, perhaps you could get the specs and write
>> drivers yourself.
>>=20
>> Have you tried to ask Kirk specific questions?
>>=20
>> Gena
>>=20
>>=20
>>=20
>> Blindness Advocacy and Self Help Online www.bashonline.org
>>=20
>> >Hi John. This is all correct, however as far as I know the =
>synthesizer =3D
>> >driver is what's up before anything else. It would be nice to have =
>=3D
>> >documentation on exactly what Speakup does at boot time i.e., =3D
>> >synthesizer driver initialization, etc. This would help me a lot in =
>my =3D
>> >development, however such docs don't seem to be available. Looks like =
>=3D
>> >I'll have to dig up everything by hand.=3D20
>> >----- Original Message -----=3D20
>> >From: John covici <covici@ccs.covici.com>
>> >To: <speakup@braille.uwo.ca>
>> >Sent: Sunday, June 16, 2002 9:10 PM
>> >Subject: speakup question
>> >
>> >
>> >> The problem is that speakup needs to be alive before modules, =
>before
>> >> a file system and before much of anything except the console is
>> >> around.
>> >>=3D20
>> >> I understand Kirk is working on a scheme to allow modules, but if =
>its
>> >> a Dectalk pc, it won't talk at boot, but will have to wait till a
>> >> file is downloaded into it (at least that is my understanding, I
>> >> don't have one of those).
>> >>=3D20
>> >> on Sunday 06/16/2002 Igor Gueths(igueths@attbi.com) wrote
>> >>  > Hi all. Does anyone know why Speakup doesn't use the standard =
>=3D
>> >conventions when designing kernel modules? In other words, why are =
>the =3D
>> >drivers not modularized? Because my plan at least for the dectalk =
>driver =3D
>> >was to write the standard module code, and then dump the rest of the =
>=3D
>> >driver-specific code into the new re-written version. I am doing this =
>=3D
>> >for two reasons. 1. I want to keep the changes as error free as =3D
>> >possible. 2. I don't want to have problems after writing new code. =
>And I =3D
>> >think most of the driver is fine the way it is. I have other reasons =
>for =3D
>> >modularizing the driver, including a project I am currently working =
>on =3D
>> >that requires this.=3D20
>> >>  >=3D20
>> >>  >=3D20
>> >>  > _______________________________________________
>> >>  > Speakup mailing list
>> >>  > Speakup@braille.uwo.ca
>> >>  > http://speech.braille.uwo.ca/mailman/listinfo/speakup
>> >>=3D20
>> >> --=3D20
>> >>          John Covici
>> >>          covici@ccs.covici.com
>> >>=3D20
>> >> _______________________________________________
>> >> Speakup mailing list
>> >> Speakup@braille.uwo.ca
>> >> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>> >>=3D20
>> >
>> >
>> >_______________________________________________
>> >Speakup mailing list
>> >Speakup@braille.uwo.ca
>> >http://speech.braille.uwo.ca/mailman/listinfo/speakup
>>=20
>> _______________________________________________
>> Speakup mailing list
>> Speakup@braille.uwo.ca
>> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
>
>_______________________________________________
>Speakup mailing list
>Speakup@braille.uwo.ca
>http://speech.braille.uwo.ca/mailman/listinfo/speakup