initial commit of Enea Linux 3.1HEADmaster

Migrated from the internal git server on the dora-enea branch

Signed-off-by: Adrian Dudau <adrian.dudau@enea.com>

1 files changed, 369 insertions, 0 deletions

diff --git a/presentations/automotive-linux-summit-2012/automotive.pin b/presentations/automotive-linux-summit-2012/automotive.pin
new file mode 100644
index 0000000..c5292fb
--- /dev/null
+++ b/presentations/automotive-linux-summit-2012/automotive.pin
@@ -0,0 +1,369 @@
+#!/usr/bin/env pinpoint
+
+[fill]
+[bottom]
+[font=ITC Kabel Semi-Bold 60px]
+[transition=fade]
+-- [yocto.jpg] [duration=15.152699]
+
+# Ross Burton, Userspace Architect for Yocto
+# Open Source Technology Centre at Intel
+# This session is a high level introduction to the Yocto Project
+
+-- [cars2.jpg] [duration=18.412748]
+What is the Yocto Project?
+# Appears to be confusion in the automotive community about the Yocto Project.
+# What is is, what it can offer and so on.
+# We were invited by the LF to come here and clarify what Yocto is.
+# So, the Yocto Project is...
+
+-- [umbrella.jpg] [duration=13.583521]
+Umbrella project
+# An umbrella project.
+# You don't download or install the Yocto Project itself
+# Just like you don't install the Apache Foundation
+
+-- [tools.jpg] [duration=27.991919]
+Build environment
+and development tools
+# An embedded build environment and development tools
+# Specifically, a build system (bitbake), package metadata (oe-core),
+# Eclipse plugin, Application Development Toolkit (deployable toolchain)
+
+-- [cpus.jpg] [text-align=center] [center] [duration=49.765675]
+x86 • ARM
+MIPS • PowerPC
+# We support all of the big architectures.
+# oe-core builds for qemu machines for all of these architectures
+# Ensures that the core builds for everything
+# Optional BSPs for specific platform support
+# Everything is cross compiled, so no "but it worked for x86" problems
+
+-- [people.jpg] [duration=22.377592]
+Collaboration space
+# Finally YP is a collaboration space, providing a forum
+# for users to share their problems and solutions
+# Public mailing lists and weekly phone conference
+# PAUSE
+
+-- [minifigs.jpg] [center] [duration=18.553514]
+So many choices…
+# When picking a platform what's the difference between yocto and
+# android, linaro, tizen, buildroot, baserock, or hacking your
+# favourite desktop distribution...
+
+-- [engineer.jpg] [duration=56.184429]
+…why pick the Yocto Project?
+# YP is Linux for embedded, from a small ARM board to mission critical
+#  xeon clusters
+# Builds a custom distro suited to your needs
+# Easy to add, remove, or change components
+# Open development process, no code drops or license complications
+
+-- [cables.jpg] [duration=40.872715]
+Some are easy to hack on,
+but you’ll regret it later
+# Especially if your target is x86, it's easy to start with a
+# desktop distribution and chop pieces out
+# Building new pieces and rebuilding the pieces that need changes
+# But when you need to change hardware, or rebuild with different compiler flags
+# It's not that easy any more
+
+-- [road.jpg] [top] [duration=47.108444]
+Designed for the long term
+# Yocto is designed for long term use
+# Six monthly release cycle but maintained release branches
+# Commercial support from OSVs
+# Tools to help do the mundane distribution building
+# - Generate package repos and disk images
+# - Static release archives for license compliance
+
+-- [tumble.jpg] [top] [duration=45.338825]
+Won’t fall apart in time
+# Yocto won't surprise you late in product development
+# Reproducable builds for the entire system
+# Clear process for updates - easy to make the changes
+# and publish a new image or repo
+# GPL compliant - trivial to public source *and* build instructions
+
+-- [group.jpg] [duration=9.779828]
+Who is in the Yocto Project?
+# Not a complete list
+
+-- [chip.jpg] [duration=15.615728]
+Hardware manufacturers
+# i.e. Intel, Texas Instruments, Freescale
+
+-- [tins.jpg] [duration=26.482639]
+Embedded OSVs
+# i.e. Wind River, MontaVista, Enea Software, Mentor Graphics
+# Commercial supported linux from these vendors
+
+-- [cat.jpg] [duration=31.311359]
+Consultants and individuals
+# Consultants, small and large
+# individuals "scratching an itch" for their own projects
+
+-- [owl.jpg] [top] [duration=60.471573]
+Advisory Board
+# finally should mention the advisory board.
+# Yocto is a project at the Linux Foundation, not owned by any
+# particular company
+# The advisory board is comprised of reps from member companies
+# working on Yocto
+# The boards first action was to name itself "advisory board" rather
+# than "steering group" to reflect that it offers advice and input and
+# doesn't control the project technical direction entirely in the
+# hands of the architects and maintainers
+
+-- [xwing.jpg] [duration=10.061844]
+How does it work?
+# Enough about what the Yocto Project can do
+# How does it work?
+
+-- [cake.jpg] [duration=36.383984]
+It’s all about the layers
+# A YP distribution is assembled from a number of layers
+# Layers are modular and you can combine layers from different sources
+# An example
+
+-- [blueprint.jpg] [text-align=center] [duration=19.801914]
+Bitbake
+# Build system
+
+-- [blueprint.jpg] [text-align=center] [transition=none] [duration=42.480724]
+oe-core
+Bitbake
+# core metadata
+# toolchain, kernel, eglibc, cairo, gstreamer, Xorg, Wayland (soon), gtk/qt
+
+-- [blueprint.jpg] [text-align=center] [transition=none] [duration=27.569431]
+meta-intel
+oe-core
+Bitbake
+# unless you happy with a qemu emulated machine you'll need a bsp
+# Intel hardware BSP, such as cedar trail (atom, netbook/industrial), fish river
+# island 2 (atom, digital signage, smart services), jasper forest (xeon, server)
+
+-- [blueprint.jpg] [text-align=center] [transition=none] [duration=42.118870]
+meta-yocto
+meta-intel
+oe-core
+Bitbake
+# Distribution policy
+# (Poky in meta-yocto for historial reasons)
+
+-- [corridor.jpg] [duration=15.193717]
+Let’s build something!
+# Enough talk, let's pretend to build something.
+
+-- [corridor.jpg] [center] [duration=58.901318]
+<tt>$ <b>wget http://downloads.yoctoproject.org/…
+       /poky-denzil-7.0.tar.bz2</b>
+$ <b>tar xjf poky-denzil-7.0.tar.bz2</b>
+$ <b>cd poky-denzil-7.0</b></tt>
+# One of the downloads from the Yocto Project is Poky, a reference
+# distribution.  This is basically Bitbake, oe-core, and meta-yocto
+# glued together for convenience Grabbing and extracting the tarball
+# of the 7.0 "denzil" release is as you'd expect
+
+-- [corridor.jpg] [center] [duration=44.895329]
+<tt> $ <b>./oe-init-build-env</b>
+ ### Shell environment set up for builds. 
+ ### You can now run 'bitbake &lt;target&gt;‘
+ Common targets are:
+   core-image-minimal
+   core-image-sato
+ …
+ $ <b>emacs conf/local.conf</b></tt>
+# First you need to source a shell script to setup the environment. 
+# Now lets have a quick look at the configuration file
+
+-- [corridor.jpg] [center] [duration=64.857567]
+<tt> # BB_NUMBER_THREADS = "4"
+ # PARALLEL_MAKE = "-j 4"
+ 
+ MACHINE ??= "qemux86"
+ …
+ #MACHINE ?= "qemuarm"
+ #MACHINE ?= "qemumips"
+ #MACHINE ?= "atom-pc"
+ #MACHINE ?= "beagleboard"</tt>
+# Just a small fragment of the options available.  Defaults are all
+# reasonable and it will successfully build out of the box.
+# For a faster build, change the parallel options. My build machine is
+# a quad core with hyperthreading, so I set both of those to 8 to keep
+# it busy
+# Default target is x86 on qemu.  This is trivially changed by simply
+# changing the MACHINE variable.
+# Other options include where to keep downloaded tarballs; location of
+# any mirrors; features to enable such as multiarch, installing the
+# toolchain in the image for development, what package format to use,
+# and more.
+
+-- [corridor.jpg] [center] [duration=38.235931]
+ <tt>$ <b>bitbake core-image-minimal</b></tt>
+# Then, you can run bitbake with the name of the target you want
+# Targets can be anything - images, packages, or operations.
+# Let's build core-image-minimal, a small system that boots to a
+# console good start to build up from if you're making a
+# single-purpose system
+
+-- [corridor.jpg] [center] [duration=61.638290]
+<tt>Currently 7 running tasks (5452 of 9438):
+0: webkit-gtk-1.8.2-r1 do_compile (pid 27137)
+1: qt4-embedded-4.8.1-r48.1 do_compile (pid 27129)
+2: qt4-x11-free-4.8.1-r46.1 do_compile (pid 27096)
+3: systemtap-1.8+git1…-r0 do_compile (pid 27130)
+4: gmp-5.0.5-r0 do_package_write_rpm (pid 27131)
+5: libglade-2.6.4-r4 do_package_write_rpm (pid 27134)
+6: nfs-utils-1.2.3-r5 do_unpack (pid 27187)</tt>
+# While bitbake is running you'll see a report of what it's doing,
+# something like this. This isn't actually the output from
+# core-image-minimal but a colleague's world build that happened to be
+# running when I was writing the slides.  Poor guy is in for a long
+# wait, webkit and two qt builds.
+
+-- [corridor.jpg] [center] [duration=33.001926]
+<tt>$ <b>ls tmp/deploy/images/</b>
+…
+core-image-minimal-atom-pc-20120918205848.hddimg
+core-image-minimal-atom-pc-20120918205848.iso
+core-image-minimal-atom-pc-20120918205848.rootfs.cpio.gz
+core-image-minimal-atom-pc-20120918205848.rootfs.ext3
+</tt>
+# When it finishes building the results are in the deploy directory
+# Here we can see the constructed root file system as a cpio archive,
+# a bare filesystem, a bootable ISO image, and a disk image.
+# Generally I'd be writing the disk image to a fast USB stick with dd
+# and booting from that for testing.
+# The build output is configurable per build and per machine. This
+# build was for a fairly standard Intel system so the final output is
+# typically bootable on those.  Build for a say beagleboard and you'll
+# get kernel, bootloader and rootfs tarballs to write a SD card.
+# alongside the images directory there is the package repository that
+# was used to construct the root fs. This can be shared on the network
+# and used as a normal repository, ie install some development or
+# debug symbol packages to fix a bug.
+
+-- [hob.jpg] [duration=47.693535]
+Hob
+# Hob is a graphical interface to bitbake
+# demo gremlins have decided to break hob on this laptop - works on my build machine
+# 1st iteration, gtk+ application to configure an image and monitor the build
+# 2nd iteration, web-based. currently under development.
+
+-- [question.jpg] [duration=17.024797]
+Now what?
+# So that's how to build an image, but what could we do with it?
+# Two quick ideas
+
+-- [dolls.jpg] [top] [duration=42.701355]
+Virtualisation
+# I expect virtualisation to be common in next-generation automotive
+# systems as individual processors become more powerful and logically
+# separate systems are ran in virtual machines on fewer physical
+# processors.
+# Because systems built by Yocto can be trivially tuned to be exactly
+# what is required and nothing else they are a good match for
+# virtualised systems, both as a minimal host that does simply manages
+# the virtual machines, or as a specialized virtual machine itself.
+
+-- [dash.jpg] [top] [duration=24.712542]
+Specialised subsystem
+# Cars are complicated beasts these days with many processors performing specialised roles
+# Dashboard, engine management, and so on.
+
+-- [qa.jpg] [duration=10.726003]
+Q&amp;A
+
+-- [yocto.jpg]
+Thanks!
+
+# Credits
+#
+# cars2.jpg
+# http://www.flickr.com/photos/15443451@N00/516336421/
+# Creative Commons 2.0 BY-NC-SA (C) Piyapat Ch.
+# 
+# cables.jpg
+# group.jpg
+# tumble.jpg
+# umbrella.jpg
+# (C) David Stewart, All Rights Reserved, Used with Permission.
+# 
+# tools.jpg
+# http://www.flickr.com/photos/22749993@N08/5386712834/
+# Creative Commons 2.0 BY (C) Jim Pennucci
+# 
+# cpus.jpg
+# http://www.flickr.com/photos/17642817@N00/4553998825/
+# Creative Commons 2.0 BY (C) Jason Rogers
+# 
+# people.jpg
+# http://www.flickr.com/photos/29370225@N03/6292167005/
+# Creative Commons 2.0 BY (C) Roberto Trm
+# 
+# minifigs.jpg
+# http://www.flickr.com/photos/40646519@N00/305410323/
+# Creative Commons 2.0 BY (C) peter dutton
+# 
+# engineer.jpg
+# http://www.flickr.com/photos/39066002@N05/3595313340/
+# Creative Commons 2.0 BY-NC-SA (C) RoberthK
+# 
+# road.jpg
+# http://www.flickr.com/photos/81851211@N00/5861614/
+# Creative Commons 2.0 BY-NC-SA (C) Rick Harrison
+# 
+# chip.jpg
+# http://www.flickr.com/photos/19616961@N00/41549347/
+# Creative Commons 2.0 BY (C) Rodrigo Senna
+# 
+# tins.jpg
+# http://www.flickr.com/photos/75771631@N00/5185871835/
+# Creative Commons 2.0 BY (C) Matthew Hine
+# 
+# cat.jpg
+# http://www.flickr.com/photos/9516941@N08/2286083797/
+# Creative Commons 2.0 BY (C) Tristan Bowersox
+# 
+# owl.jpg
+# http://www.flickr.com/photos/95962912@N00/161060725/
+# Creative Commons 2.0 BY-NC-SA (C) Nuno Barreto
+# 
+# xwing.jpg
+# http://www.flickr.com/photos/55723329@N00/6657150957/
+# Creative Commons 2.0 BY (C) psiaki
+# 
+# cake.jpg
+# http://www.flickr.com/photos/megpi/2690878513/
+# Creative Commons 2.0 BY-NC-SA (C) megpi
+# 
+# blueprint.jpg
+# http://www.flickr.com/photos/71745913@N00/2576799956/
+# Creative Commons 2.0 BY-NC-SA (C) HD41117
+# 
+# corridor.jpg
+# http://www.flickr.com/photos/71865026@N00/1264424156/
+# Creative Commons 2.0 BY-SA (C) Mark Sebastian
+# 
+# hob.jpg
+# http://www.flickr.com/photos/11247388@N00/5436586179/
+# Creative Commons 2.0 BY (C) sunshinecity
+# 
+# question.jpg
+# http://www.flickr.com/photos/65555826@N00/1447024668/
+# Creative Commons 2.0 BY (C) wonderferret
+# 
+# dolls.jpg
+# http://www.flickr.com/photos/30692297@N07/5454308102/
+# Creative Commons 2.0 BY-NC-SA (C) Adrian S Jones
+# 
+# dash.jpg
+# http://www.flickr.com/photos/97856361@N00/167428099/
+# Creative Commons 2.0 BY-NC-SA (C) Albert Lynn
+# 
+# qa.jpg
+# http://www.flickr.com/photos/39039882@N00/22778226/
+# Creative Commons 2.0 BY-NC (C) Tantek Çelik