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 | 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 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: VxWorks 6.9 |
From: | Stefen Paul <[email protected]> |
To: | EPICS Tech Talk <[email protected]> |
Date: | Fri, 15 Jan 2016 11:29:48 +0530 |
Hi Andrew,I am referring to BSP for MVME-5500 board.Thanks,Stefen.On Wed, Jan 13, 2016 at 9:36 PM, Andrew Johnson <[email protected]> wrote:Hi Stefen,
On 01/13/2016 06:41 AM, Stefen Paul wrote:
> Is it true that VxWorks 6.9 BSP can't make use of VME64 or VME64x
> addressing capabilities even if the SBC on which it is running has this
> feature ?
>
> Because in config.h I can see only A16, A24 and A32 address space details.
That depends on the BSP (you didn't tell us which board/BSP you're
using), but you could be right. Over the 15 years I've been maintaining
BSPs for the APS I have added many features to our BSPs which did not
come with the originals from Wind River. I have made several of those
changes available to the EPICS community through tech-talk, which you
can find by searching the archives, but please note that I can't publish
the full BSP code because the original BSPs are proprietary software,
not Open Source.
If you explain what you're looking for in a bit more detail there are
several people on this list who might be able to help.
- Andrew
--
There are only two hard problems in distributed systems:
2. Exactly-once delivery
1. Guaranteed order of messages
2. Exactly-once delivery
-- Mathias Verraes