From: Saul Wold <saul.wold@intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] udev-164: Update init script to do an explicit add action
Date: Mon, 07 Nov 2011 09:51:19 -0800 [thread overview]
Message-ID: <4EB81A97.6070703@intel.com> (raw)
In-Reply-To: <1320218594-13009-1-git-send-email-galak@kernel.crashing.org>
On 11/02/2011 12:23 AM, Kumar Gala wrote:
> With udev 152 or greater the default action for 'udevadm trigger' was
> modified to be 'change' instead of 'add.
>
> To ensure initial coldplug events at boot are seen be scripts the are
> expecting them as 'add' events we invoke udevadm with an explicit
> '--action=add'.
>
> Signed-off-by: Kumar Gala<galak@kernel.crashing.org>
> ---
> meta/recipes-core/udev/udev-164/init | 4 ++--
> meta/recipes-core/udev/udev_164.bb | 2 +-
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/meta/recipes-core/udev/udev-164/init b/meta/recipes-core/udev/udev-164/init
> index 9ce95ee..073942f 100644
> --- a/meta/recipes-core/udev/udev-164/init
> +++ b/meta/recipes-core/udev/udev-164/init
> @@ -48,10 +48,10 @@ kill_udevd> "/dev/null" 2>&1
>
> /sbin/udevadm control --env=STARTUP=1
> if [ "$not_first_boot" != "" ];then
> - /sbin/udevadm trigger --subsystem-nomatch=tty --subsystem-nomatch=mem --subsystem-nomatch=vc --subsystem-nomatch=vtconsole --subsystem-nomatch=misc --subsystem-nomatch=dcon --subsystem-nomatch=pci_bus --subsystem-nomatch=graphics --subsystem-nomatch=backlight --subsystem-nomatch=video4linux --subsystem-nomatch=platform
> + /sbin/udevadm trigger --action=add --subsystem-nomatch=tty --subsystem-nomatch=mem --subsystem-nomatch=vc --subsystem-nomatch=vtconsole --subsystem-nomatch=misc --subsystem-nomatch=dcon --subsystem-nomatch=pci_bus --subsystem-nomatch=graphics --subsystem-nomatch=backlight --subsystem-nomatch=video4linux --subsystem-nomatch=platform
> (/sbin/udevadm settle --timeout=3; /sbin/udevadm control --env=STARTUP=)&
> else
> - /sbin/udevadm trigger
> + /sbin/udevadm trigger --action=add
> /sbin/udevadm settle
> fi
>
> diff --git a/meta/recipes-core/udev/udev_164.bb b/meta/recipes-core/udev/udev_164.bb
> index 7cbe4d8..d487add 100644
> --- a/meta/recipes-core/udev/udev_164.bb
> +++ b/meta/recipes-core/udev/udev_164.bb
> @@ -1,6 +1,6 @@
> include udev-new.inc
>
> -PR = "r6"
> +PR = "r7"
>
> SRC_URI += "file://udev-166-v4l1-1.patch"
>
Merged into OE-Core
Thanks
Sau!
prev parent reply other threads:[~2011-11-07 17:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-02 7:23 [PATCH] udev-164: Update init script to do an explicit add action Kumar Gala
2011-11-07 17:51 ` Saul Wold [this message]
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=4EB81A97.6070703@intel.com \
--to=saul.wold@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox