Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Landing Teams within Linaro

2,955 views

Published on

A description of what Landing Teams do within the Linaro organization.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Landing Teams within Linaro

  1. 1. An Overview of Landing Teams inside Linaro Jamie Bennett, Release Manager Linaro.org
  2. 2. Schedule • Hardware Enablement • What is a Landing Team? • ARM’s Landing Team
  3. 3. Schedule • Hardware Enablement • What is a Landing Team? • ARM’s Landing Team
  4. 4. Hardware Enablement What is Hardware Enablement? “The engineering work involved in preparing a Linux- based software stack to work on a selected hardware platform”
  5. 5. Hardware Enablement What is Hardware Enablement? • Low-level initialization • Board configuration • Device driver development • Optimization of speed, power consumption • Validation of the integrated changes
  6. 6. Hardware Enablement What is Hardware Enablement? USB and Basic GFX Basic Linux Kernel Boot Loader Networking Output GFX Multimedia Acceleration Optimization Input/UI Power All Device Enhancement Management Drivers Complete
  7. 7. Hardware Enablement Upstreaming
  8. 8. Hardware Enablement Upstreaming • Kernel and tools versions increment every few months • Very tough for silicon partners to keep at leading edge for their SoCs/Dev board BSPs • OEMs and Distros increasingly wanting latest features, performance and stability
  9. 9. Hardware Enablement Upstreaming • Why Upstream? • Maintenance • Upstream/Community Relations • Free Testing • Problems of Upstreaming • Patch Author, Project Maintainer expectations • Potential long patch iterations • Significant communications • Upstream is a moving target!
  10. 10. Hardware Enablement Upstreaming • Buffer between constantly changing upstream and a stable platform • Decouples upstream from hardware enablement • System wide verification • Controlled Test verification • Its what all distributions do • Stable Target!
  11. 11. Hardware Enablement Staged Upstreaming • Buffer between constantly changing upstream and a stable platform • Decouples upstream from hardware enablement • System wide verification • Controlled Test verification • Its what all distributions do • Stable Target!
  12. 12. Schedule • Hardware Enablement • What is a Landing Team? • ARM’s Landing Team
  13. 13. Landing Teams • Where do Landing Teams fit in Linaro?
  14. 14. Landing Teams • What are Landing Teams? • Each Silicon Vendor gets one Landing Team • A Landing Team comprises of: • 1 Technical Liaison Engineer (a conduit between the vendor and Linaro) • 1 Project Manager • Number of Engineers depending of effort required to enable vendor hardware
  15. 15. Landing Teams • What do Landing Teams do? • Analyze any current board support patches • Integrate patches into Linaro vendor specific trees • Build kernel and vendor packages against the Linaro toolchain • Generate minimal images for validation • Fix any problems arising from this effort
  16. 16. Landing Teams • What do Landing Teams do (cont)? • Vendor specified Images (netbook, handset, ...) • Submission of vendor patches into the official Linaro trees (maintenance hand-off) • Drive upstream patch submission from vendors • Vendor specific toolchain optimizations and experimentations • Handle proprietary code • Project Manage
  17. 17. Landing Teams • What do Landing Teams need? • Hardware, hardware, hardware, hardware, ... • Vendor patches • Vendor specific software packages • Vendor engineering effort
  18. 18. Schedule • Hardware Enablement • What is a Landing Team? • ARM’s Landing Team
  19. 19. ARM’s Landing Team Initial area’s of Interest • Versatile Express • DS-5 Toolchain • New architecture development
  20. 20. ARM’s Landing Team Versatile Express current status • Bootloader • Kernel • rootfs • everything else
  21. 21. ARM’s Landing Team Versatile Express current status (1/4) • Bootloader • Refactored patches based on initial work done by Peter Pearse sent upstream 28th July • Matt Waddel leading the work • Initial upstream comments are favourable.
  22. 22. ARM’s Landing Team Versatile Express current status (2/4) • Kernel • All work being done by ARM engineers and being pushed upstream. ARM doing a perfect job. • Matt Waddel testing output • LTP tests being run • Frame buffer bug being worked on
  23. 23. ARM’s Landing Team Versatile Express current status (3/4) • rootfs • minimal and netbook rootfs both work with minimal tuning • Image building planned
  24. 24. ARM’s Landing Team Versatile Express current status (4/4) • Everything else • Hardware debugger support • gdb currently has some issues • QEMU support required?
  25. 25. ARM’s Landing Team DS-5 Toolchain • Nothing planned as of yet • Requirements need defining to determine the optimum landing team size • Great candidate for a more wide-spread distribution effort to gain exposure and help open source development
  26. 26. ARM’s Landing Team New architecture development • Landing teams can support features of up coming hardware • Can be shared at ARM’s discretion; Linaro understand the need to keep pre-announcement hardware private for a time • Requirements need defining
  27. 27. Questions? jamie.bennett@linaro.org

×