Aloha
About 2 years ago I was debugging a problem that we suspected was in
drvAscii. I decided to debug this problem on UNIX so I could use the
UNIX compliation tools and debuggers. To this end I created 'glue'
code so as to be able to run drvSerial and drvAscii on UNIX (the intent
was to leave those drivers untouched, as much as possible). This all
worked fine.
The 'glue' code is mainly system call translations (semaphores,
spawns, ...). This code should be subsumed into the drivers.
Since that time I have successfully driven an instrument rotator, whose
motor controller has a serial interface, using the 'glued' drvSerial and
drvAscii, along with an updated tnet driver.
In most cases, the EPICS databases using drvAscii and developed for Vxworks,
will run on the r3.14 UNIX platform by simply changing the port designations
(which should be a macro substitution), with the 'glue' drivers.
I will try and update the drivers to eliminate the 'glue' sometime soon.
cheers,
A Honey
- Navigate by Date:
- Prev:
Re: 3.14 on Linux Andrew Johnson
- Next:
Re: shared libraries build bug Janet Anderson
- Index:
1994
1995
1996
1997
1998
1999
2000
<2001>
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: 3.14 on Linux Matthieu Bec
- Next:
mvme162PA-344SE and mvme162-532A Dale L. Brewe
- Index:
1994
1995
1996
1997
1998
1999
2000
<2001>
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|