Changes between Version 51 and Version 52 of GSoC/2016

May 26, 2016, 9:38:31 PM (4 years ago)

Student updates


  • GSoC/2016

    v51 v52  
    4545||NAME || nick on #rtems || Link to Project Wiki page  || Link to project's public Github repository || Link to your development blog || Link to Calendar with Schedule
    4646||Sambeet Panigrahi||_sambeet||[ Wiki]||[ Github]||[ Blog]||[|month-3+23713+23748+23713 Calendar]
    47 ||Darshit Shah || darnir || [ Wiki] || [ GitHub] || TBA || [ Calendar]
     47||Darshit Shah || darnir || [ Wiki] || [ GitHub] || [ Blog] || [ Calendar]
    4848||Mudit Jain || mudit1729 || [ Wiki] || [ Github] ||[ Blog]|| [ Calendar]
    4949|| Punit Vara || punitvara || [ Wiki] || [ GitHub] || [ Blog] || TBA
    7878* TBD
     80== Darshit Shah ==
     81* May 25: I've been looking into the Scheduling Simulator and trying to get it to compile. However that has been a large task with a few breakages that I haven't been able to fix yet. Based on my last conversation with sebhub, it is okay to push this task to a little later since we don't need schedsim till the end of the project anyways. I've also been looking into the existing scheduler implementations and working on a draft for how I will implement the new scheduler as well. I have most of the specifics charted out now. Will start implementing the iterative MVM algorithm in the coming week.
    8083== Deval Shah ==
    8184* May 25: My first task is to add USB root hub support. For that, I need USB DWC OTG drivers and hardware specific drivers (for bcm283x) in the right place. USB DWC OTG drivers are already there in the codebase. To continue with Yurii's last year's work, I cherry picked his commits for USB roothub drivers and merged it to the current version of rtems-libbsd. Default testsuits which are related to networking are having compilation/linking errors. Later I realised that the driver (bcm283x) itself is not compiling. So I will now read the documentation regarding adding drivers in rtems-libbsd. That should help me to verify the code or if required write that from scratch. I should be able to add the hardware specific driver before the next status update.