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. 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). on Sunday 06/16/2002 Igor Gueths(igueths at attbi.com) wrote > Hi all. Does anyone know why Speakup doesn't use the standard conventions when designing kernel modules? In other words, why are the drivers not modularized? Because my plan at least for the dectalk driver was to write the standard module code, and then dump the rest of the driver-specific code into the new re-written version. I am doing this for two reasons. 1. I want to keep the changes as error free as possible. 2. I don't want to have problems after writing new code. And I think most of the driver is fine the way it is. I have other reasons for modularizing the driver, including a project I am currently working on that requires this. > > > _______________________________________________ > Speakup mailing list > Speakup at braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup -- John Covici covici at ccs.covici.com
