>Andrew Johnson wrote:
>
>> IMHO the new formats should not be hard-coded anywhere other than the
>> drivers/device support which use them; the "link_type" in the database
>> "device" definition should be something else which is definable in an
>> ascii file (and convertable into a VME_IO.h file for example, which can be
>> #included by the device/driver). This way anyone could add a new address
>> type without needing to rebuild base, but you should still be able to
>> retain backwards compatibility for existing device/driver support.
>
>I just read this more carefully. I think I now see what you are saying.
>
>Just like 3.13 has ascii definitions for menus and record types
>let it have an ascii definition for a link type.
Add support for these things to GDCT and you will be caught back up to the
hardware-config subsystem of RX ;-)
--John Winans
- Navigate by Date:
- Prev:
Re: mv162LC problem with floating point libraries in 5.1.1 Johnny Tang
- Next:
Re: rec/devSup advise needed Ric Claus
- 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: rec/devSup advise needed Tim Mooney
- Next:
tclCa package (was et_wish) Claude Saunders
- 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
|