Re: [yocto] yocto-bsp create question

2014-09-12 Thread Michael Kotson
Hi Tom,
   Thanks for the response.  I filed an enhancement request, but in the 
meantime is there a preferred method to create our own BSP from Valleyisland?

All the best,
Michael

Michael Kotson
Chief Technology Officer

OTel:   (303) 412-2055
TE-Mail: mkot...@octagonsystems.com
 NOTICE: The information contained in this email and any document attached 
hereto is intended only for the named recipient(s). If you are not the intended 
recipient, nor the employee or agent responsible for delivering this message in 
confidence to the intended recipient(s), you are hereby notified that you have 
received this transmittal in error, and any review, dissemination, distribution 
or copying of this transmittal or its attachments is strictly prohibited. If 
you have received this transmittal and/or attachments in error, please notify 
me immediately by reply e-mail and then delete this message, including any 
attachments. 


-Original Message-
From: Tom Zanussi [mailto:tom.zanu...@intel.com] 
Sent: Friday, September 12, 2014 10:26 AM
To: Michael Kotson
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] yocto-bsp create question

On Fri, 2014-09-12 at 10:07 -0600, Michael Kotson wrote:
> Hi all,
> 
>We are trying to create a custom BSP based off of valleyisland-64 
> using the yocto-bsp script.  When we are presented choices for which 
> BSP to branch from, valleyisland isn’t one of the choices.  We have 
> tried all of the different kernel options presented, but no luck.  I’m 
> pretty sure we have the layers added correctly, as we can build
> valleyisland-32 and valleyisland-64 inside of hob with no problems.
> Any idea what we are doing wrong?
> 

Nothing that you're doing wrong, it's just that the valleyisland BSPs are built 
a little differently from the normal BSPs - instead of a machine branch, they 
do a merge of a valleyisland-io branch into another branch and the yocto-bsp 
tools aren't set up to do that.  They'd need to be enhanced to enhanced to 
handle cases like that.  I'd suggest filing a an enhancement bug so we can add 
that capability..

Thanks,

Tom



>  
> 
> All the best,
> 
> Michael
> 
>  
> 
>  
> 
> Michael Kotson
> 
> Chief Technology Officer
> 
> 
> 
> (Tel:   (303) 412-2055
> 
> *E-Mail: mkot...@octagonsystems.com
> 
> NOTICE: The information contained in this email and any document 
> attached hereto is intended only for the named recipient(s). If you 
> are not the intended recipient, nor the employee or agent responsible 
> for delivering this message in confidence to the intended 
> recipient(s), you are hereby notified that you have received this 
> transmittal in error, and any review, dissemination, distribution or 
> copying of this transmittal or its attachments is strictly prohibited.
> If you have received this transmittal and/or attachments in error, 
> please notify me immediately by reply e-mail and then delete this 
> message, including any attachments.
> 
>  
> 
> 


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


[yocto] yocto-bsp create question

2014-09-12 Thread Michael Kotson
Hi all,

   We are trying to create a custom BSP based off of valleyisland-64
using the yocto-bsp script.  When we are presented choices for which BSP
to branch from, valleyisland isn't one of the choices.  We have tried
all of the different kernel options presented, but no luck.  I'm pretty
sure we have the layers added correctly, as we can build valleyisland-32
and valleyisland-64 inside of hob with no problems.  Any idea what we
are doing wrong?

 

All the best,

Michael

 

 

Michael Kotson

Chief Technology Officer

 

(Tel:   (303) 412-2055

*E-Mail: mkot...@octagonsystems.com <mailto:mkot...@octagonsystems.com> 

NOTICE: The information contained in this email and any document
attached hereto is intended only for the named recipient(s). If you are
not the intended recipient, nor the employee or agent responsible for
delivering this message in confidence to the intended recipient(s), you
are hereby notified that you have received this transmittal in error,
and any review, dissemination, distribution or copying of this
transmittal or its attachments is strictly prohibited. If you have
received this transmittal and/or attachments in error, please notify me
immediately by reply e-mail and then delete this message, including any
attachments. 

 

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