[EMAIL PROTECTED] wrote: > 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.
There are arguments both ways. I agree that separate GPIO is a bit klunky. But on the other hand, "compile another firmware image" immediately takes it out of the reach of 99% of users, no matter how "simple" the VHDL is. The Xilinx toolset is a gigabyte+ download, and is not trivial to figure out how to use it. You might as well be telling them "write another driver". In fact, they are more likely to have a C compiler and C programming skills than the Xilinx toolset and VHDL skills, and we have a makefile that handles the complexities of the build. 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
