From: Eric Nelson <eric.nelson@boundarydevices.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: "meta-freescale@yoctoproject.org"
<meta-freescale@yoctoproject.org>, Diego <diego.ml@zoho.com>,
Post Lauren-RAA013 <RAA013@freescale.com>
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:56:22 -0700 [thread overview]
Message-ID: <524C5036.5060303@boundarydevices.com> (raw)
In-Reply-To: <524C49BD.3090602@boundarydevices.com>
On 10/02/2013 09:28 AM, Eric Nelson wrote:
> Thanks Otavio,
> On 10/02/2013 08:11 AM, Otavio Salvador wrote:
>
>> On Wed, Oct 2, 2013 at 11:51 AM, Eric Nelson
>>> What's more, I think it's very important for different boards to be
>>> able to specify which kernel version is recommended for each, since
>>> the efforts behind them progress along different time-lines.
>>
>> Yes; this can be done. We does it already and Bondary's boards also
>> use a different kernel.
>>
>
> Kernel, yes.
>
> But at the moment, there's no way for a board/kernel to select
> the revision of binaries, right?
> https://github.com/Freescale/meta-fsl-arm/blob/dora/recipes-multimedia/libfslvpuwrap/libfslvpuwrap_1.0.38.bb
>
> Or can we, for instance, have two recipes for the components,
> e.g.
> gpu-viv-bin-mx6q_3.5.7-1.0.0-alpha.2-hfp.bb
> gpu-viv-bin-mx6q_3.10.9-1.0.0-alpha-hfp.bb
>
> and express PREFERRED_VERSION_gpu-viv-bin-mx6q=3.5.7-1.0.0-alpha.2
> in the linux-boundary_3.0.35.bb recipe and then set
> PREFERRED_VERSION_gpu-viv-bin-mx6q=3.10.9-1.0.0-alpha.2 in a
> linux-boundary_3.10.9.bb recipe?
Based on Lauren's comments that the 3.10.9 binaries are ABI-compatible
with the 3.0.35_4.1.0 release, and to allow testing of things,
perhaps this is more appropriate:
PREFERRED_VERSION_blah ?= 3.10.9-1.0.0-alpha
Regards,
Eric
next prev parent reply other threads:[~2013-10-02 16:56 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
2013-10-02 16:28 ` Eric Nelson
2013-10-02 16:56 ` Eric Nelson [this message]
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=524C5036.5060303@boundarydevices.com \
--to=eric.nelson@boundarydevices.com \
--cc=RAA013@freescale.com \
--cc=diego.ml@zoho.com \
--cc=meta-freescale@yoctoproject.org \
--cc=otavio@ossystems.com.br \
/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.