Re: [meta-intel] New valleyisland support

2014-03-17 Thread Darren Hart 
On 3/13/14, 6:53, Bruce Ashfield bruce.ashfi...@windriver.com wrote:

On 14-03-13 09:43 AM, Tom Zanussi wrote:
 On Thu, 2014-03-13 at 06:40 +, Keskinarkaus, Teemu wrote:
 Hi,

 Okay, here is a little background and some new issues I've encountered.

 We have been using Yocto 1.5.1 earlier to create image for our HWs.
Now the new HW uses E38xx so I started testing the new Yocto/meta-intel
- branches to get (better) support for it.

 Since the current ValleyIsland support for meta-intel was for Dylan -
branch of Yocto and also because I wasn't able to create image with
working Intel HD Graphics driver I started looking for newer versions.
Graphics worked with VESA-driver, but not with actual Intel HD Graphics
driver.  Also the kernel was quite old being 3.8.13.

 I did some digging and noticed that dvhart/bsp-ng had support for the
intel-corei7 so that's why I ended up there. I never intended to use it
other than testing if I can create working image that has working Intel
HD Graphics for Valleyisland.  Then I tried latest poky/meta-intel
combination since dvhart/bsp-ng was merged there.

 When trying to create core-image-sato using the intel-corei7-64 bsp I
ended up with this:

 ERROR: Fetcher failure: Unable to find revision
29594404d7fe73cd80eaa4ee8c43dcc53970c60e in branch meta even from
upstream
 ERROR: Function failed: Fetcher failure for URL:
'git://git.pokylinux.org/linux-yocto-dev.git;nocheckout=1;branch=standar
d/base,meta;name=machine,meta'. Unable to fetch URL from any source.
 ERROR: Logfile of failure stored in:
/opt/build/tmp/work/corei7-64-intel-common-poky-linux/linux-yocto-dev/3.
14++gitAUTOINC+29594404d7_29594404d7-r0/temp/log.do_fetch.25380
 ERROR: Task 73 
(/opt/poky/../poky/meta/recipes-kernel/linux/linux-yocto-dev.bb,
do_fetch) failed with exit code '1'

 I'm not sure if that is a Yocto - bug, Meta-intel bug or my bug.


 I ran into this too and got around it by the hack below.  Not sure why
 it's not working, how it's actually supposed to work or if there's
 something we need to be doing in meta-intel layers, adding Bruce..

ok, this is report #2 of this. I'm firing up some tests here to see
if I can reproduce it.

You shouldn't need your mod to make it work .. so I'll dig out what
is happening.

Bruce


 diff --git a/meta/recipes-kernel/linux/linux-yocto-dev.bb
b/meta/recipes-kernel/linux/linux-
 index 5e09720..917714d 100644
 --- a/meta/recipes-kernel/linux/linux-yocto-dev.bb
 +++ b/meta/recipes-kernel/linux/linux-yocto-dev.bb
 @@ -28,8 +28,8 @@ SRC_URI =
git://git.pokylinux.org/linux-yocto-dev.git;nocheckout=1;branch
   # linux-yocto-dev is the preferred provider, they will be overridden
to
   # AUTOREV in following anonymous python routine and resolved when the
   # variables are finalized.
 -SRCREV_machine ?= 29594404d7fe73cd80eaa4ee8c43dcc53970c60e
 -SRCREV_meta ?= 29594404d7fe73cd80eaa4ee8c43dcc53970c60e


Well that is obviously wrong, machine and meta can't possibly be the same
commit ID. Bad dvhart... Oh wait... This is oe-core/poky. Bad Zedd.

These should be:

$ git rev-parse origin/standard/base
c4ee7a071d120118c4a547f7fb93b9c6f3b5

$ git rev-parse origin/meta
cdf9fb795b8e848cd3ddf3c5e0d98905fac27685


Bruce, is this already queued or do you want me to prep a patch? Or... Are
these the bogus ones that are meant to trigger failure  Is the AUTOREV
mechanism for linux-yocto-dev just not working?

 +SRCREV_machine ?= ${AUTOREV}
 +SRCREV_meta ?= ${AUTOREV}

FYI, you can do this in local.conf and avoid modifying the recipe sources
(I prefer this method):

SRCREV_meta_pn-linux-yocto-dev=${AUTOREV}
SRCREV_machine_pn-linux-yocto-dev=${AUTOREV}




   python () {
   if d.getVar(PREFERRED_PROVIDER_virtual/kernel, True) !=
linux-yocto-dev:


 Good to hear that linut-rt - support was not dropped, but merely just
changed.

 Btw. Is it intentional that in intel-corei7-64.conf the
PREFERRED_PROVIDER_virtual/kernel is set using = and not ?= which makes
it impossible to override it from later scripts? Or am I doing
something wrong again? I had to comment out that line to be able to use
my own kernel version on later tests.


This is also my mistake. It should also be ?=. It was at = during
development and I forgot to update it to ?= before pushing to meta-intel.
Thank you for catching that.


-- 
Darren Hart
Yocto Project - Linux Kernel
Intel Open Source Technology Center




-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

Re: [meta-intel] New valleyisland support

2014-03-17 Thread Bruce Ashfield 

On 2014-03-17, 6:31 PM, Darren Hart wrote:

On 3/13/14, 6:53, Bruce Ashfield bruce.ashfi...@windriver.com wrote:


On 14-03-13 09:43 AM, Tom Zanussi wrote:

On Thu, 2014-03-13 at 06:40 +, Keskinarkaus, Teemu wrote:

Hi,

Okay, here is a little background and some new issues I've encountered.

We have been using Yocto 1.5.1 earlier to create image for our HWs.
Now the new HW uses E38xx so I started testing the new Yocto/meta-intel
- branches to get (better) support for it.

Since the current ValleyIsland support for meta-intel was for Dylan -
branch of Yocto and also because I wasn't able to create image with
working Intel HD Graphics driver I started looking for newer versions.
Graphics worked with VESA-driver, but not with actual Intel HD Graphics
driver.  Also the kernel was quite old being 3.8.13.

I did some digging and noticed that dvhart/bsp-ng had support for the
intel-corei7 so that's why I ended up there. I never intended to use it
other than testing if I can create working image that has working Intel
HD Graphics for Valleyisland.  Then I tried latest poky/meta-intel
combination since dvhart/bsp-ng was merged there.

When trying to create core-image-sato using the intel-corei7-64 bsp I
ended up with this:

ERROR: Fetcher failure: Unable to find revision
29594404d7fe73cd80eaa4ee8c43dcc53970c60e in branch meta even from
upstream
ERROR: Function failed: Fetcher failure for URL:
'git://git.pokylinux.org/linux-yocto-dev.git;nocheckout=1;branch=standar
d/base,meta;name=machine,meta'. Unable to fetch URL from any source.
ERROR: Logfile of failure stored in:
/opt/build/tmp/work/corei7-64-intel-common-poky-linux/linux-yocto-dev/3.
14++gitAUTOINC+29594404d7_29594404d7-r0/temp/log.do_fetch.25380
ERROR: Task 73
(/opt/poky/../poky/meta/recipes-kernel/linux/linux-yocto-dev.bb,
do_fetch) failed with exit code '1'

I'm not sure if that is a Yocto - bug, Meta-intel bug or my bug.



I ran into this too and got around it by the hack below.  Not sure why
it's not working, how it's actually supposed to work or if there's
something we need to be doing in meta-intel layers, adding Bruce..


ok, this is report #2 of this. I'm firing up some tests here to see
if I can reproduce it.

You shouldn't need your mod to make it work .. so I'll dig out what
is happening.

Bruce



diff --git a/meta/recipes-kernel/linux/linux-yocto-dev.bb
b/meta/recipes-kernel/linux/linux-
index 5e09720..917714d 100644
--- a/meta/recipes-kernel/linux/linux-yocto-dev.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-dev.bb
@@ -28,8 +28,8 @@ SRC_URI =
git://git.pokylinux.org/linux-yocto-dev.git;nocheckout=1;branch
   # linux-yocto-dev is the preferred provider, they will be overridden
to
   # AUTOREV in following anonymous python routine and resolved when the
   # variables are finalized.
-SRCREV_machine ?= 29594404d7fe73cd80eaa4ee8c43dcc53970c60e
-SRCREV_meta ?= 29594404d7fe73cd80eaa4ee8c43dcc53970c60e



Well that is obviously wrong, machine and meta can't possibly be the same
commit ID. Bad dvhart... Oh wait... This is oe-core/poky. Bad Zedd.


:) guilty!



These should be:

$ git rev-parse origin/standard/base
c4ee7a071d120118c4a547f7fb93b9c6f3b5

$ git rev-parse origin/meta
cdf9fb795b8e848cd3ddf3c5e0d98905fac27685


Bruce, is this already queued or do you want me to prep a patch? Or... Are
these the bogus ones that are meant to trigger failure  Is the AUTOREV
mechanism for linux-yocto-dev just not working?


It is supposed to be the latter, and Tom has been seeing issues, but I
can't reproduce the failure here. The AUTOREV overwrite is triggered in
anonymous python, all that I can think is that it isn't running early
enough.

Bruce




+SRCREV_machine ?= ${AUTOREV}
+SRCREV_meta ?= ${AUTOREV}


FYI, you can do this in local.conf and avoid modifying the recipe sources
(I prefer this method):

SRCREV_meta_pn-linux-yocto-dev=${AUTOREV}
SRCREV_machine_pn-linux-yocto-dev=${AUTOREV}





   python () {
   if d.getVar(PREFERRED_PROVIDER_virtual/kernel, True) !=
linux-yocto-dev:



Good to hear that linut-rt - support was not dropped, but merely just
changed.

Btw. Is it intentional that in intel-corei7-64.conf the
PREFERRED_PROVIDER_virtual/kernel is set using = and not ?= which makes
it impossible to override it from later scripts? Or am I doing
something wrong again? I had to comment out that line to be able to use
my own kernel version on later tests.



This is also my mistake. It should also be ?=. It was at = during
development and I forgot to update it to ?= before pushing to meta-intel.
Thank you for catching that.




--
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

Re: [meta-intel] New valleyisland support

2014-03-13 Thread Keskinarkaus, Teemu 
Hi,

Okay, here is a little background and some new issues I've encountered.

We have been using Yocto 1.5.1 earlier to create image for our HWs. Now the new 
HW uses E38xx so I started testing the new Yocto/meta-intel - branches to get 
(better) support for it.

Since the current ValleyIsland support for meta-intel was for Dylan - branch of 
Yocto and also because I wasn't able to create image with working Intel HD 
Graphics driver I started looking for newer versions. Graphics worked with 
VESA-driver, but not with actual Intel HD Graphics driver.  Also the kernel was 
quite old being 3.8.13.

I did some digging and noticed that dvhart/bsp-ng had support for the 
intel-corei7 so that's why I ended up there. I never intended to use it other 
than testing if I can create working image that has working Intel HD Graphics 
for Valleyisland.  Then I tried latest poky/meta-intel combination since 
dvhart/bsp-ng was merged there.

When trying to create core-image-sato using the intel-corei7-64 bsp I ended up 
with this:

ERROR: Fetcher failure: Unable to find revision 
29594404d7fe73cd80eaa4ee8c43dcc53970c60e in branch meta even from upstream
ERROR: Function failed: Fetcher failure for URL: 
'git://git.pokylinux.org/linux-yocto-dev.git;nocheckout=1;branch=standard/base,meta;name=machine,meta'.
 Unable to fetch URL from any source.
ERROR: Logfile of failure stored in: 
/opt/build/tmp/work/corei7-64-intel-common-poky-linux/linux-yocto-dev/3.14++gitAUTOINC+29594404d7_29594404d7-r0/temp/log.do_fetch.25380
ERROR: Task 73 (/opt/poky/../poky/meta/recipes-kernel/linux/linux-yocto-dev.bb, 
do_fetch) failed with exit code '1'

I'm not sure if that is a Yocto - bug, Meta-intel bug or my bug.

Good to hear that linut-rt - support was not dropped, but merely just changed.

Btw. Is it intentional that in intel-corei7-64.conf the 
PREFERRED_PROVIDER_virtual/kernel is set using = and not ?= which makes it 
impossible to override it from later scripts? Or am I doing something wrong 
again? I had to comment out that line to be able to use my own kernel version 
on later tests.

Teemu Keskinarkaus
Software system engineer

maximatecc - Humans in control


 -Original Message-
 From: Darren Hart [mailto:dvh...@linux.intel.com]
 Sent: 12. maaliskuuta 2014 17:01
 To: Keskinarkaus, Teemu; Meta Intel
 Cc: rebecca.swee.fun.chang; boon.leong.ong
 Subject: Re: [meta-intel] New valleyisland support

 Hi Teemu,

 Can you explain how you arrived at using the dvhart/bsp-ng branch? This is a
 development/testing branch, certainly not something meant for productization
 use. We're merging bits of bsp-ng into master as it's tested, verified, and 
 fixed
 up.

 Valleyisland support specifically is available in Dylan under meta-isg/meta-
 valleyisland. Rebecca and her team are working on adding it to Dora with a 
 3.10
 kernel I believe, but I'll leave it to her to comment on that.

 If you are just looking for Baytrail SoC support (not specifically
 valleyisland) then that is now available in meta-intel/master using the
 intel-corei7-64 BSP. This is a new approach to Intel BSPs which supports 
 multiple
 boards/CPUs with a single BSP.

 As to linux-yocto-rt, we have not removed support for it. If you are 
 referring to
 the removal of the linux-yocto-rt*bbappend files in dvhart/bsp-ng, that is 
 done in
 favor of a new mechanism called the intel-common kernel, which uses a single
 kernel build across multiple BSPs, removing the need for the bbappend in each
 BSP layer - you'll note it is still present under common/recipes-kernel/linux.

 If you can provide some more context about what you are trying to do, we 
 should
 be able to help make sure you are working with the right sources, and 
 prioritize
 any development to fill any gaps.

 Thanks,

 Darren

 On 3/10/14, 21:45, Keskinarkaus, Teemu
 teemu.keskinark...@maximatecc.com wrote:

 Hi,
 
 I'm bit lost here. I'm looking for support for valleyisland that is for
 Dora branch of the Yocto. I cloned the dvhart/bsp-ng, but couldn't find
 any references to valleyisland or bay trail from there so I'm guessing
 I'm looking from the wrong place. Is there a right place? Or is the
 support 'coming soon' for Dora?
 
 I'm also bit disappointed to see that you chose to drop linux-rt
 support in favor of non-rt-linux. Mostly because I'm using the linux-rt 
 variant.
 ;) So now I need to add it back there myself.
 
 Teemu Keskinarkaus
 Software system engineer
 
 maximatecc - Humans in control
 
 
 
 
 Actuant Corporation Email Notice
 
 This message is intended only for the use of the Addressee and may
 contain information that is PRIVILEGED and/or CONFIDENTIAL.
 This email is intended only for the personal and confidential use of
 the
 recipient(s) named above. If the reader of this email is not an
 intended recipient, you have received this email in error and any
 review, dissemination, distribution or copying is strictly prohibited.
 If you have received this email

Re: [meta-intel] New valleyisland support

2014-03-13 Thread Tom Zanussi 
On Thu, 2014-03-13 at 06:40 +, Keskinarkaus, Teemu wrote:
 Hi,
 
 Okay, here is a little background and some new issues I've encountered.
 
 We have been using Yocto 1.5.1 earlier to create image for our HWs. Now the 
 new HW uses E38xx so I started testing the new Yocto/meta-intel - branches to 
 get (better) support for it.
 
 Since the current ValleyIsland support for meta-intel was for Dylan - branch 
 of Yocto and also because I wasn't able to create image with working Intel HD 
 Graphics driver I started looking for newer versions. Graphics worked with 
 VESA-driver, but not with actual Intel HD Graphics driver.  Also the kernel 
 was quite old being 3.8.13.
 
 I did some digging and noticed that dvhart/bsp-ng had support for the 
 intel-corei7 so that's why I ended up there. I never intended to use it other 
 than testing if I can create working image that has working Intel HD Graphics 
 for Valleyisland.  Then I tried latest poky/meta-intel combination since 
 dvhart/bsp-ng was merged there.
 
 When trying to create core-image-sato using the intel-corei7-64 bsp I ended 
 up with this:
 
 ERROR: Fetcher failure: Unable to find revision 
 29594404d7fe73cd80eaa4ee8c43dcc53970c60e in branch meta even from upstream
 ERROR: Function failed: Fetcher failure for URL: 
 'git://git.pokylinux.org/linux-yocto-dev.git;nocheckout=1;branch=standard/base,meta;name=machine,meta'.
  Unable to fetch URL from any source.
 ERROR: Logfile of failure stored in: 
 /opt/build/tmp/work/corei7-64-intel-common-poky-linux/linux-yocto-dev/3.14++gitAUTOINC+29594404d7_29594404d7-r0/temp/log.do_fetch.25380
 ERROR: Task 73 
 (/opt/poky/../poky/meta/recipes-kernel/linux/linux-yocto-dev.bb, do_fetch) 
 failed with exit code '1'
 
 I'm not sure if that is a Yocto - bug, Meta-intel bug or my bug.
 

I ran into this too and got around it by the hack below.  Not sure why
it's not working, how it's actually supposed to work or if there's
something we need to be doing in meta-intel layers, adding Bruce..

diff --git a/meta/recipes-kernel/linux/linux-yocto-dev.bb 
b/meta/recipes-kernel/linux/linux-
index 5e09720..917714d 100644
--- a/meta/recipes-kernel/linux/linux-yocto-dev.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-dev.bb
@@ -28,8 +28,8 @@ SRC_URI = 
git://git.pokylinux.org/linux-yocto-dev.git;nocheckout=1;branch
 # linux-yocto-dev is the preferred provider, they will be overridden to
 # AUTOREV in following anonymous python routine and resolved when the
 # variables are finalized.
-SRCREV_machine ?= 29594404d7fe73cd80eaa4ee8c43dcc53970c60e
-SRCREV_meta ?= 29594404d7fe73cd80eaa4ee8c43dcc53970c60e
+SRCREV_machine ?= ${AUTOREV}
+SRCREV_meta ?= ${AUTOREV}
 
 python () {
 if d.getVar(PREFERRED_PROVIDER_virtual/kernel, True) != 
linux-yocto-dev:


 Good to hear that linut-rt - support was not dropped, but merely just changed.
 
 Btw. Is it intentional that in intel-corei7-64.conf the 
 PREFERRED_PROVIDER_virtual/kernel is set using = and not ?= which makes it 
 impossible to override it from later scripts? Or am I doing something wrong 
 again? I had to comment out that line to be able to use my own kernel version 
 on later tests.
 
 Teemu Keskinarkaus
 Software system engineer
 
 maximatecc - Humans in control
 
 
  -Original Message-
  From: Darren Hart [mailto:dvh...@linux.intel.com]
  Sent: 12. maaliskuuta 2014 17:01
  To: Keskinarkaus, Teemu; Meta Intel
  Cc: rebecca.swee.fun.chang; boon.leong.ong
  Subject: Re: [meta-intel] New valleyisland support
 
  Hi Teemu,
 
  Can you explain how you arrived at using the dvhart/bsp-ng branch? This is a
  development/testing branch, certainly not something meant for productization
  use. We're merging bits of bsp-ng into master as it's tested, verified, and 
  fixed
  up.
 
  Valleyisland support specifically is available in Dylan under meta-isg/meta-
  valleyisland. Rebecca and her team are working on adding it to Dora with a 
  3.10
  kernel I believe, but I'll leave it to her to comment on that.
 
  If you are just looking for Baytrail SoC support (not specifically
  valleyisland) then that is now available in meta-intel/master using the
  intel-corei7-64 BSP. This is a new approach to Intel BSPs which supports 
  multiple
  boards/CPUs with a single BSP.
 
  As to linux-yocto-rt, we have not removed support for it. If you are 
  referring to
  the removal of the linux-yocto-rt*bbappend files in dvhart/bsp-ng, that is 
  done in
  favor of a new mechanism called the intel-common kernel, which uses a single
  kernel build across multiple BSPs, removing the need for the bbappend in 
  each
  BSP layer - you'll note it is still present under 
  common/recipes-kernel/linux.
 
  If you can provide some more context about what you are trying to do, we 
  should
  be able to help make sure you are working with the right sources, and 
  prioritize
  any development to fill any gaps.
 
  Thanks,
 
  Darren
 
  On 3/10/14, 21:45, Keskinarkaus, Teemu
  teemu.keskinark...@maximatecc.com

Re: [meta-intel] New valleyisland support

2014-03-13 Thread Bruce Ashfield 

On 14-03-13 09:43 AM, Tom Zanussi wrote:

On Thu, 2014-03-13 at 06:40 +, Keskinarkaus, Teemu wrote:

Hi,

Okay, here is a little background and some new issues I've encountered.

We have been using Yocto 1.5.1 earlier to create image for our HWs. Now the new 
HW uses E38xx so I started testing the new Yocto/meta-intel - branches to get 
(better) support for it.

Since the current ValleyIsland support for meta-intel was for Dylan - branch of 
Yocto and also because I wasn't able to create image with working Intel HD 
Graphics driver I started looking for newer versions. Graphics worked with 
VESA-driver, but not with actual Intel HD Graphics driver.  Also the kernel was 
quite old being 3.8.13.

I did some digging and noticed that dvhart/bsp-ng had support for the 
intel-corei7 so that's why I ended up there. I never intended to use it other 
than testing if I can create working image that has working Intel HD Graphics 
for Valleyisland.  Then I tried latest poky/meta-intel combination since 
dvhart/bsp-ng was merged there.

When trying to create core-image-sato using the intel-corei7-64 bsp I ended up 
with this:

ERROR: Fetcher failure: Unable to find revision 
29594404d7fe73cd80eaa4ee8c43dcc53970c60e in branch meta even from upstream
ERROR: Function failed: Fetcher failure for URL: 
'git://git.pokylinux.org/linux-yocto-dev.git;nocheckout=1;branch=standard/base,meta;name=machine,meta'.
 Unable to fetch URL from any source.
ERROR: Logfile of failure stored in: 
/opt/build/tmp/work/corei7-64-intel-common-poky-linux/linux-yocto-dev/3.14++gitAUTOINC+29594404d7_29594404d7-r0/temp/log.do_fetch.25380
ERROR: Task 73 (/opt/poky/../poky/meta/recipes-kernel/linux/linux-yocto-dev.bb, 
do_fetch) failed with exit code '1'

I'm not sure if that is a Yocto - bug, Meta-intel bug or my bug.



I ran into this too and got around it by the hack below.  Not sure why
it's not working, how it's actually supposed to work or if there's
something we need to be doing in meta-intel layers, adding Bruce..


ok, this is report #2 of this. I'm firing up some tests here to see
if I can reproduce it.

You shouldn't need your mod to make it work .. so I'll dig out what
is happening.

Bruce



diff --git a/meta/recipes-kernel/linux/linux-yocto-dev.bb 
b/meta/recipes-kernel/linux/linux-
index 5e09720..917714d 100644
--- a/meta/recipes-kernel/linux/linux-yocto-dev.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-dev.bb
@@ -28,8 +28,8 @@ SRC_URI = 
git://git.pokylinux.org/linux-yocto-dev.git;nocheckout=1;branch
  # linux-yocto-dev is the preferred provider, they will be overridden to
  # AUTOREV in following anonymous python routine and resolved when the
  # variables are finalized.
-SRCREV_machine ?= 29594404d7fe73cd80eaa4ee8c43dcc53970c60e
-SRCREV_meta ?= 29594404d7fe73cd80eaa4ee8c43dcc53970c60e
+SRCREV_machine ?= ${AUTOREV}
+SRCREV_meta ?= ${AUTOREV}

  python () {
  if d.getVar(PREFERRED_PROVIDER_virtual/kernel, True) != 
linux-yocto-dev:



Good to hear that linut-rt - support was not dropped, but merely just changed.

Btw. Is it intentional that in intel-corei7-64.conf the 
PREFERRED_PROVIDER_virtual/kernel is set using = and not ?= which makes it 
impossible to override it from later scripts? Or am I doing something wrong 
again? I had to comment out that line to be able to use my own kernel version 
on later tests.

Teemu Keskinarkaus
Software system engineer

maximatecc - Humans in control



-Original Message-
From: Darren Hart [mailto:dvh...@linux.intel.com]
Sent: 12. maaliskuuta 2014 17:01
To: Keskinarkaus, Teemu; Meta Intel
Cc: rebecca.swee.fun.chang; boon.leong.ong
Subject: Re: [meta-intel] New valleyisland support

Hi Teemu,

Can you explain how you arrived at using the dvhart/bsp-ng branch? This is a
development/testing branch, certainly not something meant for productization
use. We're merging bits of bsp-ng into master as it's tested, verified, and 
fixed
up.

Valleyisland support specifically is available in Dylan under meta-isg/meta-
valleyisland. Rebecca and her team are working on adding it to Dora with a 3.10
kernel I believe, but I'll leave it to her to comment on that.

If you are just looking for Baytrail SoC support (not specifically
valleyisland) then that is now available in meta-intel/master using the
intel-corei7-64 BSP. This is a new approach to Intel BSPs which supports 
multiple
boards/CPUs with a single BSP.

As to linux-yocto-rt, we have not removed support for it. If you are referring 
to
the removal of the linux-yocto-rt*bbappend files in dvhart/bsp-ng, that is done 
in
favor of a new mechanism called the intel-common kernel, which uses a single
kernel build across multiple BSPs, removing the need for the bbappend in each
BSP layer - you'll note it is still present under common/recipes-kernel/linux.

If you can provide some more context about what you are trying to do, we should
be able to help make sure you are working with the right sources, and prioritize
any development to fill any

Re: [meta-intel] New valleyisland support

2014-03-12 Thread Chang, Rebecca Swee Fun 
Hi all,

We are in progress of making Valley Island BSP available in Dora with kernel 
3.10.
Currently we are trying to root cause the i915 graphic driver issue and we will 
start pushing out for review once it is done.
As of linux-yocto-rt for Valley Island, it is not included in Dylan release. I 
will need to discuss with the team whether to include in our coming release.

Thanks.
Rebecca

 -Original Message-
 From: Darren Hart [mailto:dvh...@linux.intel.com]
 Sent: 12 March, 2014 11:01 PM
 To: Keskinarkaus, Teemu; Meta Intel
 Cc: Chang, Rebecca Swee Fun; Ong, Boon Leong
 Subject: Re: [meta-intel] New valleyisland support
 
 Hi Teemu,
 
 Can you explain how you arrived at using the dvhart/bsp-ng branch? This is a
 development/testing branch, certainly not something meant for
 productization use. We're merging bits of bsp-ng into master as it's tested,
 verified, and fixed up.
 
 Valleyisland support specifically is available in Dylan under meta-isg/meta-
 valleyisland. Rebecca and her team are working on adding it to Dora with a
 3.10 kernel I believe, but I'll leave it to her to comment on that.
 
 If you are just looking for Baytrail SoC support (not specifically
 valleyisland) then that is now available in meta-intel/master using the
 intel-corei7-64 BSP. This is a new approach to Intel BSPs which supports
 multiple boards/CPUs with a single BSP.
 
 As to linux-yocto-rt, we have not removed support for it. If you are referring
 to the removal of the linux-yocto-rt*bbappend files in dvhart/bsp-ng, that is
 done in favor of a new mechanism called the intel-common kernel, which
 uses a single kernel build across multiple BSPs, removing the need for the
 bbappend in each BSP layer - you'll note it is still present under
 common/recipes-kernel/linux.
 
 If you can provide some more context about what you are trying to do, we
 should be able to help make sure you are working with the right sources, and
 prioritize any development to fill any gaps.
 
 Thanks,
 
 Darren
 
 On 3/10/14, 21:45, Keskinarkaus, Teemu
 teemu.keskinark...@maximatecc.com wrote:
 
 Hi,
 
 I'm bit lost here. I'm looking for support for valleyisland that is for
 Dora branch of the Yocto. I cloned the dvhart/bsp-ng, but couldn't find
 any references to valleyisland or bay trail from there so I'm guessing
 I'm looking from the wrong place. Is there a right place? Or is the
 support 'coming soon' for Dora?
 
 I'm also bit disappointed to see that you chose to drop linux-rt
 support in favor of non-rt-linux. Mostly because I'm using the linux-rt
 variant.
 ;) So now I need to add it back there myself.
 
 Teemu Keskinarkaus
 Software system engineer
 
 maximatecc - Humans in control
 
 
 
 
 Actuant Corporation Email Notice
 
 This message is intended only for the use of the Addressee and may
 contain information that is PRIVILEGED and/or CONFIDENTIAL.
 This email is intended only for the personal and confidential use of
 the
 recipient(s) named above. If the reader of this email is not an
 intended recipient, you have received this email in error and any
 review, dissemination, distribution or copying is strictly prohibited.
 If you have received this email in error, please notify the sender
 immediately by return mail and permanently delete the copy you received.
 
 Thank you.
 --
 ___
 meta-intel mailing list
 meta-intel@yoctoproject.org
 https://lists.yoctoproject.org/listinfo/meta-intel
 
 
 
 --
 Darren Hart
 Yocto Project - Linux Kernel
 Intel Open Source Technology Center
 
 
 

-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel