> > Not true. Threads are interruptable, based on priority. Fast threads > are higher priority than slow ones, under the assumption that the code > in a 1mS thread might take 200uS to execute, and a 25uS thread might > need to interrupt it and run a few uS worth of code several times.
Sounds like the simplest compromise would be to separate the GPIO update call from the others, so GPIO could be accessed via a different thread, with the proviso the EPP based cards cannot use multiple threads (though this may be fixable with some magic save/restore context foo) >> > > Regards, > > John Kasunich > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Emc-users mailing list > Emc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-users > Peter Wallace Mesa Electronics (\__/) (='.'=) This is Bunny. Copy and paste bunny into your (")_(") signature to help him gain world domination. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
