From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: [RFC] fix for MACHINE_KERNEL_PR stuff
Date: Wed, 03 Jun 2009 13:45:24 +0200 [thread overview]
Message-ID: <h05nok$s93$1@ger.gmane.org> (raw)
In-Reply-To: <200906031325.48159.marcin@juszkiewicz.com.pl>
On 03-06-09 13:25, Marcin Juszkiewicz wrote:
>
> This patch unbreaks current behaviour which was introduced by
> MACHINE_KERNEL_PR variable.
>
> As most of target machines do not use it they have PR with broken value
> (set to "r0" instead of value in recipe). I took other way which makes
> both types of users happy -- those with MACHINE_KERNEL_PR in use and
> those without it.
>
> By default we set M_K_PR to empty string instead of "r0" - this allows
> to check is it set at all or not. If it is set then we set PR to this value.
> Otherwise we ignore existance of that variable and use PR from recipe.
>
> Please test and review it. If this will work I will request it for stable/2009.
>
> Signed-off-by: Marcin Juszkiewicz<marcin@juszkiewicz.com.pl>
>
> diff --git a/classes/kernel.bbclass b/classes/kernel.bbclass
> index 1323228..757b704 100644
> --- a/classes/kernel.bbclass
> +++ b/classes/kernel.bbclass
> @@ -20,6 +20,12 @@ python __anonymous () {
> image = bb.data.getVar('INITRAMFS_IMAGE', d, True)
> if image != '' and image is not None:
> bb.data.setVar('INITRAMFS_TASK', '${INITRAMFS_IMAGE}:do_rootfs', d)
> +
> + pr = bb.data.getVar('PR', d, True)
You're not using 'pr' anywhere in the code you add. Looks fine
otherwise, although I haven't tested it.
regards,
Koen
next prev parent reply other threads:[~2009-06-03 11:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-03 11:25 [RFC] fix for MACHINE_KERNEL_PR stuff Marcin Juszkiewicz
2009-06-03 11:45 ` Koen Kooi [this message]
2009-06-03 11:59 ` Marcin Juszkiewicz
2009-06-08 17:51 ` Koen Kooi
2009-06-03 12:32 ` Phil Blundell
2009-06-08 15:54 ` Marcin Juszkiewicz
2009-06-09 4:05 ` Rolf Leggewie
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='h05nok$s93$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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.