[GSOC] Unified APIs Project

[Gedare Bloom]

Hi Matt,

Protected code (e.g. supervisor mode) is not in the current RTEMS direction.

-Gedare
On Jun 3, 2013 8:29 PM, "Matt Wette" <mwette at alumni.caltech.edu> wrote:

> Is there any interest in a "syscall" API that would allow future expansion
> into supporting "protected regions" of code?
>
> On Jun 3, 2013, at 10:15 AM, Vipul Nayyar wrote:
>
>
> Hello,
>
> Being accepted into GSOC with RTEMS is very exciting. This has been
> possible due to the constant support of Joel & Cynthia. A special thanks to
> Gedare for an in depth criticization of my proposal, which helped me
> improve it.
>
> I'll be working this summer on the 'Unified APIs' Project. The main task
> required for this project is to ensure that in areas where BSP support
> capabilities and APIs have evolved over the years, all the code there is
> moved to the latest version and any older implementations and
> inconsistencies across targets and BSPs are killed. The various components
> of this project are :
>
>    - Generalize the PIC interrupt support in sparc to support any other
>    simple vectored architecture.
>    - Spot discrepancies in file usage in various BSPs with PCI support.
>    - Review/Cleanup header files, which are publicly installed by
>    different BSPs , since this is the area having the most variation in coding
>    style.
>    - Unify naming styles, used for the same files in different BSPs, so
>    as to have consistent file names for the same supporting capability.
>
> My full length proposal can be found at
> http://www.google-melange.com/gsoc/proposal/review/google/gsoc2013/vipulnayyar/1 ,
> and
> https://docs.google.com/document/d/1oDp4E9_Wof4wBJaMJJIFoPqtu5fbTdsKwEcz-5qkazw/edit?usp=sharing
>
> As suggested by my mentor, I believe community input would act as an
> integral part of my work. So, I'm looking forward enthusiastically to
> working with you guys.
> Hoping for a great Summer !!!
>
> Regards
> Vipul Nayyar
>
> _______________________________________________
> rtems-users mailing list
> rtems-users at rtems.org
> http://www.rtems.org/mailman/listinfo/rtems-users
>
>
>
> _______________________________________________
> rtems-devel mailing list
> rtems-devel at rtems.org
> http://www.rtems.org/mailman/listinfo/rtems-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20130603/a8c4d5b3/attachment-0001.html>