From: Alex J. <ale...@ro...> - 2014-01-15 14:32:15
|
On that note, could you add this patch? http://www.juve.ro/~juve/bbb/0002-bbb_parport-sample-config.patch That's a sample config for my bbb_parport board (default 4 axes pinout on the DB25 connector). I'll send you a config for 6 axes too, in a little while. Regards, Alex ----- Original Message ----- From: "Charles Steinkuehler" <ch...@st...> To: "EMC developers" <emc...@li...> Sent: Wednesday, January 15, 2014 1:34 PM Subject: [Emc-developers] Driver Name and Configuration Directories I am reworking the PRU driver code for the BeagleBone, and have the change to rename some files and restructure the example configurations. The PRU driver code currently goes by the name of "hal_pru_generic", which seems both long and a bit redundant. I am thinking of dropping the hal_ and changing to one of the following: pru_generic pru_motion prumot As for the BeagleBone example configurations, David reworked those a while back, but I'm not sure the structure he came up with meshes well with the cleanup effort for the existing configurations. I volunteer to re-arrange the ARM configuration files if there is a desired directory structure target. The various permutations for configuration files on the ARM include: Machine type: 3D printer (Cartesian) 3D printer (lineardeltakins) CNC (a.k.a. ShapeOko) HAL Driver: Everything uses hal_pru_generic at the moment, but I have hopes for an FPGA driver for the 'Bone someday Pinout / Driver board: BeBoPr BeBoPr+ (a.k.a. BeBoPr-Bridge) K9 (maybe pull this one?) Replicape (not supported yet) Others to come, many of which may map to one of the above All advice and comments appreciated! -- Charles Steinkuehler ch...@st... |