[poky] Poky Laverne 4.0 Released

[Richard Purdie]

It gives me great pleasure to announce a new Poky release, Poky
'Laverne' 4.0. This comes alongside the launch of the Yocto Project
which is a new Linux Foundation project targeted at embedded developers
of which Poky is now proud to be a part. This aims to be a place
embedded developers can collaborate around a tools and other
developments, see http://www.yoctoproject.org/ for more information.

As part of this, we're making the split clear between the reference
binaries that usually accompany a release which are now a part of the
Yocto Project and the build system itself which remains Poky.

Sources and binaries are linked to from both the Poky website and
http://www.yoctoproject.org/

Release notes for Poky 4.0 and Yocto 0.9 follow.


Yocto 0.9 built by Poky Laverne Release 4.0
===========================================

- Features and Updates
- Known Issues


FEATURES AND UPDATES
====================

- Poky Build System Updates
   * Task based shared state
   * Split packages directory (now recipes-*)
   * BSP layer specifcation
   * Enhanced layer support
   * Support for multiple build directories
   * Support for readonly central installs
   * Ability to build GPL v2 only target images
   * Swapper integrated to detect host contamination
   * Shared state and checksumming leading to prebuilt binary support
- Prelink Tool Integration
   * Integration of cross prelink tools into Poky
- Toolchain Update
   * GCC 4.5.0
   * Binutils 2.20.1
   * eglibc 2.12 is default libc provider
- New and Updated Recipes
   * Major update of core recipes
   * Added additional packages towards LSB support
   * Added QT4 libraries and demo code
   * Xorg stack updates
   * Yocto embedded kernel (2.6.35) and support tools
- Packaging
   * Default to rpm packaging backend (ipk and deb still available)
   * Used pseudo for setting ownership and permissions
   * Software package management now use RPM5 and Zypper
- Standalone Yocto SDK Generator
   * Enable embedded application development       
   * Generated by Poky
   * Consists of a sysroot representing a target system
   * Includes a standalone cross compiler and cross build tools
     to isolate the two systems
- Yocto SDK Generator IDE Plug-ins
   * Works within IDE using Yocto sysroot environment and cross
     platform toolchains
   * Remote user space tool suite interaction
   * Eclipse support               
   * Anjuta support
- Yocto SDK Generator remote agent
   * TCF extension allowing remote control
   * Runs on the target "device"
   * Manage tasks e.g. deployment, launching remote tools, setup
     cross debugging session
- Qemu basic system simulation/emulation
   * Enhanced with GL passthrough (x86)
   * User mode NFS support 
- User space tool suite for target device tuning, analyzing and 
  optimizing, which includes
   * OProfile
   * Powertop      
   * Latencytop
   * Perf
   * ftrace/lttng user space
- Host side clients for tools on target devices and IDE interaction, 
  which includes     
   * ProfileUI
   * Lttv-viewer
- Updated Documentation includes
   * Core Reference Manunal Updated
   * BSP developer's guide
   * Quick Start Guide
   * FAQs



KNOWN ISSUES
============

See bugzilla.yoctoproject.org

382 - OprofileUI cross endian issues

439 - No audio from the Blacksand board Front Channel auido jack.
      Workaround: run the following cmd: 'amixer sset "Front" 30 on'

467 - Issues building with Fedora 14, this distribution provided a
      version of make that is not compatible with the Poky build
      system, the workaround it to build a native version of make via
      the build system. Users of Fedora 14 will need to do a
      'bitbake make-native' before running any other targets.

429 - Building poky from scratch with /opt/poky in your path cause host
      contamination issues, be sure that /opt/poky is not in your path
      if building from scratch

160 - Emenlow Hardware gets stuck in the reboot sequence and
      needs to be power cycled.

Zypper / RPM Issues
489/490/491 - Due to some architectual difference between zypper and
              rpm5.0, there are some compatibility issues that prevent 
              zypper from working correctly. Packages can still be  
              managed with the rpm commands.