Documentations

[Fered]

Thanks a lot.
I prefer using of a released version. I want to evaluate some idea in 
scheduling through a stable release.


Gedare Bloom wrote:
> I don't think we have such a thing for the "kernel" code, and the
> developer base probably is not large enough to warrant the effort to
> make one.
> 
> A lot of that knowledge is in developer heads. Some of it leaches out
> to documentation. Some of it can be gleaned from the doxygen [1].
> Otherwise you can ask specific questions here and we will try to give
> specific answers. :)
> 
> I can't think of anywhere else you could find useful documentation.
> The code base is not big so unlike Linux you can reasonably go and
> start figuring it out yourself with a little guidance.
> 
> I saw your email in the other list and if you are interested in kernel
> hacking / BSP development then I would suggest you use the current
> development head (which we are calling 4.11). While it is possible to
> add BSPs and backport BSPs to prior releases of RTEMS they are much
> harder to get accepted for inclusion and less likely to be maintained.
> Your efforts will be much more rewarded by using the development head.
> 
> -Gedare
> 
> [1] http://www.rtems.org/onlinedocs/doxygen/cpukit/html/
> 
> On Sun, Apr 29, 2012 at 11:57 PM, Fered <a_Fered at yahoo.com> wrote:
> > And I think I should shovel the code! :D
> > 
> > I'm looking for a document same as "Linux Kernel Development" book, in
> > linux. (It's just an example that you understand what I intend)
> > 
> > Thanks.
> > 
> >  Joel Sherrill wrote:
> >> And there is always the source code. :)
> >> 
> >> Gedare Bloom <gedare at rtems.org> wrote:
> >> >You can find them under doc/ in RTEMS, or built from the Git head at
> >> >http://rtems.org/onlinedocs/doc-current/share/rtems/html/
> >> >
> >> >On Sun, Apr 29, 2012 at 7:47 AM, Fered <a_Fered at yahoo.com> wrote:
> >> >> Hi;
> >> >> 
> >> >> Is there any document, defines architecture of RTEMS and
> >> >> implementation of some functionalities such as scheduling and
> >> >> interrupt handleing.
> >> >> 
> >> >> Thanks.
> >> >> _______________________________________________
> >> >> rtems-devel mailing list
> >> >> rtems-devel at rtems.org
> >> >> http://www.rtems.org/mailman/listinfo/rtems-devel
> >> >
> >> >_______________________________________________
> >> >rtems-devel mailing list
> >> >rtems-devel at rtems.org
> >> >http://www.rtems.org/mailman/listinfo/rtems-devel