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

▶

Apr 06, 2023 683 likes •837 views

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

SLIDE 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

SLIDE 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

SLIDE 3

Outline What is the OSWALD? Development team Project history Design considerations Hardware Firmware/Bootloaders 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

SLIDE 4

Outline What is the OSWALD? Development team Project history Design considerations Hardware Firmware/Bootloaders 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

SLIDE 5

Outline What is the OSWALD? Development team Project history Design considerations Hardware Firmware/Bootloaders Kernel Software Educational usage

Hardware specifications

◮ OMAP 3530 ◮ 128 MB DDR-SDRAM (266

MHz)

◮ 256 MB NAND ◮ 3.5” QVGA (320x240) 24 bit

color LCD

◮ Resistive touchscreen ◮ DVI out (up to 1024x768) ◮ TI TLV320AIC33 stereo audio

codec

◮ IEEE 802.15.4 wireless with IP

ver 802.15.4 support

◮ Touchpad ◮ 3 axis accelerometer ◮ 5-way rocker switch ◮ 6 general purpose buttons ◮ Speaker ◮ Microphone ◮ Built-in 1300mAh Polymer

Li-ion battery

Ben Goska and Tim Harder Oregon State University Lessons Learned Designing an Open Source UMPC

SLIDE 6

Outline What is the OSWALD? Development team Project history Design considerations Hardware Firmware/Bootloaders Kernel Software Educational usage

Manufacturing process

Ben Goska and Tim Harder Oregon State University Lessons Learned Designing an Open Source UMPC

SLIDE 7

Outline What is the OSWALD? Development team Project history Design considerations Hardware Firmware/Bootloaders 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

SLIDE 8

Outline What is the OSWALD? Development team Project history Design considerations Hardware Firmware/Bootloaders 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

SLIDE 9

Outline What is the OSWALD? Development team Project history Design considerations Hardware Firmware/Bootloaders 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

SLIDE 10

Outline What is the OSWALD? Development team Project history Design considerations Hardware Firmware/Bootloaders 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

SLIDE 11

Outline What is the OSWALD? Development team Working with a small team of students Moving the project forward

Extremely small development team

◮ Pros ◮ Cons

Ben Goska and Tim Harder Oregon State University Lessons Learned Designing an Open Source UMPC

SLIDE 12

Outline What is the OSWALD? Development team Working with a small team of students Moving the project forward

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

SLIDE 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