Changes between Version 3 and Version 4 of GSoC/2013/UnifiedAPIs


Ignore:
Timestamp:
09/24/13 20:36:14 (11 years ago)
Author:
Vipulnayyar
Comment:

added details

Legend:

Unmodified
Added
Removed
Modified

  • GSoC/2013/UnifiedAPIs

    v3 v4  
    1515 *  Submitted patches to remove legacy code from RTEMS bsps which have been accepted & are currently a part of the official RTEMS repository. These patches were submitted for bsps : csb337, csb336, edb7312, gumstix, gba, rtl22xx, & pc386.
    1616
    17  *  Since more than about 100 bsps are a part of RTEMS, so guided instructions & rules for continuing this work has been compiled & is present in my [http://www.github.com/vipulnayyar/gsoc2013_rtems github] repository.
     17 *  Since more than about 100 bsps are a part of RTEMS, so guided instructions & rules for continuing this work has been compiled & is present in my github repository.
    1818
    1919 *  Studied the PIC interrupt model based on the comments written in irq-generic.h & my own observations. Information about PIC Interrupt Model API is added to the current RTEMS documentation.
    … …  
    2323 *  Based on my observations from model bsp lpc24xx , rules were compiled based on an ongoing discussion in the community on how bsp support files are included & compiled. These rules specify which set of files are a must to be used by a bsp & in which directory they all must lie. These rules will in future help in maintaining a unified pattern for BSP file organization.
    2424
    25  *  Since the above rules are very difficult to check manually for each bsp, so a [http://git.rtems.org/rtems-testing/tree/merge-helpers/check_submission bash script] was written merging the functionality of check_submission from rtems-testing. This script is supposed to be a final test for any bsp developer before his code is accepted into RTEMS, so as to check whether that the bsp code submitted follows this unified pattern of file organization & formatting or not.
     25 *  Since the above rules are very difficult to check manually for each bsp, so a bash script was written merging the functionality of check_submission from rtems-testing. This script is supposed to be a final test for any bsp developer before his code is accepted into RTEMS, so as to check whether that the bsp code submitted follows this unified pattern of file organization & formatting or not.
     26= Automated Rule Checking with check_submission =
     27
     28The main objective of the Unified API project is to determine a unified pattern of file usage, directory structure & the methods that each file uses.The checking of above rules is automated with the check_submission script.
     29
     30Based on the observations from lpc24xx, a list of critical files & methods that every BSP must include and use was compiled. These files & methods belonging to a component for a BSP can be deemed as critical or non-critical. The rule-checking is accomplished by the following way :