[GSoC 2020]: Doubts in building RSB Recipe for EPICS for multiple architectures

Chris Johns chrisj at rtems.org
Mon Jul 27 00:27:28 UTC 2020


On 27/7/20 10:22 am, Joel Sherrill wrote:
> On Sun, Jul 26, 2020, 7:06 PM Chris Johns <chrisj at rtems.org
> <mailto:chrisj at rtems.org>> wrote:
> 
>     On 27/7/20 9:46 am, Joel Sherrill wrote:
>     > On Fri, Jul 24, 2020 at 8:51 AM Mritunjay Sharma
>     <mritunjaysharma394 at gmail.com <mailto:mritunjaysharma394 at gmail.com>
>     > <mailto:mritunjaysharma394 at gmail.com
>     <mailto:mritunjaysharma394 at gmail.com>>> wrote:
>     >
>     >     Hello all, 
>     >
>     >     To update you all, I have sent the first version of PATCHES that
>     >     implement an RSB recipe for EPICS7 building with RTEMS5 for pc-386. 
>     >
>     >     While the build was successful for pc-386, I have doubts and need 
>     >     suggestions on how to make it work across different BSP targets.
>     >     I will request Chris to show me the path and if possible then also review
>     >     the patches. 
>     >
>     >
>     > I didn't see anything in the patches that look to be pc specific but admit I
>     > could have missed something.
> 
>     There is a patch to EPICS for the PC BSP that I cannot find posted online
>     anywhere.
> 
>     > I would try another couple of BSPs known to work with EPICS
>     > using the same network stack you used for the PC. Options include:
>     >
>     > + powerpc and beatnik or a motorola_powerpc variant
>     > + arm zynq qemu
>     > + m68k uc5282
>     >
>     > Which network stack did you build against? 
>     >
> 
>     It currently is the legacy stack. Heinz has changes pending for RTEMS 5.
> 
> Then it should be repeatable for multiple powerpc and m68k bsps. That works be
> the next step past clean up and documentation to me.
> 
> Then focus on some libbsd bsps.

I am not sure yet as I have not seen what the changes are. We should be
encouraging libbsd as the primary stack for RTEMS 5 and not the legacy stack. I
would like to remove the legacy stack from the main source tree.

Chris


More information about the devel mailing list