All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <koen@dominion.thruhere.net>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/5] udev-172: add a newer version for newer kernel
Date: Wed, 13 Jul 2011 08:59:38 +0200	[thread overview]
Message-ID: <C30E8605-35B6-48C5-B6DA-D4F7D1C64759@dominion.thruhere.net> (raw)
In-Reply-To: <B49A8790-9DF0-4DAA-A95A-EC2E9F854CCB@gmail.com>


Op 13 jul 2011, om 08:22 heeft Khem Raj het volgende geschreven:

> 
> 
> On Jul 12, 2011, at 12:02 PM, nitin.a.kamble@intel.com wrote:
> 
>> From: Nitin A Kamble <nitin.a.kamble@intel.com>
>> 
>> the 2.6.38 kernel has dropped v4lv1 support. and udev-168 fails to
>> compile because of that. So add a newer 172 version of udev to work with
>> 2.6.38 kernel.
>> 
>> Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
>> ---
>> meta/recipes-core/udev/udev-172/init              |   59 +++++++++
>> meta/recipes-core/udev/udev-172/local.rules       |   35 ++++++
>> meta/recipes-core/udev/udev-172/permissions.rules |  131 +++++++++++++++++++++
>> meta/recipes-core/udev/udev-172/run.rules         |   14 +++
>> meta/recipes-core/udev/udev-172/udev.rules        |  116 ++++++++++++++++++
>> meta/recipes-core/udev/udev_172.bb                |    6 +
>> 6 files changed, 361 insertions(+), 0 deletions(-)
>> create mode 100644 meta/recipes-core/udev/udev-172/init
>> create mode 100644 meta/recipes-core/udev/udev-172/local.rules
>> create mode 100644 meta/recipes-core/udev/udev-172/permissions.rules
>> create mode 100644 meta/recipes-core/udev/udev-172/run.rules
>> create mode 100644 meta/recipes-core/udev/udev-172/udev.rules
>> create mode 100644 meta/recipes-core/udev/udev_172.bb
> 
> Meta-oe ha 171 it would be nice if you could look inti it and incorporate any differences into 172
> Then we can retire 171 from meta-oe

Meta-oe has had 172 since yesterday :) The main difference between the oe-core and meta-oe version is that the meta-oe version has removed a lot of udev rules that weren't needed and made booting slow. Where udev trigger used to take >8 seconds I can now boot X in less than a second on a cortex A9.

regards,

Koen


  reply	other threads:[~2011-07-13  7:03 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-12 19:02 [PATCH 0/5] commits for yocto.git tree for x32 work nitin.a.kamble
2011-07-12 19:02 ` [PATCH 1/5] siteinfo.bbclass: hack for x32 nitin.a.kamble
2011-07-13  6:20   ` Khem Raj
2011-07-13 15:41     ` Kamble, Nitin A
2011-07-14 19:49       ` Khem Raj
2011-07-12 19:02 ` [PATCH 2/5] udev-172: add a newer version for newer kernel nitin.a.kamble
2011-07-13  6:22   ` Khem Raj
2011-07-13  6:59     ` Koen Kooi [this message]
2011-07-13 15:43       ` Kamble, Nitin A
2011-07-12 19:02 ` [PATCH 3/5] runqemu: support qemux32 machine nitin.a.kamble
2011-07-13  1:35   ` Bruce Ashfield
2011-07-12 19:02 ` [PATCH 4/5] kernel.bbclass: fix the broken lines nitin.a.kamble
2011-07-13 11:16   ` Richard Purdie
2011-07-12 19:02 ` [PATCH 5/5] glibc: fix false failure nitin.a.kamble
2011-07-13 11:16   ` Richard Purdie
2011-07-13 11:20 ` [PATCH 0/5] commits for yocto.git tree for x32 work Richard Purdie
2011-07-13 14:14   ` Tom Rini
2011-07-13 14:38   ` Khem Raj

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=C30E8605-35B6-48C5-B6DA-D4F7D1C64759@dominion.thruhere.net \
    --to=koen@dominion.thruhere.net \
    --cc=openembedded-core@lists.openembedded.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.