Hi,
On 4 Mar, Mark Rivers wrote:
>
> Hi Nick,
>
> I believe this is the same problem I discovered on the DEC Alpha. The
> problems occurs on little-endian IEEE machines (such as Intel and DEC AXP
> running UNIX). The error happens when the source and destination address are
> the same, as they are in your case:
>> (*cac_dbr_cvrt[piiu->curMsg.m_type])(
>> piiu->pCurData,
>> piiu->pCurData,
>> FALSE,
>> piiu->curMsg.m_count);
>> # endif
>
> The problem is fixed in the latest CA release, such as R3.13.0.beta7.
Thanks a lot for your response.
I just looked at the APS, WWW server, and the most recent release is
R3.13.0beta6. I supose this won't do the trick....
I also wonder if there is any documention on channel access other than
the the... elementary "channel access reference", which only contains a
short description of the function calls. Is there a Channel Access
_Protocol_ reference? If so where I can look for it?
Thanks again,
Nick Patavalis.
--
------------------------------------------------
Nick Patavalis Snail-mail:
([email protected]) Thironos 11,
University of Athens, 161 21 Athens,
Computer Science Dept. Hellas.
------------------------------------------------
- Navigate by Date:
- Prev:
Problems with Alh & Channel Access (R3.13.0b4). Nick Patavalis
- Next:
MVME177 and vxWorks Jim B. Kowalkowski
- 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: Problems with Alh & Channel Access (R3.13.0b4). Nick Patavalis
- Next:
MVME177 and vxWorks Jim B. Kowalkowski
- 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
|