From: Daiane Angolini <daiane.angolini@freescale.com>
To: "randy.krakora@freescale.com" <randy.krakora@freescale.com>,
'Fabio Estevam' <festevam@gmail.com>
Cc: "'meta-freescale@yoctoproject.org'" <meta-freescale@yoctoproject.org>
Subject: Re: 3.5.7 kernel?
Date: Wed, 15 Jan 2014 11:01:26 -0200 [thread overview]
Message-ID: <52D686A6.2010203@freescale.com> (raw)
In-Reply-To: <7be4f3c42f0e466a959ec36c331f0849@BLUPR03MB392.namprd03.prod.outlook.com>
On 15-01-2014 00:10, randy.krakora@freescale.com wrote:
> Fabio,
>
> The project was started with 3.0.35 ltib in parallel with 3.5.7 Yocto, most of the work is done in 3.0.35, and we planned to move the updates to 3.5.7 Yocto as an interim step, then to 3.10.x. Only using 3.5.7, because some of the development is done there and the project timing may be jeopardized for starting again at 3.10 this soon. I know we did talk about moving straight to 3.10.x before Christmas, but I'm not sure the final decision here, I just want to make sure we can get 3.5.7 if we need to.
http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-arm/commit/recipes-kernel/linux?h=dora&id=068a234a1699046c8e7ad59b1566d0293b6dd5c8
if you really need that kernel, take a look in older commit
http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-arm/commit/recipes-kernel/linux?h=dora&id=068a234a1699046c8e7ad59b1566d0293b6dd5c8
You can create your own recipe/layer and have it.
Or use the layer Lauren suggested.
Daiane
>
> -Randy
>
> -----Original Message-----
> From: Fabio Estevam [mailto:festevam@gmail.com]
> Sent: Tuesday, January 14, 2014 4:04 PM
> To: Krakora Randy-B37740
> Cc: meta-freescale@yoctoproject.org
> Subject: Re: [meta-freescale] 3.5.7 kernel?
>
> On Tue, Jan 14, 2014 at 5:55 PM, Ra37740@freescale.comndy <b37740@freescale.com> wrote:
>> Hello,
>>
>> I'm trying to build the 3.5.7 kernel in Dylan branch - modifying
>> local.conf as this:
>>
>> MACHINE ??= 'imx6qsabresd'
>> ...
>> PREFERRED_VERSION_linux-imx_mx6="3.5.7"
>>
>> but seeing this when I build:
>>
>> NOTE: preferred version 3.5.7 of linux-imx not available (for item
>> linux-imx)
>> NOTE: versions of linux-imx available: 3.0.35
>> NOTE: Resolving any missing task queue dependencies
>> NOTE: preferred version 3.5.7 of linux-imx not available (for item
>> kernel-base)
>> NOTE: versions of linux-imx available: 3.0.35
>> NOTE: preferred version 3.5.7 of linux-imx not available (for item
>> kernel-image)
>> NOTE: versions of linux-imx available: 3.0.35
>> NOTE: Preparing runqueue
>> NOTE: Tainting hash to force rebuild of task
>> /home/randy/fsl-community-bsp/sources/meta-fsl-arm/recipes-kernel/linu
>> x/linux-imx_3.0.35.bb,
>> do_compile
>>
>> Is 3.5.7 no longer an option for linux-imx?
>
> Can't you use 3.10 instead?
>
> Regards,
>
> Fabio Estevam
>
>
> _______________________________________________
> meta-freescale mailing list
> meta-freescale@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale
>
>
--
Daiane
next prev parent reply other threads:[~2014-01-15 13:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-14 19:55 3.5.7 kernel? Ra37740@freescale.comndy
2014-01-14 20:30 ` Lauren Post
2014-01-14 21:04 ` Fabio Estevam
2014-01-15 2:10 ` randy.krakora
2014-01-15 13:01 ` Daiane Angolini [this message]
2014-01-15 13:12 ` Otavio Salvador
2014-01-15 1:34 ` Otavio Salvador
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=52D686A6.2010203@freescale.com \
--to=daiane.angolini@freescale.com \
--cc=festevam@gmail.com \
--cc=meta-freescale@yoctoproject.org \
--cc=randy.krakora@freescale.com \
/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.