Ralph,
Thanks for the analysis:
>For an output, I can think of three reasonable choices that may be
>controlled without having to introduce another field in OUT:
>1. PINI = NO, DOL = don't care...
>2. PINI = YES, DOL is set (constant or link)...
>3. PINI = YES, DOL is not set...
Given the following...
>Some of the database configuration tools (i.e. CapFast) do not handle
>the new situation correctly. Users may have problems as they might not
>be able to _not_ set a DOL field...
...I feel that there _should_ be explicit control over whether output records
read the VxWorks variable at initialization time. Also, I think that
this is necessary in order to achieve backwards compatibility.
Also, Bob D suggested allowing the direct specification of an address. I
have permitted this (if the global variable doesn't exist, the name is
passed to strtoul(), so octal, decimal and hexadecimal are all
allowed). The result is that you can now use VxWorks global variable
device support for direct access to device registers if you so desire.
William
- Replies:
- Re: VxWorks global variable device support Ralph . Lange
- Navigate by Date:
- Prev:
cd2400 or z85230 serial driver ioctl options Porter, Rodney
- Next:
gdct313 Linux executable ? Brian McAllister
- 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: VxWorks global variable device support Ralph . Lange
- Next:
Re: VxWorks global variable device support Ralph . Lange
- 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
|