David Greaves

Our world is full of small powerful devices; but most of them run Android.

I'll show how Mer, SailfishOS and HADK lets us reuse them as full blown linux systems - with touchscreens, 3D graphics, modem, wifi, usb...

At the heart is libhybris - talked about at FOSDEM; found inside the Ubuntu Touch distro, invented and developed at Mer & Jolla where it's used in the Jolla phone (ARM) and soon the Jolla tablet (x86).

Together we can route around the breakage of closed binary blobs and work on FOSS on these devices.

The spEEDO project aims to augment existing debug APIs (such as GNU's RSP and ARM's Coresight) with a power component for reporting and tracing energy use in multicore systems-on-chip. Energy is logged per IP block and per application thread and reports are made available to the operating system, to applications programs and over the debug interface. The aim is facilitate optimizations for energy-efficiency at all stages of software and silicon development.

Dr Greaves will report on the current state of the API and solicit adoption by and improvements from the SoC community.

Dr David J Greaves.

University of Cambridge Computer Laboratory in Collaboration with Ultrasoc Limited.

Covering Mer's birth, the MeeGo years and how we now work in a truly collaborative and open project to make Mer productizable.

Mer supports organizational collaboration; our vendor focus drove the design from the project structure through the architecture, the deliverables and the processes. We continuously ask "How will this decision affect vendors using our solution to make a product?"

Mer delivers a world-class platform for building products: after all, it's an ultra-modern Linux stack with a strong upstream focus that partners with a world-class graphical framework; it rocks!

I'll explain why "code is not enough"; what else we deliver and how we ensure that the code, policies and processes you tell your customers to use are up to the job.

Then the details of Mer and QtCreator; how the cross-compilation and emulation works in the Mer SDK.

Finally some future goals for Mer and our collaborators and a demonstration of some technology that is guaranteed to be of interest to people looking to build Qt products now, on hardware shipping today.

Mer says it is "aimed at device manufacturers" - but what does this mean? It has the same source as many other distros so this talk will introduce the non-code areas where Mer differentiates and how it does that by operating in the open. From systems and tools to processes; what's available, what Mer does and does not address and how a Mer-based project gets going?