Re: linux-yocto 3.0.1 upgrade broke PREFERRED_VERSION setting in BSPs
Bruce Ashfield <bruce.ashfield@...>
On 11-08-17 11:23 PM, Darren Hart wrote:
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.
Cheers,
Bruce
We have just rolled out PREFERRED_VERSION="3.0+git%", and these now failI made this change due to some other explicit requests about the
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.
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.
Cheers,
Bruce