Re: New RTOS cross with linux+RT_PREEMPT patch

["Ernest L. Williams Jr." <ernesto@slac.stanford.edu>]

On 05/15/2012 01:24 PM, Andrew Johnson wrote:
> Hi Ernest,
>
> On 2012-05-15 Ernest L. Williams Jr. wrote:
> > We are not using the product from WRS.
> > So, we will propose a different name.
> > How about  "linuxRT-x86"  and "linuxRT-ppcP2020"  ?
> Linux/RT was a /different/ commercial real-time Linux distribution from
> TimeSys, although they may be dead now for all I know.  The name Linux-rt is
> also used for the generic real-time linux community that maintain the
> CONFIG_PREEMPT_RT patches for the kernel.org kernel.
This is why I removed the delimiter between linux and RT.



> > > Will these targets be using the standard Linux OS_CLASS or do they
> > > require their own versions of the OS-dependent files under
> > > src/libCom/osi/os?
> > We are using the standard Linux "OS_CLASS"
> If you're just using the standard code from Base without changing any of it
> then all you really need is to create local (SLAC-specific) aliases for the
> linux-x86 and linux-ppc targets.  In that case you can call them whatever you
> like since they don't have to make their way into the official Base release.
I am hoping that the toolchain Till is developing will not be SLAC 
specific but usable
by the EPICS community.
So, I do want to choose a unique name that many sites can identify with.
"linuxRT-x86"  and  "linuxRT-ppc"


> I would recommend that you try to avoid CPU-specific target names like
> linuxRT-ppcP2020 unless you really need them.  It is usually sufficient to
> configure gcc to build for the generic CPU family, unless you're writing
> highly tuned CPU-specific kernel-level code.  You won't want to have to
> compile everything for multiple CPU-specific architectures if all your CPUs
> can run generic linuxRT-ppc binaries instead.
Sounds good.
Will do.

> - Andrew