Archive

Posts Tagged ‘wayland’

Tizen 3.0 Features & Tizen Lite Unveiled

November 12th, 2013 No comments

We have just learned about NX300M camera, the first Tizen device, based on Tizen 1.0, but development of the new mobile operating systems is still going on, and the key features of Tizen 3.0, as well as Tizen Lite, Tizen for low-end hardware, have been unveiled at the Tizen Developer Summit on 11th of November 2013.

Tizen_3.0_FeaturesTizen 3.0 features:

  • Update core OS and toolchain
  • Multiple user support
  • 64-bit Intel and ARM architecture support
  • (New) 3D UI Framework with 3D rendering for 2D and 3D objects in 3D, and a dynamic animation library
  • WayLand based compositor replacing X
  • Crosswalk – HTML5 based application runtime based on Chromium/Blink

Tizen 3.0 release is scheduled for Q3 2014, so the first Tizen smartphones and tablets which are expected for Q1 2014 will probably ship with Tizen 2.2.1, or even possibly with an earlier version.

Android KitKat 4.4 has been optimized to run smoothly on device with just 512 MB, but the newly announced Tizen Lite beats that as it will be optimized for devices with just 256MB RAM competing with other low footprint operating systems such as Firefox OS.

Tizen Mobile Full vs Tizen Mobile Lite

Tizen Mobile Full vs Tizen Mobile Lite

Where Tizen will run on hardware with at least 512 MB RAM, WVGA (800×480) minimum resolution, and use at least 1GB flash, Tizen Lite will run on even lower end hardware with 256 MB RAM, HVGA (480×320) to QVGA (320 x 240) displays, and require at least 512 MB flash. Interestingly, the minimum specs corresponds to ZTE Open, one of the first Firefox OS phone.

Via Liliputing, Tizen Experts, and The HandHeld Blog

Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter

Categories: Tizen Tags: arm, intel, smartphone, tizen, toolchain, wayland

LinuxCon Europe 2013 Schedule – Web Technologies, Debugging Techniques, Wayland, and More

August 22nd, 2013 No comments

I’ve just received an email from the Linux Foundation saying the schedule for LinuxCon and CloudOpen Europe 2013 had been made available. The conference will take place for 3 days (October 21-23, 2013) in the Edinburgh International Conference Center, Edinburgh, United Kingdom. There will be over 100 conference sessions, and several co-located events including: Automotive Linux Summit, the Embedded Linux Conference, Gluster Workshop, KVM Forum, Tizen Summit, Xen Project Developer Summit.

LinuxCon_Europe_2013

As I’ve recently done with LinuxCon North America 2013 and ARM TechCon 2013, I’ll make a virtual schedule with selected developer sessions using the event’s schedule builder. You may find out several sessions will also be given in LinuxCon North America.

Monday – 21st of October

This presentation will cover a brief introduction on how the Bluetooth Low Energy technology works. Then it will present the current status of its support on Linux, including the profiles we’re currently working on what can be expected to be finished on the near future. The currently available APIs and how to interact with Bluetooth Smart devices will be shown and there will be a few demos of Bluetooth Smart devices working with Linux.

Web Browsers are quickly becoming the most frequently used individual application in any modern desktop, following the same trend in mobile devices. They are growing in capabilities and performance, enabling an era of new webapps ranging from email to vehicle navigation and games. Current browsers are powerful enough to run even the Linux kernel in a Javascript PC emulator. Browsers are enabled by web engines, but have you ever questioned how they work? The objective of this talk is to present how a modern web engine works, following the several steps from the first user input to access a webpage up to the moment where content is rendered in the screen. Topics like multiprocess browser architecture, process sandboxing, content parsing and rendering will be covered. The web engine used for the discussion will be WebKit, with some examples drawn from Blink and Gecko.

The many tracing tools available on Linux today provide a wide array of choices for the users. Deciding which of them to use to diagnose system problems on production systems can prove challenging. Various tools have various states of integration within the Linux kernel, and also within different Linux distributions. Bleeding edge features are often just being merged into the upstream Linux kernel. It takes often a long time for such features to be incorporated in commercial distributions. The required set up for the tools and their level of usability also vary significantly. This talk will cover the more popular and actively developed tracing areas focusing on their latest updates and will describe the infrastructure they rely on. An overview of the tracing tools (ftrace, perf, systemtap, DTrace for Linux, etc) will be included with some examples of usage of each.

HTML5 is going to be used widely because of its powerful specification. A lot of browsers are now supporting HTML5. It is a new technology, so that currently only few engineers can use this technology. Needs of such skillful engineers are urgent and necessary from the point of Industry, such as automotive and others. We started the development of the certification program of HTML5 skill set. The purpose of this program is to encourage engineers to learn and and improve their skill set, and increase number of skillful engineers. In this presentation, I will provide why we started this program, how we develop, and time-frame.

Being one of the most successful open source projects to date, WebKit development process consists of a series of protocols and strict policies in order to obtain committer and reviewer status. Blink follows a similar approach with committers and scoped code owners, in a similar fashion as Linux Kernel does with its subsystem maintainers. Their open source success is due to not only solid support from major technology companies, but also to the high quality and automated testing performed on patches before submission. In this presentation, Bruno explains how the development process of both WebKit and Blink projects are – from submitting well-tested patches with strict policies to check, get review from community, and commit upstream via commit-queue system (including early warning system bots). This is a very practical talk with live demonstrations of patch submissions on both projects.

Tuesday – 22nd of October

Most of the kernel messages would be intended to know developers what’s going on in the kernel, and they tend to be not friendly to users and machines. To improve this, Hidehiro Kawai is trying to add hash value for each kernel message to identify them easily. If this feature becomes available, users can consult external manuals by feeding the hash and know detailed information. Or a monitor tool can identify specific message in low overhead and trigger a fail-over or collect related information automatically. In this presentation, he explains the implementation of the first RFC patch set, on-going discussions (if there are), and how utilizing the feature in user space, while introducing a similar challenge 5 years ago and how addressed its objections.

The Wayland project is growing fast, as well as its adoption by several toolkits. EFL (Enlightenment Foundation Libraries) specifically has a Wayland backend being actively developed over the last 2 years, with its latest features being already incorporated. EFL developers are also contributing back to the Wayland project itself, helping to improve the protocol and implementation, from a toolkit point of view. This talk will present the current development state of the Wayland backend of EFL, describing the latest incorporated features. It will also present the changes that this port has passed since the beginning of its development, and its improvements so far. A comparison to the other EFL backends will be done, as well as future plans for Wayland on EFL and the Enlightenment Window Manager.

Window managers and desktop environments in the Open Source community number in the dozens, but only a small number of those include compositors; fewer still can boast that they run seamlessly on embedded devices or in Wayland. Enlightenment is so flexible that it was chosen by Samsung to be to window manager for their new Linux-based mobile operating system, Tizen, in addition to being used by tens of thousands of users worldwide for over a decade. With the current development of E19, it’s time to take a step back and look at the main feature: compositor design. This presentation will give a brief introduction to compositing and window management before jumping directly into the history of Enlightenment’s compositor architecture and its progression to the current state of full Wayland and X support.

The 2013 version of this popular talk describing the current state of kernel development and where it can be expected to go in the near future. There will be some technical content, but this talk is highly accessible to non-technical participants as well.

Concurrency issues in the software, and data races in particular, may have devastating effects but are often quite hard to reveal. Hunting down such problems is especially important for the Linux kernel, which is inherently concurrent. Although there is a variety of tools to help reveal data races in the user-space code (Helgrind, DRD, ThreadSanitizer, etc.), there are only a few that can be applied to the kernel. In his presentation, Eugene Shatokhin will give an overview of such tools and the techniques they rely upon. Among other things, he will present KernelStrider, a component of KEDR Framework that collects data about the operation of the kernel modules in runtime. The data are then analyzed by an “offline” detector in the user-space to actually reveal the races. The results obtained so far as well as possible directions of future development will also be discussed.

Wednesday – 23rd of October

git bisect” is a command that is part of the Git distributed version control system. This command enables software users, developers and testers to easily find the commit that introduced a regression. This is done by performing a kind of binary search between a known good and a known bad commit. git bisect supports both a manual and an automated mode. The automated mode uses a test script or command.People are very happy with automated bisection, because it saves them a lot of time, it makes it easy and worthwhile for them to improve their test suite, and overall it efficiently improves software quality.

The GFS2 cluster filesystem has been under development for a number of years, however there has been no up-to-date presentation covering all of the latest features since OLS 2007. The intent of this talk is to provide an overview of the current feature set, noting recent significant developments, as well as an introduction into the major algorithms of GFS2 for those less familiar with its capabilities. During the development process, many lessons were learned which would apply equally to any open source project, and these will be discussed too.

October 21, 2013 marks the Qt Project’s second anniversary. Launched in 2011 to be the home of the Qt libraries and frameworks under Open Source Governance, the Qt Project has seen quite a lot of change in these 2 years., good and bad. It lost its main sponsor and many doubted the project would continue, but it did, and it managed to release the first major release in 7 years (5.0), one more feature release and half a dozen patch releases. This presentation will review the principles of the project’s governance, who the contributors are and how they work, the major changes that happened in the past two years and how they’ve influenced the project. It will explore the development process from patch to release and to maintenance / bug fixing, and will also show how non-code contributors participate.

As the number of cores in systems steadily increases, you may find that the good old mutual exclusion synchronization is not sufficient to let your application use more cores not only for heat generation, but primarily for effective computing. The Userspace RCU library implements Read-Copy Update (RCU) synchronization and various lock-free data structures that allow user-space applications to leverage very lightweight synchronization across cores. It allows a broad range of demanding applications to scale to large numbers of cores. This library is released under LGPL v2.1, so it can be used by all applications. This tutorial will walk the audience through the basics of Read-Copy Update, and then through the synchronization and data structure APIs exposed by Userspace RCU.

You can register to LinuxCon Europe 2013 and CloudOpen Europe 2013 online for the following fees:

  • US$475 through July 14th (Early)
  • US$575 July 15th – September 1st (Standard)
  • US$675 thereafter (Late)
  • Student Registration – $150
Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter

RebeccaBlackOS is a Linux Distribution Showcasing Wayland

May 29th, 2013 2 comments

nerdopolis, a developer and a Rebecca Black fan, has been maintaining a Linux distribution called RebeccaBlackOS that uses Wayland’s reference compositor Weston as the default for handling its graphical user interface, and automatically start “Friday” song as it boots.

RebbecaBlackOS

Rebecca Black Linux Desktop (Click to Enlarge)

This distribution actually supports both Wayland and X, as even though QT, GTK, EFL (Enlightenment Foundation Libraries), Clutter, and SDL (Simple DirectMedia Layer) have all been compiled to support Wayland, many apps don’t work with Wayland, so Xwayland provides a way to run many, but not all, X apps in Wayland.

You can try the latest 1.8 GB ISO image (24 May 2013), which is based on 32-bit Kubuntu 13.04, by transferring it to a USB flash drive via Unetbootin, or by using the ISO directly in VirtualBox (it will then use the framebuffer). I planned to try it before writing this post, by the “18 hours, 10 minutes remaining” message quickly dissuaded me from doing so. H-Online reports it does not include the latest Wayland and Weston version 1.1, but version 1.0.5 instead.

The developer explains this distribution is not really stable, and has some security issues, so this is mainly to play around with Wayland and check its development status. Further information on how to test Wayland with this distributions is available on the project’s sourcefore page.

Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter

Categories: Linux, Testing, Ubuntu Tags: Linux, ubuntu, wayland

Future Versions of Ubuntu To Feature Mir Display Server Compatible With Android Graphics Drivers

March 5th, 2013 3 comments

The X server is getting old, and many developers complain it’s not an optimal solution anymore due to its (over) complexity, which was why Wayland was developed. However, it turns out Ubuntu will not use Wayland, but instead their own display server called Mir which will be used in all form factors from phones to desktops.

Mir on Android Drivers (Now and in May 2013)

Mir on Android Drivers (Now and in May 2013)

Phoronix has provided a quick summary about the key aspects of Mir:

  • Mir is a new display server being developed at Canonical and it is not based on X.Org or Wayland.
  • Android graphics drivers will be supported.
  • Existing DRM/KMS/Mesa/GBM (the open-source Linux graphics drivers) will work. Canonical is pressuring the binary blob vendors to make their drivers compatible.
  • There will be support for legacy X11 applications through an integrated root-less X.Org Server.
  • Canonical will natively support GTK3 and Qt/QML toolkits with Mir.
  • Mir will be used for all form factors from Ubuntu Phones to the Ubuntu Linux desktop.
  • Mir should be ready for Ubuntu Phone OS by this October while it should come to other form factors (and the desktop) within one year.

Canonical has not chose Wayland because it could not fulfill their requirements completely, but due to their design, it would still be possible to add Wayland support by implementing a Wayland-specific frontend for the Mir server or by providing a client-side implementation of libwayland that talks to Mir.

Mir will also run on the free drivers software stack, but it does not run on closed source drivers now, and Phoronix reports that Canonical is in talks with closed-source vendors (NVIDIA and AMD) about supporting Mir and a unified EGL-centric driver model. From the look of it, it seems only desktop platforms will support the free Linux graphics drivers, which means other platforms such as smartphones and tablets may have to rely exclusively on the Android drivers (TBC).

There are three milestones for Mir development:

  • May 2013 -  Finish the first step towards integrating Unity Next with Mir and provide enough facility to start iterating the actual shell development.
  • October 2013 – Unity Next & Mir window management are completely integrated with the rest of the system to support an Ubuntu Phone product. Desktops and laptops will have access to a legacy mode that allows to run legacy X clients against an on-demand rootless X server.
  • April 2014 – Complete convergence across the form factors is achieved, with Mir serving as the carrier across form factors.

That means Ubuntu 14.04 LTS will be the first release to fully take advantage of the new display server.

Thanks to Guillaume.

Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter

Categories: Graphics, Linux, Ubuntu Tags: kernel, mir, qml, qt, ubuntu, wayland, x11

Linux Conference Australia and FOSDEM 2013 Videos are Now Online

February 8th, 2013 3 comments

FOSDEM 2013 took place last week, and the organizers are in the process of uploading videos. Up to now, 5 main tracks sessions have been uploaded (Firefox OS;  Free, open, secure and convenient communications; FreedomBox 1.0;  Samba 4; and systemd, Two Years Later) as well as over 20 lightning talks.

You can find the videos at http://video.fosdem.org/2013. You may also want to check my previous post for a lists of interesting talks, and I’ll probably feature some FOSDEM 2013 videos in this blog, at least the open source GPU driver talk.

LCA_2013Linux Conference Australia took place on January 28 – February 1, 2013, and the 5-day conference featured lots of talks including several dealing with graphics in Linux, and one developer apparently trashing X in terms of complexity and performance, and explaining how Wayland was better. Others Linux sessions dealt with subject such as 3D printing, supercomputing, Arduino, big.LITTLE processing, open source, git, Raspberry Pi, UEFI, and much more.

You can download LCA 2013 videos in MP4 or OGV formats.

Via H-Online

Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter

Qt on Embedded Systems – ELCE 2012

January 16th, 2013 No comments

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.

Abstract:

Qt LogoFor 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:

  • Qt Introduction
  • 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.

Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter

Wayland Library: X11 Display Server Replacement for Linux

February 14th, 2012 No comments

Wayland LogoThe X Window System has been implemented in Linux since the beginning and manages the graphical user interface of most Linux distributions, although some embedded systems do without X11 and use lightweight graphics libraries such as Nano-X, SDL, DirectFB etc…

X11 is invisible to the end-user but does all the hard work needed to have Gnome, KDE and Unity user interfaces work properly and smoothly.

However, in recent years, GNU/Linux desktop graphics has moved from having numerous rendering APIs talking to the X server which manages everything towards putting the Linux kernel in the middle with direct rending (e.g.  OpenGL, VDPAU/VAAPI) with window systems taking the backstage. This new architecture  provides a much-simplified graphics system offering more flexibility and better performance.

The problem is that the X Window System is highly complex, a complexity that is not really needed with the newest version of the kernel. That’s where Wayland protocol comes into play. Wayland is described as follows:

Wayland is a protocol for a compositor to talk to its clients as well as a C library implementation of that protocol. The compositor can be a standalone display server running on Linux kernel modesetting and evdev input devices, an X application, or a wayland client itself. The clients can be traditional applications, X servers (rootless or fullscreen) or other display servers.

Here’s a graphical comparison between X11 and Wayland.

X Architecture

X11 Architecture

Wayland Protocol Architecture (Click to Enlarge)

Wayland Architecture

Without going into details,  Wayland is clearly less complex than X11 as it gets rid off the middle man (the X server) and the number of messages as well as inter-process communication complexity are reduced.

Contrary to X11, Wayland uses direct rendering (DRI2), where the client and the server share a video memory buffer. The client links to a rendering library such as OpenGL that knows how to program the hardware and renders directly into the buffer. The compositor in turn can take the buffer and use it as a texture when it composites the desktop. After the initial setup, the client only needs to tell the compositor which buffer to use and when and where it has rendered new content into it.

Wayland can be backward compatible with X clients, so that all those existing applications won’t have to be rewritten. This will however require X server modifications so that it communicates with the Wayland compositor.

The first release of Wayland (and Weston) has been announced on the 9th of February 2012 with version 0.85. Version 1.0 is expected to be released in H2 2012. Wayland is the protocol and IPC mechanism while Weston is the reference compositor implementation.

The source code for both Wayland and Weston 0.85 libraries can be downloaded at:

  http://wayland.freedesktop.org/releases/wayland-0.85.0.tar.xz
  http://wayland.freedesktop.org/releases/weston-0.85.0.tar.xz

Ubuntu (Canonical), Fedora and KDE development teams have already planned to replace X11 by Wayland in future versions. Canonical is also planning to help port Compiz to OpenGL ES and Wayland is on the high priority list at Linaro for ARM support although it still needs approval.

For further details, you can visit Wayland page at freedesktop.org.

Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter

Categories: Graphics, Linux Tags: Linux, kernel, opengl, wayland, x11