All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Darren Hart <dvhart@linux.intel.com>
Cc: Yocto Project <yocto@yoctoproject.org>
Subject: Re: linux-yocto 3.0.1 upgrade broke PREFERRED_VERSION setting in BSPs
Date: Thu, 18 Aug 2011 00:40:19 -0400	[thread overview]
Message-ID: <4E4C97B3.1060308@windriver.com> (raw)
In-Reply-To: <4E4C90F2.7040904@windriver.com>

On 11-08-18 12:11 AM, Bruce Ashfield wrote:
> On 11-08-17 11:23 PM, Darren Hart wrote:
>> We have just rolled out PREFERRED_VERSION="3.0+git%", and these now fail
>> with messages like:
>>
>> NOTE: preferred version 3.0+git% of linux-yocto not available (for item
>> virtual/kernel)
>>
>> I could patch everything really quick to use 3.0.1+git%... but 3.0.2 was
>> just released and I'd have to do it again tomorrow. For 2.6.37, the
>> LINUX_VERSION remained the same across point releases. I recommend we do
>> the same for 3.0. I really don't want to have to go through and update
>> all the PREFERRED_VERSIONs in addition to all the SRCREVs everytime a
>> point release comes out.
>
> I made this change due to some other explicit requests about the
> kernel version not being obvious. I don't really see this as a big
> deal, I'm already updating SRCREVs, we are already updating the
> SRCREVs in the meta-* layers .. so I fail to see how this is much
> more load.
>
> I'd argue that 2.6.37 was a mistake, and you shouldn't even need
> to set the preferred version anymore once the latest kernel works
> for your machines. It will always be selected and you shouldn't
> need to force it. We only needed this during the transition phase,
> and I'm about to change the default in meta-yocto .. so you definitely
> won't need it.

Another thought on this is that we follow up on the discussion that
we had when I first had to force some boards back to 2.6.37. We drop
all the preferred version manipulations and control this via
DEFAULT_PREFERENCE.

I can just set DEFAULT_PREFERENCE = -1 in the linux-yocto_<ver>.bb
file, and as machines are tested/validated, they'll just set
the DEFAULT_PREFERENCE_$MACHINE in their recipe/bbappend file. That
saves us all the PREFERRED version fun.

Alternatively, we go back to just setting it to 3.0 and leaving it
there and those folks that don't want to check the tags in the kernel
I can put a comment in the recipe that lets them know the true
version.

Cheers,

Bruce

>
> Cheers,
>
> Bruce
>
>>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto



  reply	other threads:[~2011-08-18  4:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-18  3:23 linux-yocto 3.0.1 upgrade broke PREFERRED_VERSION setting in BSPs Darren Hart
2011-08-18  4:11 ` Bruce Ashfield
2011-08-18  4:40   ` Bruce Ashfield [this message]
2011-08-18  5:31     ` Darren Hart
2011-08-18 13:33       ` Bruce Ashfield
2011-08-18 13:43         ` Martin Jansa
2011-08-18 13:02   ` Tom Zanussi
2011-08-18 13:40     ` Bruce Ashfield
2011-08-19  6:00 ` Khem Raj
2011-08-21  4:41   ` Bruce Ashfield

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=4E4C97B3.1060308@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=dvhart@linux.intel.com \
    --cc=yocto@yoctoproject.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.