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: Porting EPICS to a new OS |
From: | Stephen Beckwith <[email protected]> |
To: | Eric Norum <[email protected]> |
Cc: | EPICS mailing list <[email protected]> |
Date: | Fri, 6 Jun 2014 13:03:09 -0400 |
At a quick estimate, and assuming that POSIX-compiiant really means what you and the EPICS developers think it means, I’d expect that porting EPICS base might just be a ‘1’ on the scale you’ve shown. Are you planning on native or cross development?Of course I wouldn’t be surprised if Mr. Murphy’s Law requires a little of ‘3’, too.The real work comes when you want to provide driver support — especially if you want to get at local hardware I/O space and even more so if you need the ability to deal with hardware interrupts. If all you want is ASYN-style serial and network ports things should be pretty simple.On Jun 6, 2014, at 9:01 AM, Emmanuel Mayssat <[email protected]> wrote:
Hello,I am interested in porting EPICS to a new OS, namely QNX.QNX is a real-time OS with a microkernel.It is POSIX compliant.How much work will that take?or rather what needs to be done?0/ Because QNX is POSIX compliant, epics-base compiles out of the box1/ It compiles provided that I create/change files in the $(TOP)/configure directory2/ It compile but I have to change the master Makefile of epics-base3/ I have to change the epics-base code itself4/ It compiles, but requires a combination of all the above5/ ... something even more time consuming ...6/ It is impossible.So on the scale of 0 to 6, how big of a job is that?Regards,--Emmanuel--
Eric Norum
[email protected]