Back
[15:42:44] <skunkworks846> skunkworks846 is now known as skunkworks_
[16:40:02] <alex_joni> alex_joni is now known as hammerschlag
[16:40:13] <skunkworks_> skunkworks_ is now known as alex_joni
[16:40:26] <alex_joni> alex_joni is now known as skunkworks_
[16:41:06] <hammerschlag> hammerschlag is now known as alex_joni
[17:51:04] <CIA-21> EMC: 03seb 07TRUNK * 10emc2/src/hal/drivers/ (m7i43_hm2.comp m7i43_hm2.h Submakefile): Version 0.1 of m7i43_hm2, a driver for the Mesa 7i43 with HostMot2 firmware.
[17:51:05] <CIA-21> EMC: 03seb 07TRUNK * 10emc2/src/hal/drivers/mesa7i43-firmware/gpio/ (6 files): Version 0.1 of m7i43_hm2, a driver for the Mesa 7i43 with HostMot2 firmware.
[17:51:06] <CIA-21> EMC: 03seb 07TRUNK * 10emc2/src/hal/drivers/mesa7i43-firmware/source/ (6 files): Version 0.1 of m7i43_hm2, a driver for the Mesa 7i43 with HostMot2 firmware.
[17:51:06] <CIA-21> EMC: 03seb 07TRUNK * 10emc2/src/hal/drivers/mesa7i43-firmware/hostmot2/ (6 files): Version 0.1 of m7i43_hm2, a driver for the Mesa 7i43 with HostMot2 firmware.
[17:51:09] <CIA-21> EMC: 03seb 07TRUNK * 10emc2/src/hal/drivers/mesa7i43-firmware/hostmot2/src/ (22 files): Version 0.1 of m7i43_hm2, a driver for the Mesa 7i43 with HostMot2 firmware.
[17:52:01] <cradek> woooo
[17:52:49] <jepler> neat-o!
[17:53:12] <seb_kuzminsky> woot! :-)
[17:53:43] <seb_kuzminsky> i just sent out an email announcement to the emc-developers and emc-users lists with some more details
[17:57:23] <seb_kuzminsky> got to go, back in a couple of hours
[20:33:48] <alex_joni> seb_kuzminsky: cool
[20:34:57] <seb_kuzminsky> thanks!
[20:46:00] <seb_kuzminsky> i wasn't sure how to represent the hm2 gpios - they can be switched between digital input and output at runtime....
[20:46:25] <seb_kuzminsky> i sort of squished the digital input and digital output canonical device interfaces together, and added an "is_output" parameter
[20:46:55] <seb_kuzminsky> the .in and .out pins are both always there, but which one is useful depends on the .is_output param
[20:47:28] <seb_kuzminsky> maybe it'd be better to just export the pin that's available based on .is_output, and un-export the other one?
[20:48:20] <alex_joni> hmm.. I think having both, one unused might cause confusion
[20:48:39] <alex_joni> I don't remember if you can un-export a HAL pin, but if you can.. I'd go for that
[20:49:12] <alex_joni> although I don't see many people changing things during runtime
[20:49:42] <seb_kuzminsky> nope, according to hal.h, there is no way to remove a pin other than hal_exit()...
[20:50:14] <seb_kuzminsky> agreed, for any one user or configuration, the pin directions will be set at the beginning and then not changed.
[20:52:38] <seb_kuzminsky> i thought of having just one pin and calling it ".value" or something, but that deviates farther from the CDI
[20:53:09] <seb_kuzminsky> or forcing the user to specify the in/out settings for all gpios at load-time
[20:53:21] <seb_kuzminsky> there's a million ways to do it...
[20:54:13] <alex_joni> seb_kuzminsky: yeah, but I see no real advantage for emc users
[20:54:33] <alex_joni> it might be usefull for HAL-only users (but I don't know of any atm)
[20:56:47] <SWPadnos___> SWPadnos___ is now known as SWPadnos