From: Eric Nelson <eric.nelson@boundarydevices.com>
To: Post Lauren-RAA013 <RAA013@freescale.com>,
"meta-freescale@yoctoproject.org"
<meta-freescale@yoctoproject.org>
Subject: Re: Request to integrate freescale i.mx 3.10.9-1.0.0 alpha release into dora branch of meta-fsl-arm
Date: Wed, 02 Oct 2013 09:51:23 -0700 [thread overview]
Message-ID: <524C4F0B.9070604@boundarydevices.com> (raw)
In-Reply-To: <2BC32295742BF14CA5950C3659567EB677A6A5@039-SN1MPN1-003.039d.mgd.msft.net>
Thanks Lauren,
These details are very helpful.
On 10/02/2013 08:41 AM, Post Lauren-RAA013 wrote:
> 3.10.9 will be a GA kernel by early next year.
>
> 3.5.7-alpha2 is just graphics package (fixes beyond 3.0.35-4.1.0
> based on p12 version)
>
And Device-tree support... This clearly made major strides leading to
3.10 and main-line.
> 3.10.9-1.0.0_alpha graphics is still p12 based with additional fixes
> beyond 3.5.7-alpha2 so it should replace 3.5.7-alpha2.
Thanks again. We should be able to examine the changes and
look for ABI-compatibility.
> 3.10.9 also provides full Weston-wayland support.
>
> We understand that 3.0.35-4.1.0 is the current GA current and is preferred
> by those wanting a stable kernel. Just note that the non-kernel
> packages are pretty close to the 3.0.35-4.1.0 release that just
> came out in August so I'm not that worried about stability.
>
Stability hasn't been an issue with our testing of 3.5.7, but
there were significant gaps for things like PCIe, cameras, and
such (at least for us).
> I built with community 3.0.35 and community uboot 2013.10 and
> had no problems with non-kernel 3.10.9 components.
>
> Unfortunately we don't have test resources to test 3.0.35-4.1.0
> with 3.10.9-1.0.0 non-kernel components but my sanity test showed
> it worked. Imx-test requires one update for a header name change
> between the kernels that I've sent to Otavio.
>
We should be able to help here. After all, "community" is a two-way
street, right?
> The 3.10.9 release has all the imx6 boards including imx6 solo
> lite and it went through a full test cycle for our alpha release
> (and will go through more test cycles for beta and ga).
>
> The goal is to get this integrated so that our GA 3.10.9 kernel
> will be on a stable yocto branch.
>
> Our future 3.10.9 beta and GA will be based on the dora branch
> not the master branch.
>
> Our other option is just release on our release layer
> meta-fsl-bsp-release and that is normally our plan but since
> dora is just coming out we asked for an exception for this
> time since our GA will be complete far before Yocto 1.6 is available.
>
Sounds good to me.
Regards,
Eric
next prev parent reply other threads:[~2013-10-02 16:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-01 16:34 Request to integrate freescale i.mx 3.10.9-1.0.0 alpha release into dora branch of meta-fsl-arm Post Lauren-RAA013
2013-10-02 13:06 ` Diego
2013-10-02 13:55 ` Otavio Salvador
2013-10-02 13:56 ` Daiane Angolini
2013-10-02 14:51 ` Eric Nelson
2013-10-02 15:11 ` Otavio Salvador
2013-10-02 15:41 ` Post Lauren-RAA013
2013-10-02 16:51 ` Eric Nelson [this message]
2013-10-02 16:28 ` Eric Nelson
2013-10-02 16:56 ` Eric Nelson
2013-10-02 18:40 ` Post Lauren-RAA013
2013-10-22 13:09 ` Gonzalez, Alex
2013-10-02 14:01 ` John Weber
2013-10-02 14:24 ` Eric Nelson
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=524C4F0B.9070604@boundarydevices.com \
--to=eric.nelson@boundarydevices.com \
--cc=RAA013@freescale.com \
--cc=meta-freescale@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.