2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 <2021> 2022 2023 2024 | Index | 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: Announcement: Legacy libnetworking will be removed from RTEMS and will be placed in a separate repository |
From: | "Johnson, Andrew N. via Core-talk" <core-talk at aps.anl.gov> |
To: | Chris Johns <chrisj at rtems.org> |
Cc: | Core talk <core-talk at aps.anl.gov>, Joel Sherrill <joel at rtems.org>, "rtems-devel at rtems.org" <devel at rtems.org> |
Date: | Fri, 5 Mar 2021 00:29:51 +0000 |
On Mar 4, 2021, at 5:36 PM, Chris Johns <chrisj at rtems.org> wrote:
The rtems5 branch of EPICS Base which may be nearing merge soon currently contains configuration files for these RTEMS BSPs:
Now the -qemu variants are our internal names so you can ignore them. I don’t believe anyone is using the at91rm9200ek, gen68360, mcp750, mvme167 or psim BSPs so similarly I would ignore them (I’ll try to get those files dropped from EPICS someday). There
is probably no need for the separate mvme5500 BSP since that board can run the beatnik instead, but there might be one or two sites using it. That leaves this list for future use, to a first approximation:
Note that this branch only builds the pc386 on RTEMS-4 and the pc686 on RTEMS-5 and above, so for your purposes you can drop the separate pc386 as well. Several of the above are only just being added so wouldn’t be used with RTEMS-4, but I’m pretty sure
we have users currently running RTEMS-4 on the PowerPC BSPs and the uC5282.
I would have expected a Canadian cross to have
--host be the same as the build host, not as the final target ("please build me a compiler that can run on that host and produce binaries for that target”). That’s why they seem weird. Just wondering.
Thanks,
- Andrew
--
Complexity comes for free, simplicity you have to work for.
|