<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/poky.git/meta/recipes-kernel, branch 1.3_M5</title>
<subtitle>Mirror of git.yoctoproject.org/poky</subtitle>
<id>https://git.enea.com/cgit/linux/poky.git/atom?h=1.3_M5</id>
<link rel='self' href='https://git.enea.com/cgit/linux/poky.git/atom?h=1.3_M5'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/'/>
<updated>2012-09-25T12:39:45+00:00</updated>
<entry>
<title>kexec-tools: admit mips as a COMPATIBLE_HOST</title>
<updated>2012-09-25T12:39:45+00:00</updated>
<author>
<name>Phil Blundell</name>
<email>philb@gnu.org</email>
</author>
<published>2012-09-24T11:49:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=0ab08f1539926446c7e3b1b297816af5cbadc3b5'/>
<id>urn:sha1:0ab08f1539926446c7e3b1b297816af5cbadc3b5</id>
<content type='text'>
(From OE-Core rev: 372dc3cf95373225d512160a2ec3e16bf3dc5b8f)

Signed-off-by: Phil Blundell &lt;pb@pbcl.net&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>linux-yocto/3.4: update beagleboard configs</title>
<updated>2012-09-25T09:41:28+00:00</updated>
<author>
<name>Bruce Ashfield</name>
<email>bruce.ashfield@windriver.com</email>
</author>
<published>2012-09-24T20:25:46+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=27874b70f47e0b6493e101319b3b3b580c0e5e99'/>
<id>urn:sha1:27874b70f47e0b6493e101319b3b3b580c0e5e99</id>
<content type='text'>
Updating to pickup a couple of configuration tweaks that were done
as part of a bump to the 3.4 linux-yocto tree for the beagleboard.

In particular, this updates DVI and USB settings to enable the
perhipherals out of the box.

(From OE-Core rev: 3c562b8360edf52aea6280849fa33e8a0f34742b)

Signed-off-by: Liang Li &lt;liang.li@windriver.com&gt;
Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@windriver.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>linux-yocto/3.4: update kver to v3.4.11</title>
<updated>2012-09-25T09:41:28+00:00</updated>
<author>
<name>Bruce Ashfield</name>
<email>bruce.ashfield@windriver.com</email>
</author>
<published>2012-09-24T20:25:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=3e7e0bdad7dabde5189908fbe9003b7a584a07e8'/>
<id>urn:sha1:3e7e0bdad7dabde5189908fbe9003b7a584a07e8</id>
<content type='text'>
Updating the machine and meta SRCREVs to the latest 3.4.x -stable
release.

See git whatchanged v3.4.10..v3.4.11 for the full changelog.

(From OE-Core rev: b164d9776802784a2fee01f2ab267dab4c2beafe)

Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@windriver.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>linux-yocto/3.4: Update fri2 and sys940x to emgd-1.14</title>
<updated>2012-09-24T10:30:32+00:00</updated>
<author>
<name>Bruce Ashfield</name>
<email>bruce.ashfield@windriver.com</email>
</author>
<published>2012-09-24T03:06:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=ae18a5996a13a0068c7ff3494d125ceb8f23bb02'/>
<id>urn:sha1:ae18a5996a13a0068c7ff3494d125ceb8f23bb02</id>
<content type='text'>
Bumping the meta SRCREV to pickup a newer emgd for the fri2 and
sys940x.

(From OE-Core rev: abb23d987184f76fb922af15508f2e251399e3ed)

Signed-off-by: Darren Hart &lt;dvhart@linux.intel.com&gt;
Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@windriver.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>linux-yocto/3.4: use profiling and latencytop features in yocto bsps</title>
<updated>2012-09-21T10:10:24+00:00</updated>
<author>
<name>Bruce Ashfield</name>
<email>bruce.ashfield@windriver.com</email>
</author>
<published>2012-09-20T17:34:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=2c9c9117739e6b9959f37b83a44a66c352d40bfe'/>
<id>urn:sha1:2c9c9117739e6b9959f37b83a44a66c352d40bfe</id>
<content type='text'>
Updating the meta SRCREVs to pickup the following configuration change:

    594994c meta: use profiling and latencytop features in yocto bsps

(From OE-Core rev: df0197810e72337093ea6ced1c8b28eeeef8a7a8)

Signed-off-by: Tom Zanussi &lt;tom.zanussi@intel.com&gt;
Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@windriver.com&gt;
Signed-off-by: Saul Wold &lt;sgw@linux.intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>qemux86-64: Support for KVM, paravirt and virtio added</title>
<updated>2012-09-21T10:10:20+00:00</updated>
<author>
<name>Cristian Iorga</name>
<email>cristian.iorga@intel.com</email>
</author>
<published>2012-09-19T07:06:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=51048acb2d89b260651963ddb9b57c9bd642fc21'/>
<id>urn:sha1:51048acb2d89b260651963ddb9b57c9bd642fc21</id>
<content type='text'>
    KVM, paravirtualization and virtio drivers are now activated
    in runqemu using the kvm option flag for qemux86-64.
    Host CPU features are also exported to guest OS (Yocto Linux).
    Usage example: runqemu qemux86-64 core-image-x11 kvm

    Implements [YOCTO #2550].

(From OE-Core rev: cbb6431b3ee9128ea15c9ae0a19e7d2998ffc561)

Signed-off-by: Cristian Iorga &lt;cristian.iorga@intel.com&gt;
Signed-off-by: Saul Wold &lt;sgw@linux.intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>qemux86: Support for KVM, paravirt and virtio added</title>
<updated>2012-09-21T10:10:19+00:00</updated>
<author>
<name>Cristian Iorga</name>
<email>cristian.iorga@intel.com</email>
</author>
<published>2012-09-19T07:06:54+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=ab2b2a1f2a931258a80ea4e7ed9430aacac591b7'/>
<id>urn:sha1:ab2b2a1f2a931258a80ea4e7ed9430aacac591b7</id>
<content type='text'>
KVM, paravirtualization and virtio drivers are now activated
in runqemu using the kvm option flag for qemux86.
Host CPU features are also exported to guest OS (Yocto Linux).
Usage example: runqemu qemux86 core-image-x11 kvm

Implements [YOCTO #2550].

(From OE-Core rev: a35d03e2eb905de4eadc9c7df5b50bff1fb7f897)

Signed-off-by: Cristian Iorga &lt;cristian.iorga@intel.com&gt;
Signed-off-by: Saul Wold &lt;sgw@linux.intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>linux-yocto/3.4: make uprobes select perf events</title>
<updated>2012-09-14T08:50:31+00:00</updated>
<author>
<name>Bruce Ashfield</name>
<email>bruce.ashfield@windriver.com</email>
</author>
<published>2012-09-14T04:57:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=ffc3b5ded372bdebcb610b7aac91ff56cabeddce'/>
<id>urn:sha1:ffc3b5ded372bdebcb610b7aac91ff56cabeddce</id>
<content type='text'>
uprobes depends on functionality provided by perf events. After
uprobes was enabled in the standard kernel the mpc8315 board showed
link errors due to missing perf event functions.

This problem isn't isolated to the board or powerpc arch, but all
other boards have PERF_EVENTS enabled. To fix this, we make UPROBE_EVENT
select PERF_EVENTS, and any new boards will be protected from the
same failure.

We also update the configuration fragments since CONFIG_UPROBES depends on
CONFIG_PERF_EVENTS being set, so PERF_EVENTS needs to be added whenever
uprobes are enabled.

[YOCTO #3111]

(From OE-Core rev: b681b74624d1c8c4c98b2a121828e010fc5c3a25)

Signed-off-by: Tom Zanussi &lt;tom.zanussi@intel.com&gt;
Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@windriver.com&gt;
Signed-off-by: Saul Wold &lt;sgw@linux.intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>linux-yocto: virtio and KVM guest configuration</title>
<updated>2012-09-14T08:50:30+00:00</updated>
<author>
<name>Bruce Ashfield</name>
<email>bruce.ashfield@windriver.com</email>
</author>
<published>2012-09-13T18:59:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=268177e4e64525a3655094b5a835aee62acea622'/>
<id>urn:sha1:268177e4e64525a3655094b5a835aee62acea622</id>
<content type='text'>
Updating the meta branch SRCREV to pick up virtio and kvm guest
configuration fragments.

  79947f1 meta: add paravirtualized KVM guest config fragment
  3ed86ed meta: add MMIO support in virtio config fragment

(From OE-Core rev: b6b5b501fbe7158f190e887c3edc1214bb3671ed)

Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@windriver.com&gt;
Signed-off-by: Saul Wold &lt;sgw@linux.intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>kernel-yocto: fix kernel configuration audit for custom yocto kernels</title>
<updated>2012-09-14T08:50:29+00:00</updated>
<author>
<name>Bruce Ashfield</name>
<email>bruce.ashfield@windriver.com</email>
</author>
<published>2012-09-13T12:59:08+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=3a6cebbe373f3d02f92210d319f0622482b5841f'/>
<id>urn:sha1:3a6cebbe373f3d02f92210d319f0622482b5841f</id>
<content type='text'>
It was reported that the kernel configuration checks for custom yocto
kernels had the following output:

  NOTE: validating kernel configuration
  grep: /meta-series: No such file or directory
  grep: /meta-series: No such file or directory
  WARNING: Can't find any BSP hardware or required configuration fragments.
  WARNING: Looked at //cfg///hdw_frags.txt and //cfg///required_frags.txt in directory: //cfg//
  NOTE: Tasks Summary: Attempted 375 tasks of which 367 didn't need to be rerun and all succeeded.

which is not inspire confidence in the output of the process.

Completely inhibiting the check is one option to remove the messages,
but that removes the ability see output, which can help move users to
a better or more fully configured linux-yocto based kernel.

To fix this, we have to ensure that the path to the meta-series is
always valid, and that the tools can deal with not all files existing
in the audit directory.

Since custom yocto kernels do not set KMETA (they don't have a meta branch),
we ensure that a default of 'meta' is passed to the audit ('meta' is always
valid), and that kconf_check itself can deal with an incomplete set of
input audit files.

The net result is output like this (using a defconfig with invalid options
for the kernel being built):

  NOTE: validating kernel configuration
  This BSP sets 19 invalid/obsolete kernel options.
  These config options are not offered anywhere within this kernel.
  The full list can be found in your kernel src dir at:
  meta/cfg/standard/qemux86/invalid.cfg

  There were 1 instances of config fragment errors.
  The full list can be found in your kernel src dir at:
  meta/cfg/standard/qemux86/fragment_errors.txt

  The full list can be found in your kernel src dir at:
  meta/cfg/standard/qemux86/missing_required.cfg

(From OE-Core rev: 4d1b7dae063ee4c35c426306d0e22f11ce112c72)

Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@windriver.com&gt;
Signed-off-by: Saul Wold &lt;sgw@linux.intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
</feed>
