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 2025 | 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 2025 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: VME Bus Error handling on MVME3100 and MVME6100 boards |
From: | Andrew Johnson <[email protected]> |
To: | Kate Feng <[email protected]> |
Cc: | [email protected] |
Date: | Mon, 28 Aug 2006 09:18:25 -0500 |
Andrew Johnson wrote about mvme6100:
The only sure-fire way around this problem is to check the Tempe chip's VMEbus Exception Attributes Register after every write operation and every read that returns an all-1s bit pattern
This can be implemented at the level of the Tsi148 driver instead of the EPICS driver, right ?
- clearly not something conducive to good I/O performance, and not compatible with any existing EPICS drivers.
At least, only the VME devices implemented with the 2eSST protocols are eight times faster than the regular one, which somehow compensate the overhead. The only possible performance gain over the Universe on the VME backplane lies at the MBLT via the DMAs of the tempo chip using the 2eSST protocols, which will be confirmed by Timo.
- Andrew -- There is considerable overlap between the intelligence of the smartest bears and the dumbest tourists. -- Yosemite National Park Ranger