Binary Blobs Attack!!!
Most SoC vendors distribute binary blobs with Linux kernel shims. These binary blobs enable graphics engines, DSPs and other cores on ARM and other architecture SoCs. These binary blobs tend to be tied to specific kernel versions which limits unreadability and hackability and complicates device manufactures, which slows down innovation and the introduction of new and unique computing devices. This BoF is aimed at trying to improve this situation with pragmatic steps.
Anyone interested in discussing their experience with binary blob integration, ideas for making this easier to deal with across architectures, ways to encourage openness while allowing vendor differentiation and others interested in a constructive dialog should attend.
Blueprint information
- Status:
- Complete
- Approver:
- Zach Pfeffer
- Priority:
- Essential
- Drafter:
- Zach Pfeffer
- Direction:
- Approved
- Assignee:
- Zach Pfeffer
- Definition:
- Approved
- Series goal:
- Accepted for 2012q1
- Implementation:
-
Implemented
- Milestone target:
-
connect-q1.12
- Started by
- Zach Pfeffer
- Completed by
- Zach Pfeffer
Whiteboard
Meta:
Roadmap id: ANDROID2012-
Goal:
The goal of this session is create a plan to more efficiently handle binary blobs.
Agenda:
Rant
Go through typical binary blob cycle and get sign off from all teams on supporting the current state of the world
Go through the current binary blob list and generate block diagrams of each
Talk about standardized interface for each of these blobs, functions, signalling, etc...
