How valuable is it for hostmot2 to have stand-alone gpio access (for the PCI cards only)? It seems like sort of a klunky interface.
The differentiating feature of hostmot2 is the flexible firmware, which solves this problem very neatly. So I still think the current interface is the right one, and the solution to the problem JMK described is to compile another firmware image. -- Sebastian Kuzminsky never be discouraged just let your nerdy flourish -----Original Message----- From: "Peter C. Wallace" <[EMAIL PROTECTED]> Subj: Re: [Emc-users] Stepper configuration Date: Sat 2008 Aug 9 11:53 Size: 1K To: "Enhanced Machine Controller (EMC)" <emc-users@lists.sourceforge.net> > > 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) ------------------------------------------------------------------------- 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
