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

Timestamp:

09/24/13 20:18:45 (11 years ago)

Author:

Vipulnayyar

Comment:

GSoC/2013/UnifiedAPIs

@@ -15 +15 @@
  *  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.
 
- *  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 & publicly available on a google drive document.
+ *  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.
 
- *  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.
+ *  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.
 
  *  For bsps that do not use the generic interrupt framework , rules to initialize & use it are written and present in the code repository. These rules specify how bsp specific code & the generic code works together & handles Interrupt Service Routines before, during and after an interrupt has occurred.
@@ -23 +23 @@
  *  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.
 
- *  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.
+ *  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.