When I added support for the Mesa UART and BSPI drivers to the Hostmot2
code I could not think of a way to decide in the "loadrt" string how to
configure all the possible parameters and create HAL pins on-the-hoof. So,
at the moment the Hostmot2 driver simply offers a function that returns a
handle into the Hostmot2 data structure.

Then the Smart Serial devices arrived, and creating HAL pins to match
load-time parameters became necessary, as the SmartSerial boards declare
their pins from onboard rom.

Then the Absolute encoder driver came along and piggy-backed on the
smart-serial HAL pin creation, using a config string slightly like printf
to create the pins.

So, it seems that UART and BSPI could be a lot more friendly. But making
them more friendly might not be backwards-compatible.

I wonder if there is any way to know if anyone is using the current
interface? The 7i65 driver clearly does
http://linuxcnc.org/docs/html/man/man9/mesa_7i65.9.html but I think that
entire driver could be trivially replaced by a config string in the
proposed scheme.

That driver does show how one is required to interface with the BSPI driver
at the moment.

-- 
atp
If you can't fix it, you don't own it.
http://www.ifixit.com/Manifesto
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers

Reply via email to