Device Tree on Android

Registered by Zach Pfeffer on 2012-01-09

[NOTICE]: This session will be cancelled since the kernel team will handle the Device Tree topic. All the people who have already subscribed this, would you please to transfer to this one?

https://blueprints.launchpad.net/linux-linaro/+spec/linaro-kernel-q112-device-tree-update-2012q1

And their session will launch on this Thursday, 09:00 - 09:55 at Grand Salon room:

http://summit.linaro.org/lcq1-12/meeting/20077/linaro-kernel-q112-device-tree-update-2012q1/

Thank you!

Blueprint information

Status:
Complete
Approver:
Zach Pfeffer
Priority:
Essential
Drafter:
Botao
Direction:
Approved
Assignee:
Botao
Definition:
Approved
Series goal:
Accepted for 2012q1
Implementation:
Implemented
Milestone target:
milestone icon connect-q1.12
Started by
Zach Pfeffer on 2012-02-27
Completed by
Zach Pfeffer on 2012-02-27

Related branches

Sprints

Whiteboard

Meta:
Roadmap id: ANDROID2011-FDT-LEB

Goal:
The goal of this session will be a realistic plan to enable device tree on all targets that will be moving to the 3.2 kernel.

Device tree was discussed at Linaro Connect 11Q4. The discussion was captured on https://blueprints.launchpad.net/linaro-android/+spec/linaro-platforms-lc4.11-android-device-tree.

The key outcome was that all kernels had to be on Linux kernel version 3.2.

As of the 12.01 release, the builds we're on:

Origen was on: 3.0.4
Snowball was on: 3.1.1
Panda was on 3.2.0-rc7, 3.1.0, 3.2.0-rc6, 3.0.8
iMX53 was on 3.1.0-rc9
Versatile Express was on 3.2.0

Agenda:
Talk about if any of the boards not at 3.2 will be upgraded to 3.2
Review Versatile Expresses changes for Device tree and see if they can be used for the other platforms
Talk about how Device Tree files get generated and if they need to get revisioned
Generate a per-board plan with dates that each will hit 3.2 and/or indicate the kernel will not hit that milestone

(?)

Work Items