● MeeGo and PandaBoard – was it easy?
● Challenges Faced
● Directions Taken
● Current Status and future directions
● Short Preview
MeeGo and PandaBoard
Was it easy?
● Big upstream focused Team
● TI world wide development – Dallas, Mexico, India, France, ....
● Development for Ubuntu, Android, Angstrom,.....
● Small MeeGo focused Team
● 4-5 members from India, Dallas, Mexico
● Does not really need huge investment to enable if upstream
● Decision early on to be a community focused
platform – hardware and software :) - PandaBoard
was a blessing!
● Thank you MeeGo community – our experience
Challenges faced 1/2
● Big Corporations do not move fast enough for
upstream – TI inclusive
● Inhouse code is easier to do than upstream – you
just need your platform to work! Upstream is
compromise, better quality and harder to achieve
● Meaning of upstream varies
● Some folks call upstream == “submitted to ML”!!
● Upstream is not very predictable – A manager's worst nightmare:
put a schedule around upstreamed features!
● Features in upstream may not be as fancy and
usable as “private code” versions!
Challenges faced 2/2
● Surprise: Kernel upstream support for display and EHCI
was not ready! No display == no UI!
● MeeGo is constantly evolving – kernel(2.6.35) Vs kernel-
dev(2.6.37-rc1) – TI upstream leverage
● New platforms on a brand new OS has surprises as well:
● Mic2 and libgparted story – boot sector formatting for mmc cards!
● -show-cursor option in apps – developers did not really think for handset
UI to be used with a mouse and keyboard
● More importantly – putting Symbian and Android
developers into MeeGo development – world of
difference – for the better :)
Decisions made in
PandaBoard MeeGo● Team split into two:
● Upstream is more important – TI team split into long
term objective of upstream version of MeeGo on
– Work with development teams inside TI to identify
components that are critical to upstream and
force the issue to take place – realities of a
– Work with the community to help enable features
using upstream components – upstream should
mean more beyond “nice looking code”!
● Private-demo – showcase what TI internal code can
do with MeeGo (TI internal code based on 2.6.35
Current Status and directions:
● Basic shell prompt – all using upstream versions
● Focus kernel
● EHCI support posted to appropriate ML – expected to make 2.6.38-rc1
● Display support over DVI – framework patches posted upstream –
hopefully by 2.6.38-rc1 – few more follow on upstream patches required
● WLAN – to be worked on
● Focus gstreamer/mm:
● Gstreamer 0.11 support patches in the works – but long term
● Short team 0.10 support needs to be worked out.
● Focus UI:
● Enable IVI, netbook?
● Enable SGX
● Focus Build: move to IMG/BOSS
Current Status and directions:
TI private version
● Full UI up with HDMI– basic apps work, network works
● Future directions:
● SGX enablement
● MM playback capability
● Wlan security access points
● Pulseaudio integration
● Maybe modem integration??
● Even probably switch to Blaze development platform
Contribute as a platform developer
● pandaboard.org – TRM, DM, schematics, Order it as
● Initial OMAP4 support in meego OBS and staging
● IRC : irc.freenode.net
● #pandaboard – pandaboard specific
● #linux-omap – anything linux and omap specific
● #meego – anything meego specific
● #meego-arm – anything meego and arm specific (including meego
• Designed as a vehicle for mobile software development
• Community support for various Linux-based distributions; like MeeGo
• Dual-core performance, SMP support, open source foundation, community-driven support
• Out-of-the-box 1080p, WLAN, Bluetooth® technology features and more
• Available through distributors
It’s all about community!
Introducing the world’s first open,
OMAP™ 4 processor-based mobile
software development platform