From: Steffen Sledz <sledz@dresearch.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: udev, udev-compat and old kernel
Date: Thu, 03 Mar 2011 13:01:05 +0100 [thread overview]
Message-ID: <4D6F8301.2030605@dresearch.de> (raw)
In-Reply-To: <4D6B9C9D.7080107@dresearch.de>
Am 28.02.2011 14:01, schrieb Steffen Sledz:
> In our local development branch we've set
>
> PREFERRED_VERSION_udev = "141"
>
> in angstrom-2008-preferred-versions.inc to force udev-141 for our old kernel (2.6.24) at hipox machine. But i'm nearly sure that's not the correct way to do this. ;-)
>
> So what's the right way to handle this?
>
> Looking around i found the udev-compat141_141.bb recipe. In my understanding this package adds some rules to newer udev packages (e.g. udev-151) to be able to work with older kernels, so that it is possible to use newer udev versions. Right?
>
> In this case it should be enough to add some lines to conf/machine/hipox.conf, recipes/udev/udev.inc, recipes/udev/udev_{151,154,162,165}.bb similar to poodle machine. Right?
Ping!
It would be helpful if someone could help here to clarify things. The documentation on that is not very clear.
Thx,
Steffen
--
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:sledz@DResearch.de
Fax: +49 30 515932-299
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 130120 B;
Ust.-IDNr. DE273952058
next prev parent reply other threads:[~2011-03-03 12:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-28 13:01 udev, udev-compat and old kernel Steffen Sledz
2011-03-03 12:01 ` Steffen Sledz [this message]
2011-03-03 13:02 ` Richard Purdie
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=4D6F8301.2030605@dresearch.de \
--to=sledz@dresearch.de \
--cc=openembedded-devel@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