Changes between Version 164 and Version 165 of GSoC/2015

Jun 23, 2015, 10:48:49 PM (4 years ago)
André Marques



  • GSoC/2015

    v164 v165  
    5555||Anand Krishnan Prakash||anandkp92||[ wiki]||[ Github]||[ Blog]||[ Calendar]
    5656||Saurabh Gadia||sgworks||[ Wiki]||[ Rtems_Github] [ JPF]||[ Blog]|| [ Calendar]
    57 ||Andre Marques||asuol||TBD||[ Github]|| [ Blog] || [ Calendar]
     57||Andre Marques||asuol||TBD||[ Github]|| [ Blog] || [ Calendar]
    5858||Jarielle Catbagan||jrcatbagan||[ Wiki]|| [ Github] || [ Blog] || [ Calendar]
    5959||Ragunath || ragunath || [ wiki] || [ Github] || [ Blog] || [ calendar]
    8686* June 16: I have completely separated the rpi code from the rtems gpio API, and the features mentioned in the last week's blog post are almost all implemented (just need to take care of some details, such as locking the data structure that keeps the GPIO status. Currently only the interrupt management is being protected by a mutex and vector enable/disable). At this time the core of the GPIO API can leave the rpi bsp to somewhere accessible by all BSPs, and may be used by others, so today and in the next very few days I will be finishing/cleaning up/adding documentation to the code, as well as updating the blog/wiki with a developers/user manual so it can be reviewed. While it is being reviewed I can then start to work on the I2C porting to the new framework.
     88* June 23: This week I have posted patches for review regarding the RTEMS GPIO API and its rpi implementation. I have also been gathering more references/documentation to help in the I2C porting (by what I have seen only the xilinx bsp currently uses the new I2C framework). At this time I am correcting the issues/suggestions pointed on the GPIO API, and intend to send a new version of the patches tomorrow/thursday. I should have documentation (developer/user manual and/or blog/wiki page) posted this week. The I2C work can start right after, and at this point I am not expecting much trouble, but if it does I will post any problem on the ml regarding the new framework.
    8890== Anand Krishnan Prakash ==