[for-danny][RFT] Danny bugfixes/improvements from master

[for-danny][RFT] Danny bugfixes/improvements from master

[Otavio Salvador]

Hello,

I've prepared a branch with the patches I think we could apply to "danny".

Daiane Angolini (6):
      imx-lib: Update to version 1.1.0
      imx-test: Update to version 1.1.0
      firmware-imx: Update to version 1.1.0
      libfslcodec: Update to version 3.0.5
      libfslparser: Update to version 3.0.5
      gst-fsl-plugin: Update to version 3.0.5

Eric BENARD (2):
      xf86-dri-vivante: fix licence chekcsum
      xf86-video-imxfb-vivante: fix missing headers

Eric Bénard (2):
      xf86-video-imxfb: fix build error due to missing uint declaration
      gst-fsl-plugin-2.0.3: fix build error due to missing uint declaration

Eric Nelson (1):
      linux-imx (3.0.35): Synchronize Boundary Devices changes

Jeremy Stashluk (1):
      gpu-viv-bin-mx6q: fix gc_vdk_types include path

Leonardo Sandoval (4):
      qt4: Add a unreference instruction on qt4 phonon patch
      imx-test: Add script to print system clocks
      imx-test: Condition the mxc_epdc_x11_fb_test installation
      gst-fsl-plugin: Include the Real-Time Extension lib into mfw_v4lsrc

Otavio Salvador (10):
      linux-linaro: Remove recipes as it is not active upstream
      linux-imx (3.0.35): Upgrade to 1.1.0 BSP release
      gst-fsl-plugin (3.0.5): Fix build failure due missing 'uint' definition
      linux-fslc: Update to 3.7.5 based kernel
      u-boot-fslc: Update to 2013.01-rc3
      u-boot-mxsboot: Update to 2013.01
      u-boot: Update to 2013.01 release
      u-boot-fslc: Update GIT revision for 20130207 snapshot
      u-boot-imx: Add imx6qsabresd support
      u-boot-imx (mx6): Update to 1.1.0 BSP version

Those are all available at 'danny-next' branch and it fixes many
issues found since the branching and also does upgrade some BSP
packages to 1.1.0.

Please give it a good test and comment if you think something should
be added or dropped.

Regards,

--
Otavio Salvador                             O.S. Systems
E-mail: otavio@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br

Re: [for-danny][RFT] Danny bugfixes/improvements from master

[Eric Bénard]

Hi Otavio,

Le Sat, 16 Feb 2013 16:41:34 -0200,
Otavio Salvador <otavio@ossystems.com.br> a écrit :
> Those are all available at 'danny-next' branch and it fixes many
> issues found since the branching and also does upgrade some BSP
> packages to 1.1.0.
> 
please don't remove 12.09.01 recipes in danny : this is a stable
release so please don't break users' layers which could have bbappend
on the actual recipes.
The goal of a release branch is to make a snapshot of what is stable
at the day of the release and then to get only fixes, not to track
everything which goes into master.

Thanks
Eric

Re: [for-danny][RFT] Danny bugfixes/improvements from master

[Otavio Salvador]

On Sat, Feb 16, 2013 at 6:20 PM, Eric Bénard <eric@eukrea.com> wrote:
> Hi Otavio,
>
> Le Sat, 16 Feb 2013 16:41:34 -0200,
> Otavio Salvador <otavio@ossystems.com.br> a écrit :
>> Those are all available at 'danny-next' branch and it fixes many
>> issues found since the branching and also does upgrade some BSP
>> packages to 1.1.0.
>>
> please don't remove 12.09.01 recipes in danny : this is a stable
> release so please don't break users' layers which could have bbappend
> on the actual recipes.
> The goal of a release branch is to make a snapshot of what is stable
> at the day of the release and then to get only fixes, not to track
> everything which goes into master.

Part of me agrees with you; part does not.

I agree that the upgrade to 1.1.0 might break some users BSP at same
time the BSP has been upgraded by Freescale due they've fixed known
issues and those might be important to customers. So we have a
dead-lock here :-)

For me, I am fine in picking just the recipes bugfixes and putting
those into danny my bigger concern here is what people really want
from danny branch. So could someone else comment on this?

-- 
Otavio Salvador                             O.S. Systems
E-mail: otavio@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br

Re: [for-danny][RFT] Danny bugfixes/improvements from master

[Eric Bénard]

Hi Otavio,

Le Sat, 16 Feb 2013 18:46:55 -0200,
Otavio Salvador <otavio@ossystems.com.br> a écrit :
> On Sat, Feb 16, 2013 at 6:20 PM, Eric Bénard <eric@eukrea.com> wrote:
> > Le Sat, 16 Feb 2013 16:41:34 -0200,
> > Otavio Salvador <otavio@ossystems.com.br> a écrit :
> >> Those are all available at 'danny-next' branch and it fixes many
> >> issues found since the branching and also does upgrade some BSP
> >> packages to 1.1.0.
> >>
> > please don't remove 12.09.01 recipes in danny : this is a stable
> > release so please don't break users' layers which could have bbappend
> > on the actual recipes.
> > The goal of a release branch is to make a snapshot of what is stable
> > at the day of the release and then to get only fixes, not to track
> > everything which goes into master.
> 
> Part of me agrees with you; part does not.
> 
> I agree that the upgrade to 1.1.0 might break some users BSP at same
> time the BSP has been upgraded by Freescale due they've fixed known
> issues and those might be important to customers. So we have a
> dead-lock here :-)
> 
problem is that this will break any bbappend and any patch peoples may
have in their layers for their custom boards which are based on danny
and so on 12.09.01.

IMHO, a stable branch is the snapshot of versions which are considered
to be stable at the date of the release. During the stable branch's
life, if updates or bug fixes are available for the versions _already_
in the stable branch you can of course apply them to the stable branch.
12.09.01 was considered to be stable at the time of the danny release
and allows to generate a working configuration for i.MX6 when 1.1.0
was released after danny was created as a stable branch and thus is the
right BSP to use for the _next_ stable branch.

If a stable branch is a branch which can get all the upgrades from
master whenever a BSP is upgraded, then you will always have good
reason to pick up any patch from master so a stable branch is not
necessary and it is better to say to users : we are a moving target, if
you want stability, stick to a commit hash and not to a branch (or
create your own branch based on master and cherry-pick the patches you
want).
Of course you can argue there may not be many users of the stable
branch (and certainly even less with i.MX6 boards), but you already
thought that at the time of denzil and that broke at least 2 i.MX53 BSP
I maintain for 2 different customers which were based on denzil so yes,
there can be some users of the stable branches of meta-fsl-arm.
If you merge 1.1.0 in danny, the problem is the message you send to
users : you need to warn people that meta-fsl-arm's stable branches can
receive major upgrades and thus break their own layers so that users
can take their responsibility and choose either to work on a fixed
commit hash or to fork meta-fsl-arm for their own project.

If you do a git diff master danny-next you will see there is nearly no
reason to have 2 branches ;-)

Eric

Re: [for-danny][RFT] Danny bugfixes/improvements from master

[Otavio Salvador]

On Sun, Feb 17, 2013 at 5:21 PM, Eric Bénard <eric@eukrea.com> wrote:
> Hi Otavio,
>
> Le Sat, 16 Feb 2013 18:46:55 -0200,
> Otavio Salvador <otavio@ossystems.com.br> a écrit :
>> On Sat, Feb 16, 2013 at 6:20 PM, Eric Bénard <eric@eukrea.com> wrote:
>> > Le Sat, 16 Feb 2013 16:41:34 -0200,
>> > Otavio Salvador <otavio@ossystems.com.br> a écrit :
>> >> Those are all available at 'danny-next' branch and it fixes many
>> >> issues found since the branching and also does upgrade some BSP
>> >> packages to 1.1.0.
>> >>
>> > please don't remove 12.09.01 recipes in danny : this is a stable
>> > release so please don't break users' layers which could have bbappend
>> > on the actual recipes.
>> > The goal of a release branch is to make a snapshot of what is stable
>> > at the day of the release and then to get only fixes, not to track
>> > everything which goes into master.
>>
>> Part of me agrees with you; part does not.
>>
>> I agree that the upgrade to 1.1.0 might break some users BSP at same
>> time the BSP has been upgraded by Freescale due they've fixed known
>> issues and those might be important to customers. So we have a
>> dead-lock here :-)
>>
> problem is that this will break any bbappend and any patch peoples may
> have in their layers for their custom boards which are based on danny
> and so on 12.09.01.
>
> IMHO, a stable branch is the snapshot of versions which are considered
> to be stable at the date of the release. During the stable branch's
> life, if updates or bug fixes are available for the versions _already_
> in the stable branch you can of course apply them to the stable branch.
> 12.09.01 was considered to be stable at the time of the danny release
> and allows to generate a working configuration for i.MX6 when 1.1.0
> was released after danny was created as a stable branch and thus is the
> right BSP to use for the _next_ stable branch.
>
> If a stable branch is a branch which can get all the upgrades from
> master whenever a BSP is upgraded, then you will always have good
> reason to pick up any patch from master so a stable branch is not
> necessary and it is better to say to users : we are a moving target, if
> you want stability, stick to a commit hash and not to a branch (or
> create your own branch based on master and cherry-pick the patches you
> want).
> Of course you can argue there may not be many users of the stable
> branch (and certainly even less with i.MX6 boards), but you already
> thought that at the time of denzil and that broke at least 2 i.MX53 BSP
> I maintain for 2 different customers which were based on denzil so yes,
> there can be some users of the stable branches of meta-fsl-arm.
> If you merge 1.1.0 in danny, the problem is the message you send to
> users : you need to warn people that meta-fsl-arm's stable branches can
> receive major upgrades and thus break their own layers so that users
> can take their responsibility and choose either to work on a fixed
> commit hash or to fork meta-fsl-arm for their own project.
>
> If you do a git diff master danny-next you will see there is nearly no
> reason to have 2 branches ;-)

Ok; I agree with you.

I will redo danny-next and send a new e-mail so people can check its contents.

-- 
Otavio Salvador                             O.S. Systems
E-mail: otavio@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br

[for-danny][RFT] Danny bugfixes/improvements from master

[Otavio Salvador]

Hello,

I've prepared a branch with the patches I think we could apply to "danny".

Eric BENARD (2):
      xf86-dri-vivante: fix licence chekcsum
      xf86-video-imxfb-vivante: fix missing headers

Eric Nelson (1):
      linux-imx (3.0.35): Synchronize Boundary Devices changes

Jeremy Stashluk (1):
      gpu-viv-bin-mx6q: fix gc_vdk_types include path

Leonardo Sandoval (3):
      qt4: Add a unreference instruction on qt4 phonon patch
      imx-test: Add script to print system clocks
      imx-test: Condition the mxc_epdc_x11_fb_test installation

Otavio Salvador (2):
      linux-fslc: Update to 3.7.5 based kernel
      u-boot-imx: Add imx6qsabresd support

Those are all available at 'danny-next' branch and it fixes many
issues found since the branching.

Please give it a good test and comment if you think something should
be added or dropped.

Regards,

--
Otavio Salvador                             O.S. Systems
E-mail: otavio@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br

Re: [for-danny][RFT] Danny bugfixes/improvements from master

[Otavio Salvador]

On Wed, Feb 20, 2013 at 9:09 AM, Otavio Salvador
<otavio@ossystems.com.br> wrote:
> Hello,
>
> I've prepared a branch with the patches I think we could apply to "danny".
>
> Eric BENARD (2):
>       xf86-dri-vivante: fix licence chekcsum
>       xf86-video-imxfb-vivante: fix missing headers
>
> Eric Nelson (1):
>       linux-imx (3.0.35): Synchronize Boundary Devices changes
>
> Jeremy Stashluk (1):
>       gpu-viv-bin-mx6q: fix gc_vdk_types include path
>
> Leonardo Sandoval (3):
>       qt4: Add a unreference instruction on qt4 phonon patch
>       imx-test: Add script to print system clocks
>       imx-test: Condition the mxc_epdc_x11_fb_test installation
>
> Otavio Salvador (2):
>       linux-fslc: Update to 3.7.5 based kernel
>       u-boot-imx: Add imx6qsabresd support
>
> Those are all available at 'danny-next' branch and it fixes many
> issues found since the branching.
>
> Please give it a good test and comment if you think something should
> be added or dropped.

Merged onto danny branch.

-- 
Otavio Salvador                             O.S. Systems
E-mail: otavio@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br