From: Tom Zanussi <tom.zanussi@intel.com>
To: yocto@yoctoproject.org
Cc: Darren Hart <dvhart@linux.intel.com>
Subject: Updated Yocto Hands-on Kernel Lab available
Date: Fri, 15 Feb 2013 20:29:07 -0600 [thread overview]
Message-ID: <1360981747.1691.29.camel@empanada> (raw)
Hi,
I'm happy to announce that an updated version of the Yocto 'Hands-on
Kernel Lab' has been released and is available here:
https://www.yoctoproject.org/sites/yoctoproject.org/files/elc2013-kernel-lab.pdf
The above document contains all the instructions you need to get started
from scratch.
You can always get to the lab and associated content by visiting the
Yocto home page (https://www.yoctoproject.org/) and selecting 'Read
presentations about the project' from the drop-down list you get by
clicking on the 'Start Here to learn more' box on the left-hand side and
clicking on the 'Working with the Kernel' presentation link.
The 'Hands-on Kernel Lab' has been updated to Yocto 1.3 ('danny') and
has been substantially expanded from three to five labs, with completely
new sections covering custom kernels, loadable modules and getting them
into (and autoloaded into) images, external modules, local clones, bare
local clones, and enabling LTSI features.
See below for a more complete listing of what's covered along with the
lab number covering those topics.
I've run through the lab twice, once on Fedora 17 and once on Ubuntu
12.04, so it should be pretty solid at this point, but if you find
problems, please let me know...
* Creating and using a traditional kernel recipe (lab1)
* Using 'bitbake -c menuconfig' to modify the kernel configuration and replace the defconfig with the new configuration (lab1)
* Adding a kernel module to the kernel source and configuring it as a built-in module by adding options to the kernel defconfig (lab1)
* Creating and using a linux-yocto-based kernel (lab2)
* Adding a kernel module to the kernel source and configuring it as a built-in module using linux-yocto 'config fragments' (lab2)
* Using the linux-yocto kernel as an LTSI kernel (configuring in an item added by the LTSI kernel which is merged into linux-yocto) (lab2)
* Using an arbitrary git-based kernel via the linux-yocto-custom kernel recipe (lab3)
* Adding a kernel module to the kernel source of an arbitrary git-based kernel and configuring it as a loadable module using 'config fragments' (lab3)
* Actually getting the module into the image and autoloading it on boot (lab3)
* Using a local clone of an arbitrary git-based kernel via the linux-yocto-custom kernel recipe to demonstrate a typical development workflow (lab4)
* Modifying the locally cloned custom kernel source and verifying the changes in the new image (lab4)
* Using a local clone of a linux-yocto- kernel recipe to demonstrate a typical development workflow (lab4)
* Modifying the locally cloned linux-yocto kernel source and verifying the changes in the new image (lab4)
* Using a 'bare' local clone of a linux-yocto- kernel recipe to demonstrate a typical development workflow (lab4)
* Modifying the locally cloned 'bare' linux-yocto kernel source and verifying the changes in the new image (lab4)
* Adding and using an external kernel module via a module recipe (lab4)
* Using the 'Yocto BSP Tools' yocto-bsp tool generate a new Yocto BSP (lab5)
* Using the 'Yocto BSP Tools' yocto-kernel tool to add kernel patches and config fragments (lab5)
next reply other threads:[~2013-02-16 2:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-16 2:29 Tom Zanussi [this message]
2013-02-16 2:54 ` Updated Yocto Hands-on Kernel Lab available Stewart, David C
[not found] ` <CAHUNapRsL+R2+inZztqdTBfVM9EZNtgTWayjLWXE_6tQnd+6Mw@mail.gmail.com>
2013-02-18 2:16 ` Trevor Woerner
2013-02-18 6:28 ` Tom Zanussi
2013-02-18 23:50 ` Trevor Woerner
2013-02-19 5:31 ` Tom Zanussi
2013-02-19 10:31 ` Trevor Woerner
2013-02-19 17:45 ` Tom Zanussi
2013-02-20 3:34 ` Trevor Woerner
2013-02-20 18:48 ` Tom Zanussi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1360981747.1691.29.camel@empanada \
--to=tom.zanussi@intel.com \
--cc=dvhart@linux.intel.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.