Skip to contentSkip to conversation

meta-intel candidate branch for 1.1 edison point release

DISCUSSION Tom Zanussi 2 participants 3 messages Nov 2, 2011

lore
Share & tools
lore
#0 lore raw

Hi,

I've created a new meta-intel/edison-next branch to hold commits intended for the upcoming 1.1 point release.

I'll be collecting candidate commits for a 1.1 point release there until it's time to cut the 1.1 point release, and will pull those into edison proper at that point, assuming we have agreement on the set of patches in the branch.

Please let me know if you have any comments on this set or if you know of any missing patches that should be added.

Thanks,

Tom

Here's the current set of commit descriptions for the commits in that branch:

commit 59292a744ad1ea7875c0f2b7564c4ad74af2d68e

Author: Tom Zanussi <[email protected]>
Date:   Fri Oct 28 11:26:22 2011 -0500

meta-crownbay: allow linux-yocto-rt to be used for crownbay

The crownbay linux-yocto-rt .bbappend is missing settings needed for use with crownbay - this adds them.

commit 3d78b56773943803f46c09f69e908506fff95b04

Author: Tom Zanussi <[email protected]>
Date:   Thu Oct 27 23:48:15 2011 -0500

meta-fri2: allow linux-yocto-rt to be used for fri2-noemgd

The fri2 linux-yocto-rt .bbappend is missing settings needed for use with fri2-noemgd - this adds them.

commit 9b901b4df24c88795e2a188e070249ef5273a8e9

Author: Tom Zanussi <[email protected]>
Date:   Thu Oct 27 17:37:27 2011 -0500

meta-crownbay: add linux-yocto-rt_3.0.bbappend

commit 061f3187e8cbec70d5970928b6e8252cb0958f4a (meta-intel: move emgd-driver-bin_1.8 to common) somehow mistakenly removed the unrelated linux-yocto-rt_3.0.bbappend from meta-crownbay. This adds it back.

commit cc0a4df25eb1db45698574d781c13fd7ee2ddaa7

Author: Tom Zanussi <[email protected]>
Date:   Thu Oct 20 17:03:13 2011 -0500

meta-fri2: README correction

In the instructions for manually extracting the binaries from the EMGD Linux tarball, an additional step for removing the emgd_drv_video shared library is necessary; this adds it for fri2.

commit b8f9910a39196bdbce37dea25f82538b144d72dd

Author: Tom Zanussi <[email protected]>
Date:   Thu Oct 20 17:01:39 2011 -0500

meta-crownbay: README correction

In the instructions for manually extracting the binaries from the EMGD Linux tarball, an additional step for removing the emgd_drv_video shared library is necessary; this adds it for crownbay.

The following changes since commit c3e12aa981e97261093abee05bb0301c35f54c23:
Tom Zanussi (1):
meta-emenlow: switch edison back to linux-yocto-2.6.37 kernel

are available in the git repository at:

git://git.yoctoproject.org/meta-intel.git tzanussi/edison-next
http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/log/?h=tzanussi/edison-next

Tom Zanussi (5):
meta-crownbay: README correction
meta-fri2: README correction
meta-crownbay: add linux-yocto-rt_3.0.bbappend
meta-fri2: allow linux-yocto-rt to be used for fri2-noemgd
meta-crownbay: allow linux-yocto-rt to be used for crownbay

 meta-crownbay/README                               |    5 +++++
 .../linux/linux-yocto-rt_3.0.bbappend              |   20 ++++++++++++++++++++
 meta-fri2/README                                   |    9 +++++++++
 .../linux/linux-yocto-rt_3.0.bbappend              |    2 ++
 4 files changed, 36 insertions(+), 0 deletions(-)
 create mode 100644 meta-crownbay/recipes-kernel/linux/linux-yocto-rt_3.0.bbappend
#1 lore raw
Quoted 5 lines · Tom Zanussi

Hi,

I've created a new meta-intel/edison-next branch to hold commits intended for the upcoming 1.1 point release.

From a build perspective, it would be better if these commits ended up in the meta-intel/edison branch. It's generally what we do for poky.git and I'd like to keep meta-intel the same. Also, the autobuilder, when it builds out release branches like this, actually will end up requiring that the release branches for all layers are the same (at least until full layer support is implemented.)

-b

Signature · 3 lines
Elizabeth Flanagan
Yocto Project
Build and Release
#2 lore raw
Quoted 7 lines · Elizabeth
Quoted 5 lines · Tom Zanussi

Hi,

I've created a new meta-intel/edison-next branch to hold commits intended for the upcoming 1.1 point release.

Quoted 7 lines

From a build perspective, it would be better if these commits ended up in the meta-intel/edison branch. It's generally what we do for poky.git and I'd like to keep meta-intel the same. Also, the autobuilder, when it builds out release branches like this, actually will end up requiring that the release branches for all layers are the same (at least until full layer support is implemented.)

Yes, they will end up there, as the next paragraph mentions:

"I'll be collecting candidate commits for a 1.1 point release there until
it's time to cut the 1.1 point release, and will pull those into edison proper at that point, assuming we have agreement on the set of patches in the branch."

Tom

Quoted 4 lines

-b