Sebastian Kuzminsky wrote: > Eric H. Johnson wrote: >> 2> Adding the PIN file to the configuration folder >> >> I also think, at least for the configurations for the various Mesa boards, >> that it would make sense to include the pin files in with the configuration >> files (ini, hal, etc). Having to find it under >> src/hal/drivers/m5i20/...(current configurations - I presume a PIN file will >> be added to mesa-hostmot2) is a bit daunting both for the novice and when >> installing from the precompiled packages. > > I agree that the PIN files should be more accessible, but I'm not sure > the config directory is the place for them. The *firmware* determines > the pinout, and all the config can do is turn of some module instances > and let their pins revert to gpio. > > The .PIN files are provided by Mesa, one for each .BIT file. They're > currently in src/hal/drivers/mesa-hostmot2/firmware/*, and I dont think > they get installed with the debian package... Maybe the PIN files > should be installed in /usr/share/doc/emc2?
I'm about to run some errands, so I can't look into this r I'm about to go run some errands, so I can't look into this right now, but I had an idea (uh-oh ;-) PIN files are designed to be parsed by a computer - that means the format probably isn't too horrible, and should be consistent from one file to the next. I wonder how hard it would be to write a program that takes a PIN file as input and produces a man page as output. Make it part of the build process, and put the resulting man pages with all the rest. I might take a shot at that later this weekend, if I get some time. 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-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
