David Stewart, manager of the Yocto Project team within the Open Source Technology Center at Intel, gives an introduction to the Yocto Project, as well as a status update at ELCE 2012.
The Yocto Project is a joint project to unify the world’s efforts around embedded Linux and to make Linux the best choice for embedded designs. The Yocto Project is an open source starting point for embedded Linux development which contains tools, templates, methods and actual working code to get started with an embedded device project. In addition, the Yocto Project includes Eclipse plug-ins to assist the developer. This talk gives a walk-through of the key parts of the Yocto Project for developing embedded Linux projects. In addition, features will be described from the latest release of the Yocto Project, v1.3. The talk will include demos of some of the key new features such as the Build Appliance and Hob.
At the end of the talk, developers should be able to start their own embedded project using the Yocto Project and use it for developing the next great embedded device.
Hans Verkuil, R&D software engineer at Cisco Systems Norway, talks about Video4Linux status, progress, and plans at the embedded Linux Conference in Barcelona, Spain, on November 7, 2012.
Video4Linux is a fast-changing subsystem where a lot of work is done to support the complex video hardware of embedded systems. This presentation will give an overview of the developments in the past year and the work that is planned for the near future.
Hans covers SoC video devices support, core, control, and videobuf2 frameworks, HDTV timings & events API, video connector support, media controllers, codec & flash support, and more…
You can also download the slides for this presentation. For further details about development, subscribe to linux-media mailing lists or chat on #v4l IRC channel on freenode.
Tsugikazu Shibata, chief manager of OSS promotion center at NEC, gives a status update for LTSI, an LTS kernel for the consumer electronics market at ELCE 2012.
LTSI (Long-Term Stable Initiative) had been established October 2011 as an activity of CE Working Group of The Linux Foundation. LTSI will maintain Linux kernel for long term and stable for use of Consumer Electronics industry to share common cost and also help industry engineers to merge their patches into upstream. This talk will update latest status of LTSI project and discuss about next step such as how the development process going on and what version of Linux kernel will be maintained for long term and stably use. This talk will be intended to provide information for managers and engineers in the embedded industry and not necessary to have specific knowledge.
Agenda of the talk:
Status of Linux kernel development and maintenance of long term kernel
Thomas Gleixner, Linux kernel programmer at Linutronix, talks about UBI flash management layer, and fastmap implementation to speed up boot times at the Embedded Linux Conference Europe, on November 7, 2012.
UBI is a flash management layer in the Linux kernel designed to handle especially the shortcomings of NAND flash. UBI itself has the requirement to scan the full flash at boot time. With flash sizes becoming larger and larger this can take quite some time. A recent development implemented fast mapping functionality which is designed to put an upper bound on the number of flash eraseblocks to scan. This allows faster boot times without sacrifying the robustness of UBI. This talk gives an overview of the UBI fastmap design and looks at costs and benefits.
The talk provides an overview of UBI and its shortcomings, and explains UBI fastmap implementation in details showing it provides significant speedup proportional to the flash size. UBI fastmap has been merged in Kernel 3.7.
Tero Kristo, Linux kernel developer at Texas Instruments, explains how to debug power management in Embedded Linux at ELCE 2012.
The presentation will talk about debugging various problems a kernel developer can face when working with power management. These include hardware related issues (IC / HW layout bugs, bad documentation) and software related (kernel bugs, driver problems, adding new kernel features, bad userspace behavior.) Along with presenting some of these problems, I will discuss about ways to debug these… power management typically requires specific tools to be used. I will base the discussion on my first hand experience from working with Linux PM. Target audience is (kernel) software developers interested in power management.
Marcin Juszkiewicz, software engineer at Canonical, explains how ARMv8 was bootstrapped with OpenEmbedded with fast model simulation at the Embedded Linux Conference in Barcelona on November 7, 2012.
The time has come – there is ARM 64-bit architecture right behind a corner. In this talk I will present how OpenEmbedded was used to build root filesystem for fast models simmulating not-yet-existing hardware. Presentation is targeted at developers interested in cross compilation, handling new architectures in existing projects.
Agenda of the talk:
Introduction to Aarch64 – aka arm64 or ARMv8, the new 64-bit version of the ARM architecture
Introduction to OpenEmbedded – Build system capable to build everything from package to
whole distribution with repositories
Create own layer for AArch64 stuff
Adding basic support into OE classes
Toolchain – Based on gcc 4.7 + ARM patches
Build results – As of October 2012, 800 packages have been built, and LAMP and SDK images are available
Typical problems – configure scripts, old config files, and CPU/Architecture definitions
Current status – Merged into OpenEmbedded, Available in meta-linaro layer and meta-aarch64 layer
Lars Knoll, chief maintainer for the Qt Project, gives a presentation about Qt on embedded systems, including a demo with the Raspberry Pi at the Embedded Linux Conference Europe 2012 in Barcelona, Spain.
For well over 10 years, Qt has been used in many types of embedded devices, ranging from high-end medical systems, through mobile phones and smartphones, all the way to simple devices like coffee makers. This presentation will show some of the work that has been put in Qt throughout the years to support embedded devices, some of the challenges that the development team faced in order to bring a fully-featured desktop toolkit to resource-limited devices, along with solutions they came up with. Time permitting, the presenter will also show Qt demos running on an embedded device.
This session is intended for embedded application developers looking to make use of the capabilities of recent hardware, as well as decision makers looking for technology to enable their product solutions. The presenter is the Qt Chief Maintainer, having worked on and off embedded device development for a decade.
Here are the key sections of the talk:
A bit of Qt Embedded history – QWS, Qt Palmtop, Qtopia… used in industrial applications, VoIP phones,
Qt Quick – QML language, easy to bind and extend with C++
Project Lighthouse & Qt5
EGLFS & Wayland – For graphics support. EGLFS: Great option for single process UIs if EGL and OpenGL is available. Wayland: Best solution for multi process environment, integrates with other frameworks
Qt Raspberry Pi Demo
Qt on Android
Presentation slides are not available for this talk, but you can download some other similar “Qt on Embedded Systems” slides for a speech by Lars given at Qt Developers Day Europe 2012.
Tim Bird, senior staff software engineer at Sony Network Entertainment, hosts a BoF session about tools & methods for embedded Linux developers at ELCE 2012.
In this Birds-of-a-Feather-session, Tim will share some of his favorite tips for developing embedded Linux software. This will include tips for using ‘git’, how he does multi-platform development, and tips for other tools that other developers might find useful. Prior to the event, Tim will do a survey and solicit ideas from other developers as well. Please come to this BoF prepared to share your own productivity tips for embedded Linux development.
Tim talks is divided into the following key points:
Git tips – How to finds info about commits (git log, git show), use aliases (e.g. for colored output), find a commit that caused problem (git bisect), and more