lessons learned designing an open source umpc
play

Lessons Learned Designing an Open Source UMPC Ben Goska and Tim - PowerPoint PPT Presentation

Outline What is the OSWALD? Development team Lessons Learned Designing an Open Source UMPC Ben Goska and Tim Harder Oregon State University September 25, 2009 Ben Goska and Tim Harder Oregon State University Lessons Learned Designing an


  1. Outline What is the OSWALD? Development team Lessons Learned Designing an Open Source UMPC Ben Goska and Tim Harder Oregon State University September 25, 2009 Ben Goska and Tim Harder Oregon State University Lessons Learned Designing an Open Source UMPC

  2. Outline What is the OSWALD? Development team What is the OSWALD? Project history Design considerations Hardware Firmware/Bootloaders Kernel Software Educational usage Development team Working with a small team of students Moving the project forward Ben Goska and Tim Harder Oregon State University Lessons Learned Designing an Open Source UMPC

  3. Project history Design considerations Outline Hardware What is the OSWALD? Firmware/Bootloaders Development team Kernel Software Educational usage Noteworthy events in the project’s short history ◮ Concepts/ideas leading to the project ◮ OSU Platforms for Learning ◮ Paired with Beaversource ◮ Combining social networking and coding — Elgg + Trac ◮ Less intimidating introduction to open source communities ◮ Timeline ◮ Project started in June 2008 ◮ First prototypes release in December 2008 ◮ First deployment in April 2009 ◮ Large-scale deployment in October 2009 Ben Goska and Tim Harder Oregon State University Lessons Learned Designing an Open Source UMPC

  4. Project history Design considerations Outline Hardware What is the OSWALD? Firmware/Bootloaders Development team Kernel Software Educational usage Design considerations ◮ Price ◮ Flexibility ◮ Manufacturability ◮ Openness Ben Goska and Tim Harder Oregon State University Lessons Learned Designing an Open Source UMPC

  5. Project history Design considerations Outline Hardware What is the OSWALD? Firmware/Bootloaders Development team Kernel Software Educational usage Hardware specifications ◮ OMAP 3530 ◮ IEEE 802.15.4 wireless with IP over 802.15.4 support ◮ 128 MB DDR-SDRAM (266 ◮ Touchpad MHz) ◮ 3 axis accelerometer ◮ 256 MB NAND ◮ 5-way rocker switch ◮ 3.5” QVGA (320x240) 24 bit ◮ 6 general purpose buttons color LCD ◮ Speaker ◮ Resistive touchscreen ◮ Microphone ◮ DVI out (up to 1024x768) ◮ Built-in 1300mAh Polymer ◮ TI TLV320AIC33 stereo audio codec Li-ion battery Ben Goska and Tim Harder Oregon State University Lessons Learned Designing an Open Source UMPC

  6. Project history Design considerations Outline Hardware What is the OSWALD? Firmware/Bootloaders Development team Kernel Software Educational usage Manufacturing process Ben Goska and Tim Harder Oregon State University Lessons Learned Designing an Open Source UMPC

  7. Project history Design considerations Outline Hardware What is the OSWALD? Firmware/Bootloaders Development team Kernel Software Educational usage Low-level software ◮ atmega48 ◮ Cypress ◮ cc2431 802.15.4 wireless system ◮ Das U-Boot ◮ Flashing ◮ Display options ◮ Boot selection Ben Goska and Tim Harder Oregon State University Lessons Learned Designing an Open Source UMPC

  8. Project history Design considerations Outline Hardware What is the OSWALD? Firmware/Bootloaders Development team Kernel Software Educational usage Merging our efforts with the linux-omap branch ◮ 2.6.31-omap1 + OSWALD patches ◮ Hacking around hardware problems ◮ Adding functionality – battery monitor ◮ Developing new drivers – 802.15.4 wireless Ben Goska and Tim Harder Oregon State University Lessons Learned Designing an Open Source UMPC

  9. Project history Design considerations Outline Hardware What is the OSWALD? Firmware/Bootloaders Development team Kernel Software Educational usage Distro creation with OpenEmbedded ◮ Radix ◮ Using the OE development branch ◮ Many extra packages and version bumps available through package repos Ben Goska and Tim Harder Oregon State University Lessons Learned Designing an Open Source UMPC

  10. Project history Design considerations Outline Hardware What is the OSWALD? Firmware/Bootloaders Development team Kernel Software Educational usage A hands-on approach to computer science Classes ◮ Last spring 162 ◮ Fall 161 ◮ Future Non-curricular activities ◮ OSU Robotics club ◮ Games Ben Goska and Tim Harder Oregon State University Lessons Learned Designing an Open Source UMPC

  11. Outline Working with a small team of students What is the OSWALD? Moving the project forward Development team Extremely small development team ◮ Pros ◮ Cons Ben Goska and Tim Harder Oregon State University Lessons Learned Designing an Open Source UMPC

  12. Outline Working with a small team of students What is the OSWALD? Moving the project forward Development team Building a community ◮ Finding more developers ◮ Inspiring students to contribute ◮ Operating on a shoestring budget Ben Goska and Tim Harder Oregon State University Lessons Learned Designing an Open Source UMPC

  13. Outline What is the OSWALD? Development team Small quantities available to the open source community in November Questions? Project page: http://beaversource.oregonstate.edu/projects/cspfl Git repos: https://code.oregonstate.edu/git Ben Goska and Tim Harder Oregon State University Lessons Learned Designing an Open Source UMPC

Download Presentation
Download Policy: The content available on the website is offered to you 'AS IS' for your personal information and use only. It cannot be commercialized, licensed, or distributed on other websites without prior consent from the author. To download a presentation, simply click this link. If you encounter any difficulties during the download process, it's possible that the publisher has removed the file from their server.

Recommend


More recommend