[PATCH 1/6] MAINTAINERS: corect pathname

[PATCH 1/6] MAINTAINERS: corect pathname

[nitin.a.kamble]

From: Nitin A Kamble <nitin.a.kamble@intel.com>

The commmon directory has more stuff than just recipes-core.
All this need to be maintained together as part of the meta-intel layer.

Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
---
 MAINTAINERS |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/MAINTAINERS b/MAINTAINERS
index d63ed31..eac592b 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -42,7 +42,7 @@ F:	meta-chiefriver/
 
 COMMON
 M:	Nitin A Kamble<nitin.a.kamble@intel.com>
-F:	common/recipes-core/
+F:	common/
 
 CROWNBAY
 M:	Nitin A Kamble<nitin.a.kamble@intel.com>
-- 
1.7.3.4

[PATCH 2/6] chiefriver README: add WebTitle & Compliance information

[nitin.a.kamble]

From: Nitin A Kamble <nitin.a.kamble@intel.com>

The WebTitle will be used to publish the BSP on the Yocto Project Website.
And adding the Yocto Project Compliance information for the 1.3 release.
Also specifying all the layers used from meta-intel repository.

Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
---
 meta-chiefriver/README |   10 +++++++++-
 1 files changed, 9 insertions(+), 1 deletions(-)

diff --git a/meta-chiefriver/README b/meta-chiefriver/README
index 7c47b02..7af1288 100644
--- a/meta-chiefriver/README
+++ b/meta-chiefriver/README
@@ -6,6 +6,14 @@ The 'Chief River' platform consists of the Intel Ivy Bridge processor,
 plus the Panther Point PCH.  This BSP assumes that the Ivy Bridge
 integrated graphics are being used.
 
+WebTitle: Intel 3nd Generations Core Platforms: Core i3, i5, i7 (Ivy Bridge)
+
+
+Compliance:
+============
+This BSP is compliant with Yocto Project as per requirements listed here:
+http://www.yoctoproject.org/yocto-project-compatible-registration
+
 
 Dependencies
 ============
@@ -20,7 +28,7 @@ This layer depends on:
   branch: master
 
   URI: git://git.yoctoproject.org/meta-intel
-  layers: intel
+  layers: meta-intel, meta-chiefriver
   branch: master
 
 
-- 
1.7.3.4

[PATCH 3/6] crownbay README: add WebTitle & Compliance information

[nitin.a.kamble]

From: Nitin A Kamble <nitin.a.kamble@intel.com>

The WebTitle will be used to publish the BSP on the Yocto Project Website.
And adding the Yocto Project Compliance information for the 1.3 release.
Also specifying all the layers used from meta-intel repository.

Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
---
 meta-crownbay/README |   13 +++++++++++--
 1 files changed, 11 insertions(+), 2 deletions(-)

diff --git a/meta-crownbay/README b/meta-crownbay/README
index 4bc9f31..3996a94 100644
--- a/meta-crownbay/README
+++ b/meta-crownbay/README
@@ -2,13 +2,22 @@ This README file contains information on building the meta-crownbay
 BSP layer, and booting the images contained in the /binary directory.
 Please see the corresponding sections below for details.
 
-The Crown Bay platform consists of the Intel Atom Z6xx processor,
+The Crown Bay platform consists of the Intel Atom E6xx processor,
 plus the Intel EG20T Platform Controller Hub (Tunnel Creek + Topcliff).
 
 It also supports the E6xx embedded on-chip graphics via the Intel
 Embedded Media and Graphics Driver (EMGD) 1.14 Driver.
 
 
+WebTitle: Intel Atom E6xx processor with Intel EG20T Controller Hub development kit (crownbay)
+
+
+Compliance:
+============
+This BSP is compliant with Yocto Project as per requirements listed here:
+http://www.yoctoproject.org/yocto-project-compatible-registration
+
+
 Dependencies
 ============
 
@@ -22,7 +31,7 @@ This layer depends on:
   branch: master
 
   URI: git://git.yoctoproject.org/meta-intel
-  layers: intel
+  layers: meta-intel, meta-crownbay
   branch: master
 
 
-- 
1.7.3.4

[PATCH 0/6] meta-intel: README updates

[nitin.a.kamble]

From: Nitin A Kamble <nitin.a.kamble@intel.com>

For the YP 1.3 release, README changes for the BSPs I am maintaining.

Thanks,
Nitin


The following changes since commit f502e7493694c487767f60df232055bc7b854e69:

  gstreamer-vaapi: add missing build dependencies (2012-10-23 07:43:46 -0500)

are available in the git repository at:
  git://git.yoctoproject.org/meta-intel-contrib nitin/misc
  http://git.yoctoproject.org/cgit.cgi/meta-intel-contrib/log/?h=nitin/misc

Nitin A Kamble (6):
  MAINTAINERS: corect pathname
  chiefriver README: add WebTitle & Compliance information
  crownbay README: add WebTitle & Compliance information
  emenlow README: add WebTitle & Compliance information
  jasperforest README: add WebTitle & Compliance information
  sugarbay README: add WebTitle & Compliance information

 MAINTAINERS              |    2 +-
 meta-chiefriver/README   |   10 +++++++++-
 meta-crownbay/README     |   13 +++++++++++--
 meta-emenlow/README      |   11 ++++++++++-
 meta-jasperforest/README |   11 ++++++++++-
 meta-sugarbay/README     |    9 ++++++++-
 6 files changed, 49 insertions(+), 7 deletions(-)

-- 
1.7.3.4

[PATCH 4/6] emenlow README: add WebTitle & Compliance information

[nitin.a.kamble]

From: Nitin A Kamble <nitin.a.kamble@intel.com>

The WebTitle will be used to publish the BSP on the Yocto Project Website.
And adding the Yocto Project Compliance information for the 1.3 release.
Also specifying all the layers used from meta-intel repository.

Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
---
 meta-emenlow/README |   11 ++++++++++-
 1 files changed, 10 insertions(+), 1 deletions(-)

diff --git a/meta-emenlow/README b/meta-emenlow/README
index 3932718..91381d3 100644
--- a/meta-emenlow/README
+++ b/meta-emenlow/README
@@ -13,6 +13,15 @@ depending on which BSP tarball you downloaded.
 Please see the corresponding sections below for details.
 
 
+WebTitle: Platforms with Intel Atom Z5xx processor with Intel US15W Controller Hub (emenlow)
+
+
+Compliance:
+============
+This BSP is compliant with Yocto Project as per requirements listed here:
+http://www.yoctoproject.org/yocto-project-compatible-registration
+
+
 Dependencies
 ============
 
@@ -26,7 +35,7 @@ This layer depends on:
   branch: master
 
   URI: git://git.yoctoproject.org/meta-intel
-  layers: intel
+  layers: meta-intel, meta-emenlow
   branch: master
 
 
-- 
1.7.3.4

[PATCH 5/6] jasperforest README: add WebTitle & Compliance information

[nitin.a.kamble]

From: Nitin A Kamble <nitin.a.kamble@intel.com>

The WebTitle will be used to publish the BSP on the Yocto Project Website.
And adding the Yocto Project Compliance information for the 1.3 release.
Also specifying all the layers used from meta-intel repository.

Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
---
 meta-jasperforest/README |   11 ++++++++++-
 1 files changed, 10 insertions(+), 1 deletions(-)

diff --git a/meta-jasperforest/README b/meta-jasperforest/README
index 12f84c2..98a4d57 100644
--- a/meta-jasperforest/README
+++ b/meta-jasperforest/README
@@ -8,6 +8,15 @@ combined with the Intel 3420 PCH chipset (Ibex Peak) make up the
 'Picket Post' CRB this BSP was developed on.
 
 
+WebTitle: Platforms with Intel Xeon C5500/C3500 processors with Intel 3420 PCH chipset (jasperforest)
+
+
+Compliance:
+============
+This BSP is compliant with Yocto Project as per requirements listed here:
+http://www.yoctoproject.org/yocto-project-compatible-registration
+
+
 Dependencies
 ============
 
@@ -21,7 +30,7 @@ This layer depends on:
   branch: master
 
   URI: git://git.yoctoproject.org/meta-intel
-  layers: intel
+  layers: meta-intel, meta-jasperforest
   branch: master
 
 
-- 
1.7.3.4

[PATCH 6/6] sugarbay README: add WebTitle & Compliance information

[nitin.a.kamble]

From: Nitin A Kamble <nitin.a.kamble@intel.com>

The WebTitle will be used to publish the BSP on the Yocto Project Website.
And adding the Yocto Project Compliance information for the 1.3 release.
Also specifying all the layers used from meta-intel repository.

Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
---
 meta-sugarbay/README |    9 ++++++++-
 1 files changed, 8 insertions(+), 1 deletions(-)

diff --git a/meta-sugarbay/README b/meta-sugarbay/README
index c8a99d7..36da170 100644
--- a/meta-sugarbay/README
+++ b/meta-sugarbay/README
@@ -6,6 +6,13 @@ The 'Sugar Bay' platform consists of the Intel Sandy Bridge processor,
 plus the Cougar Point PCH (Q67 Express or B65 Express chipsets).  This
 BSP assumes that the Sandy Bridge integrated graphics are being used.
 
+WebTitle: Intel 2nd Generations Core Platforms: Core i3, i5, i7 (Sandy Bridge)
+
+Compliance:
+============
+This BSP is compliant with Yocto Project as per requirements listed here:
+http://www.yoctoproject.org/yocto-project-compatible-registration
+
 
 Dependencies
 ============
@@ -20,7 +27,7 @@ This layer depends on:
   branch: master
 
   URI: git://git.yoctoproject.org/meta-intel
-  layers: intel
+  layers: meta-intel, meta-sugarbay
   branch: master
 
 
-- 
1.7.3.4

Re: [PATCH 0/6] meta-intel: README updates

[Kamble, Nitin A]

These commits are for both danny & master branches of meta-intel.

Thanks,
Nitin



> -----Original Message-----
> From: Kamble, Nitin A
> Sent: Tuesday, October 23, 2012 1:25 PM
> To: yocto@yoctoproject.org; Zanussi, Tom; Hart, Darren
> Cc: Kamble, Nitin A
> Subject: [PATCH 0/6] meta-intel: README updates
> 
> From: Nitin A Kamble <nitin.a.kamble@intel.com>
> 
> For the YP 1.3 release, README changes for the BSPs I am maintaining.
> 
> Thanks,
> Nitin
> 
> 
> The following changes since commit
> f502e7493694c487767f60df232055bc7b854e69:
> 
>   gstreamer-vaapi: add missing build dependencies (2012-10-23 07:43:46 -
> 0500)
> 
> are available in the git repository at:
>   git://git.yoctoproject.org/meta-intel-contrib nitin/misc
>   http://git.yoctoproject.org/cgit.cgi/meta-intel-contrib/log/?h=nitin/misc
> 
> Nitin A Kamble (6):
>   MAINTAINERS: corect pathname
>   chiefriver README: add WebTitle & Compliance information
>   crownbay README: add WebTitle & Compliance information
>   emenlow README: add WebTitle & Compliance information
>   jasperforest README: add WebTitle & Compliance information
>   sugarbay README: add WebTitle & Compliance information
> 
>  MAINTAINERS              |    2 +-
>  meta-chiefriver/README   |   10 +++++++++-
>  meta-crownbay/README     |   13 +++++++++++--
>  meta-emenlow/README      |   11 ++++++++++-
>  meta-jasperforest/README |   11 ++++++++++-
>  meta-sugarbay/README     |    9 ++++++++-
>  6 files changed, 49 insertions(+), 7 deletions(-)
> 
> --
> 1.7.3.4

Re: [PATCH 2/6] chiefriver README: add WebTitle & Compliance information

[Darren Hart]

On 10/23/2012 01:24 PM, nitin.a.kamble@intel.com wrote:
> From: Nitin A Kamble <nitin.a.kamble@intel.com>
> 
> The WebTitle will be used to publish the BSP on the Yocto Project Website.
> And adding the Yocto Project Compliance information for the 1.3 release.
> Also specifying all the layers used from meta-intel repository.
> 
> Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
> ---
>  meta-chiefriver/README |   10 +++++++++-
>  1 files changed, 9 insertions(+), 1 deletions(-)
> 
> diff --git a/meta-chiefriver/README b/meta-chiefriver/README
> index 7c47b02..7af1288 100644
> --- a/meta-chiefriver/README
> +++ b/meta-chiefriver/README
> @@ -6,6 +6,14 @@ The 'Chief River' platform consists of the Intel Ivy Bridge processor,
>  plus the Panther Point PCH.  This BSP assumes that the Ivy Bridge
>  integrated graphics are being used.
>  
> +WebTitle: Intel 3nd Generations Core Platforms: Core i3, i5, i7 (Ivy Bridge)

s/3nd/3rd/

Otherwise looks fine.

> +
> +
> +Compliance:
> +============
> +This BSP is compliant with Yocto Project as per requirements listed here:
> +http://www.yoctoproject.org/yocto-project-compatible-registration
> +
>  
>  Dependencies
>  ============
> @@ -20,7 +28,7 @@ This layer depends on:
>    branch: master
>  
>    URI: git://git.yoctoproject.org/meta-intel
> -  layers: intel
> +  layers: meta-intel, meta-chiefriver
>    branch: master
>  
>  
> 

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

Re: [PATCH 3/6] crownbay README: add WebTitle & Compliance information

[Darren Hart]

On 10/23/2012 01:24 PM, nitin.a.kamble@intel.com wrote:
> From: Nitin A Kamble <nitin.a.kamble@intel.com>
> 
> The WebTitle will be used to publish the BSP on the Yocto Project Website.
> And adding the Yocto Project Compliance information for the 1.3 release.
> Also specifying all the layers used from meta-intel repository.
> 
> Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
> ---
>  meta-crownbay/README |   13 +++++++++++--
>  1 files changed, 11 insertions(+), 2 deletions(-)
> 
> diff --git a/meta-crownbay/README b/meta-crownbay/README
> index 4bc9f31..3996a94 100644
> --- a/meta-crownbay/README
> +++ b/meta-crownbay/README
> @@ -2,13 +2,22 @@ This README file contains information on building the meta-crownbay
>  BSP layer, and booting the images contained in the /binary directory.
>  Please see the corresponding sections below for details.
>  
> -The Crown Bay platform consists of the Intel Atom Z6xx processor,
> +The Crown Bay platform consists of the Intel Atom E6xx processor,
>  plus the Intel EG20T Platform Controller Hub (Tunnel Creek + Topcliff).

How can we distinguish this from Queens Bay, which I would describe in
exactly the same terms?

--
Darren

>  
>  It also supports the E6xx embedded on-chip graphics via the Intel
>  Embedded Media and Graphics Driver (EMGD) 1.14 Driver.
>  
>  
> +WebTitle: Intel Atom E6xx processor with Intel EG20T Controller Hub development kit (crownbay)
> +
> +
> +Compliance:
> +============
> +This BSP is compliant with Yocto Project as per requirements listed here:
> +http://www.yoctoproject.org/yocto-project-compatible-registration
> +
> +
>  Dependencies
>  ============
>  
> @@ -22,7 +31,7 @@ This layer depends on:
>    branch: master
>  
>    URI: git://git.yoctoproject.org/meta-intel
> -  layers: intel
> +  layers: meta-intel, meta-crownbay
>    branch: master
>  
>  
> 

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

Re: [PATCH 6/6] sugarbay README: add WebTitle & Compliance information

[Darren Hart]

On 10/23/2012 01:24 PM, nitin.a.kamble@intel.com wrote:
> From: Nitin A Kamble <nitin.a.kamble@intel.com>
> 
> The WebTitle will be used to publish the BSP on the Yocto Project Website.
> And adding the Yocto Project Compliance information for the 1.3 release.
> Also specifying all the layers used from meta-intel repository.
> 
> Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
> ---
>  meta-sugarbay/README |    9 ++++++++-
>  1 files changed, 8 insertions(+), 1 deletions(-)
> 
> diff --git a/meta-sugarbay/README b/meta-sugarbay/README
> index c8a99d7..36da170 100644
> --- a/meta-sugarbay/README
> +++ b/meta-sugarbay/README
> @@ -6,6 +6,13 @@ The 'Sugar Bay' platform consists of the Intel Sandy Bridge processor,
>  plus the Cougar Point PCH (Q67 Express or B65 Express chipsets).  This
>  BSP assumes that the Sandy Bridge integrated graphics are being used.
>  
> +WebTitle: Intel 2nd Generations Core Platforms: Core i3, i5, i7 (Sandy Bridge)

Some places you used merged lowercase terms "crownbay" and other places
the capitalized expanded terms "Sandy Bridge". I don't know which is more
correct, but we should be consistent in our usage.

--
Darren

> +
> +Compliance:
> +============
> +This BSP is compliant with Yocto Project as per requirements listed here:
> +http://www.yoctoproject.org/yocto-project-compatible-registration
> +
>  
>  Dependencies
>  ============
> @@ -20,7 +27,7 @@ This layer depends on:
>    branch: master
>  
>    URI: git://git.yoctoproject.org/meta-intel
> -  layers: intel
> +  layers: meta-intel, meta-sugarbay
>    branch: master
>  
>  
> 

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

Re: [PATCH 3/6] crownbay README: add WebTitle & Compliance information

[Tom Zanussi]

On Tue, 2012-10-23 at 13:24 -0700, nitin.a.kamble@intel.com wrote:
> From: Nitin A Kamble <nitin.a.kamble@intel.com>
> 
> The WebTitle will be used to publish the BSP on the Yocto Project Website.
> And adding the Yocto Project Compliance information for the 1.3 release.
> Also specifying all the layers used from meta-intel repository.
> 
> Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
> ---
>  meta-crownbay/README |   13 +++++++++++--
>  1 files changed, 11 insertions(+), 2 deletions(-)
> 
> diff --git a/meta-crownbay/README b/meta-crownbay/README
> index 4bc9f31..3996a94 100644
> --- a/meta-crownbay/README
> +++ b/meta-crownbay/README
> @@ -2,13 +2,22 @@ This README file contains information on building the meta-crownbay
>  BSP layer, and booting the images contained in the /binary directory.
>  Please see the corresponding sections below for details.
>  
> -The Crown Bay platform consists of the Intel Atom Z6xx processor,
> +The Crown Bay platform consists of the Intel Atom E6xx processor,
>  plus the Intel EG20T Platform Controller Hub (Tunnel Creek + Topcliff).
>  
>  It also supports the E6xx embedded on-chip graphics via the Intel
>  Embedded Media and Graphics Driver (EMGD) 1.14 Driver.
>  
> 
> +WebTitle: Intel Atom E6xx processor with Intel EG20T Controller Hub development kit (crownbay)
> +

I'm not sure this kind of thing should be in the README since we can
have multiple downloadable BSPs per layer e.g. crownbay vs
crownbay-noemgd.  I suppose in keeping with the build system you could
have separate WebTitle_crownbay and WebTitle_crownbay-noemgd lines. ;-) 
(and it would be nice if you could get rid of the CamelCaps too)

Why not put this info in the machine.conf, where we already have fields
meant to be machine parseable e.g.

#@TYPE: Machine
#@NAME: crownbay

#@WEBTITLE: ...

Or maybe just use the exisiting #@DESCRIPTION for that...

> +
> +Compliance:
> +============

For consistency with the rest of the README, please remove the colon and
clean up the underlining.

Thanks,

Tom

> +This BSP is compliant with Yocto Project as per requirements listed here:
> +http://www.yoctoproject.org/yocto-project-compatible-registration
> +
> +
>  Dependencies
>  ============
>  
> @@ -22,7 +31,7 @@ This layer depends on:
>    branch: master
>  
>    URI: git://git.yoctoproject.org/meta-intel
> -  layers: intel
> +  layers: meta-intel, meta-crownbay
>    branch: master
>  
> 

Re: [PATCH 3/6] crownbay README: add WebTitle & Compliance information

[Darren Hart]

On 10/23/2012 02:16 PM, Tom Zanussi wrote:
> On Tue, 2012-10-23 at 13:24 -0700, nitin.a.kamble@intel.com wrote:

>> +WebTitle: Intel Atom E6xx processor with Intel EG20T Controller Hub development kit (crownbay)
>> +
> 
> I'm not sure this kind of thing should be in the README since we can
> have multiple downloadable BSPs per layer e.g. crownbay vs
> crownbay-noemgd.  I suppose in keeping with the build system you could
> have separate WebTitle_crownbay and WebTitle_crownbay-noemgd lines. ;-) 
> (and it would be nice if you could get rid of the CamelCaps too)
> 
> Why not put this info in the machine.conf, where we already have fields
> meant to be machine parseable e.g.
> 
> #@TYPE: Machine
> #@NAME: crownbay
> 
> #@WEBTITLE: ...

Oh much much better.

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

Re: [PATCH 3/6] crownbay README: add WebTitle & Compliance information

[Kamble, Nitin A]

> -----Original Message-----
> From: Zanussi, Tom
> Sent: Tuesday, October 23, 2012 2:16 PM
> To: Kamble, Nitin A
> Cc: yocto@yoctoproject.org; Hart, Darren
> Subject: Re: [PATCH 3/6] crownbay README: add WebTitle & Compliance
> information
> 
> On Tue, 2012-10-23 at 13:24 -0700, nitin.a.kamble@intel.com wrote:
> > From: Nitin A Kamble <nitin.a.kamble@intel.com>
> >
> > The WebTitle will be used to publish the BSP on the Yocto Project Website.
> > And adding the Yocto Project Compliance information for the 1.3 release.
> > Also specifying all the layers used from meta-intel repository.
> >
> > Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
> > ---
> >  meta-crownbay/README |   13 +++++++++++--
> >  1 files changed, 11 insertions(+), 2 deletions(-)
> >
> > diff --git a/meta-crownbay/README b/meta-crownbay/README index
> > 4bc9f31..3996a94 100644
> > --- a/meta-crownbay/README
> > +++ b/meta-crownbay/README
> > @@ -2,13 +2,22 @@ This README file contains information on building
> > the meta-crownbay  BSP layer, and booting the images contained in the
> /binary directory.
> >  Please see the corresponding sections below for details.
> >
> > -The Crown Bay platform consists of the Intel Atom Z6xx processor,
> > +The Crown Bay platform consists of the Intel Atom E6xx processor,
> >  plus the Intel EG20T Platform Controller Hub (Tunnel Creek + Topcliff).
> >
> >  It also supports the E6xx embedded on-chip graphics via the Intel
> > Embedded Media and Graphics Driver (EMGD) 1.14 Driver.
> >
> >
> > +WebTitle: Intel Atom E6xx processor with Intel EG20T Controller Hub
> > +development kit (crownbay)
> > +
> 
> I'm not sure this kind of thing should be in the README since we can have
> multiple downloadable BSPs per layer e.g. crownbay vs crownbay-noemgd.  I
> suppose in keeping with the build system you could have separate
> WebTitle_crownbay and WebTitle_crownbay-noemgd lines. ;-) (and it would
> be nice if you could get rid of the CamelCaps too)
> 
> Why not put this info in the machine.conf, where we already have fields
> meant to be machine parseable e.g.
> 
> #@TYPE: Machine
> #@NAME: crownbay
> 
> #@WEBTITLE: ...
> 
> Or maybe just use the exisiting #@DESCRIPTION for that...

For example in the current way the BSPs are published, this is shown on the YP website for crownbay 

Intel Atom Processor E660 with Intel Platform Controller Hub EG20T Development Kit
Version: 7.0 "Denzil"
Release date: 29 Jun 2012
Type: BSP
Download Links:
Crown Bay
Crown Bay no EMGD
Release Notes

So there is one BSP list item per h/w with multiple links to different BSP tarballs for the same hardware.
If we move the WebTitle in machine file, then we will have multiple items in the BSP list for the same hardware.
I am not sure which is better from the downloader's point of view. But this is worth considering for this change.

> 
> > +
> > +Compliance:
> > +============
> 
> For consistency with the rest of the README, please remove the colon and
> clean up the underlining.

Will do.

Thanks,
Nitin
> 
> Thanks,
> 
> Tom
> 
> > +This BSP is compliant with Yocto Project as per requirements listed here:
> > +http://www.yoctoproject.org/yocto-project-compatible-registration
> > +
> > +
> >  Dependencies
> >  ============
> >
> > @@ -22,7 +31,7 @@ This layer depends on:
> >    branch: master
> >
> >    URI: git://git.yoctoproject.org/meta-intel
> > -  layers: intel
> > +  layers: meta-intel, meta-crownbay
> >    branch: master
> >
> >
> 

Re: [PATCH 3/6] crownbay README: add WebTitle & Compliance information

[Tom Zanussi]

On Wed, 2012-10-24 at 11:06 -0500, Kamble, Nitin A wrote:
> 
> > -----Original Message-----
> > From: Zanussi, Tom
> > Sent: Tuesday, October 23, 2012 2:16 PM
> > To: Kamble, Nitin A
> > Cc: yocto@yoctoproject.org; Hart, Darren
> > Subject: Re: [PATCH 3/6] crownbay README: add WebTitle & Compliance
> > information
> > 
> > On Tue, 2012-10-23 at 13:24 -0700, nitin.a.kamble@intel.com wrote:
> > > From: Nitin A Kamble <nitin.a.kamble@intel.com>
> > >
> > > The WebTitle will be used to publish the BSP on the Yocto Project Website.
> > > And adding the Yocto Project Compliance information for the 1.3 release.
> > > Also specifying all the layers used from meta-intel repository.
> > >
> > > Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
> > > ---
> > >  meta-crownbay/README |   13 +++++++++++--
> > >  1 files changed, 11 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/meta-crownbay/README b/meta-crownbay/README index
> > > 4bc9f31..3996a94 100644
> > > --- a/meta-crownbay/README
> > > +++ b/meta-crownbay/README
> > > @@ -2,13 +2,22 @@ This README file contains information on building
> > > the meta-crownbay  BSP layer, and booting the images contained in the
> > /binary directory.
> > >  Please see the corresponding sections below for details.
> > >
> > > -The Crown Bay platform consists of the Intel Atom Z6xx processor,
> > > +The Crown Bay platform consists of the Intel Atom E6xx processor,
> > >  plus the Intel EG20T Platform Controller Hub (Tunnel Creek + Topcliff).
> > >
> > >  It also supports the E6xx embedded on-chip graphics via the Intel
> > > Embedded Media and Graphics Driver (EMGD) 1.14 Driver.
> > >
> > >
> > > +WebTitle: Intel Atom E6xx processor with Intel EG20T Controller Hub
> > > +development kit (crownbay)
> > > +
> > 
> > I'm not sure this kind of thing should be in the README since we can have
> > multiple downloadable BSPs per layer e.g. crownbay vs crownbay-noemgd.  I
> > suppose in keeping with the build system you could have separate
> > WebTitle_crownbay and WebTitle_crownbay-noemgd lines. ;-) (and it would
> > be nice if you could get rid of the CamelCaps too)
> > 
> > Why not put this info in the machine.conf, where we already have fields
> > meant to be machine parseable e.g.
> > 
> > #@TYPE: Machine
> > #@NAME: crownbay
> > 
> > #@WEBTITLE: ...
> > 
> > Or maybe just use the exisiting #@DESCRIPTION for that...
> 
> For example in the current way the BSPs are published, this is shown on the YP website for crownbay 
> 
> Intel Atom Processor E660 with Intel Platform Controller Hub EG20T Development Kit
> Version: 7.0 "Denzil"
> Release date: 29 Jun 2012
> Type: BSP
> Download Links:
> Crown Bay
> Crown Bay no EMGD
> Release Notes
> 
> So there is one BSP list item per h/w with multiple links to different BSP tarballs for the same hardware.
> If we move the WebTitle in machine file, then we will have multiple items in the BSP list for the same hardware.
> I am not sure which is better from the downloader's point of view. But this is worth considering for this change.
> 

Yeah, on the one hand if we have text that's the same for all BSPs in
the layer, it could go in the README for lack of a better common place.

But we should consider whether we want to lay things out as the crownbay
above, or more like the cedartrail, which has:

Intel® Atom™ Processor N2000 and D2000 Series-based Platform (CEDAR
TRAIL) with PowerVR Graphics

(there's no corresponding -nopvr version available, though I suspect
that's an oversight and would have been something like:

Intel® Atom™ Processor N2000 and D2000 Series-based Platform (CEDAR
TRAIL) with VESA Graphics

I'm not sure the field(s) need to map exactly to the page layout, but
all the information should be there to allow the page to be generated or
laid out by hand without having to ask questions, in either case.  Did
you have any idea as to how for example to distinguish between the emgd
and -noemgd versions (side note: there's nothing in the current entry
that tells the user what EMGD even is - should it at least be spelled
out in the title, or do we need a separate subtext element to describe
that?)

Tom

> > 
> > > +
> > > +Compliance:
> > > +============
> > 
> > For consistency with the rest of the README, please remove the colon and
> > clean up the underlining.
> 
> Will do.
> 
> Thanks,
> Nitin
> > 
> > Thanks,
> > 
> > Tom
> > 
> > > +This BSP is compliant with Yocto Project as per requirements listed here:
> > > +http://www.yoctoproject.org/yocto-project-compatible-registration
> > > +
> > > +
> > >  Dependencies
> > >  ============
> > >
> > > @@ -22,7 +31,7 @@ This layer depends on:
> > >    branch: master
> > >
> > >    URI: git://git.yoctoproject.org/meta-intel
> > > -  layers: intel
> > > +  layers: meta-intel, meta-crownbay
> > >    branch: master
> > >
> > >
> > 
> 

Re: [PATCH 3/6] crownbay README: add WebTitle & Compliance information

[Darren Hart]

On 10/24/2012 09:43 AM, Tom Zanussi wrote:
> On Wed, 2012-10-24 at 11:06 -0500, Kamble, Nitin A wrote:
>>
>>> -----Original Message-----
>>> From: Zanussi, Tom
>>> Sent: Tuesday, October 23, 2012 2:16 PM
>>> To: Kamble, Nitin A
>>> Cc: yocto@yoctoproject.org; Hart, Darren
>>> Subject: Re: [PATCH 3/6] crownbay README: add WebTitle & Compliance
>>> information
>>>
>>> On Tue, 2012-10-23 at 13:24 -0700, nitin.a.kamble@intel.com wrote:
>>>> From: Nitin A Kamble <nitin.a.kamble@intel.com>
>>>>
>>>> The WebTitle will be used to publish the BSP on the Yocto Project Website.
>>>> And adding the Yocto Project Compliance information for the 1.3 release.
>>>> Also specifying all the layers used from meta-intel repository.
>>>>
>>>> Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
>>>> ---
>>>>  meta-crownbay/README |   13 +++++++++++--
>>>>  1 files changed, 11 insertions(+), 2 deletions(-)
>>>>
>>>> diff --git a/meta-crownbay/README b/meta-crownbay/README index
>>>> 4bc9f31..3996a94 100644
>>>> --- a/meta-crownbay/README
>>>> +++ b/meta-crownbay/README
>>>> @@ -2,13 +2,22 @@ This README file contains information on building
>>>> the meta-crownbay  BSP layer, and booting the images contained in the
>>> /binary directory.
>>>>  Please see the corresponding sections below for details.
>>>>
>>>> -The Crown Bay platform consists of the Intel Atom Z6xx processor,
>>>> +The Crown Bay platform consists of the Intel Atom E6xx processor,
>>>>  plus the Intel EG20T Platform Controller Hub (Tunnel Creek + Topcliff).
>>>>
>>>>  It also supports the E6xx embedded on-chip graphics via the Intel
>>>> Embedded Media and Graphics Driver (EMGD) 1.14 Driver.
>>>>
>>>>
>>>> +WebTitle: Intel Atom E6xx processor with Intel EG20T Controller Hub
>>>> +development kit (crownbay)
>>>> +
>>>
>>> I'm not sure this kind of thing should be in the README since we can have
>>> multiple downloadable BSPs per layer e.g. crownbay vs crownbay-noemgd.  I
>>> suppose in keeping with the build system you could have separate
>>> WebTitle_crownbay and WebTitle_crownbay-noemgd lines. ;-) (and it would
>>> be nice if you could get rid of the CamelCaps too)
>>>
>>> Why not put this info in the machine.conf, where we already have fields
>>> meant to be machine parseable e.g.
>>>
>>> #@TYPE: Machine
>>> #@NAME: crownbay
>>>
>>> #@WEBTITLE: ...
>>>
>>> Or maybe just use the exisiting #@DESCRIPTION for that...
>>
>> For example in the current way the BSPs are published, this is shown on the YP website for crownbay 
>>
>> Intel Atom Processor E660 with Intel Platform Controller Hub EG20T Development Kit
>> Version: 7.0 "Denzil"
>> Release date: 29 Jun 2012
>> Type: BSP
>> Download Links:
>> Crown Bay
>> Crown Bay no EMGD
>> Release Notes
>>
>> So there is one BSP list item per h/w with multiple links to different BSP tarballs for the same hardware.
>> If we move the WebTitle in machine file, then we will have multiple items in the BSP list for the same hardware.
>> I am not sure which is better from the downloader's point of view. But this is worth considering for this change.
>>
> 
> Yeah, on the one hand if we have text that's the same for all BSPs in
> the layer, it could go in the README for lack of a better common place.
> 
> But we should consider whether we want to lay things out as the crownbay
> above, or more like the cedartrail, which has:
> 
> Intel® Atom™ Processor N2000 and D2000 Series-based Platform (CEDAR
> TRAIL) with PowerVR Graphics
> 
> (there's no corresponding -nopvr version available, though I suspect
> that's an oversight and would have been something like:
> 
> Intel® Atom™ Processor N2000 and D2000 Series-based Platform (CEDAR
> TRAIL) with VESA Graphics
> 
> I'm not sure the field(s) need to map exactly to the page layout, but
> all the information should be there to allow the page to be generated or
> laid out by hand without having to ask questions, in either case.  Did
> you have any idea as to how for example to distinguish between the emgd
> and -noemgd versions (side note: there's nothing in the current entry
> that tells the user what EMGD even is - should it at least be spelled
> out in the title, or do we need a separate subtext element to describe
> that?)

I like the Cedar Trail description with the graphics mentioned
explicitly. Doing this in the machine conf as Tom original suggested
makes perfect sense to me. If that means two entries for some machines,
that's preferable to me than extra complexity of subtexts, etc.

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

Re: [PATCH 3/6] crownbay README: add WebTitle & Compliance information

[Kamble, Nitin A]

> -----Original Message-----
> From: Zanussi, Tom
> Sent: Wednesday, October 24, 2012 9:43 AM
> To: Kamble, Nitin A
> Cc: yocto@yoctoproject.org; Hart, Darren
> Subject: Re: [PATCH 3/6] crownbay README: add WebTitle & Compliance
> information
> 
> On Wed, 2012-10-24 at 11:06 -0500, Kamble, Nitin A wrote:
> >
> > > -----Original Message-----
> > > From: Zanussi, Tom
> > > Sent: Tuesday, October 23, 2012 2:16 PM
> > > To: Kamble, Nitin A
> > > Cc: yocto@yoctoproject.org; Hart, Darren
> > > Subject: Re: [PATCH 3/6] crownbay README: add WebTitle & Compliance
> > > information
> > >
> > > On Tue, 2012-10-23 at 13:24 -0700, nitin.a.kamble@intel.com wrote:
> > > > From: Nitin A Kamble <nitin.a.kamble@intel.com>
> > > >
> > > > The WebTitle will be used to publish the BSP on the Yocto Project
> Website.
> > > > And adding the Yocto Project Compliance information for the 1.3
> release.
> > > > Also specifying all the layers used from meta-intel repository.
> > > >
> > > > Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
> > > > ---
> > > >  meta-crownbay/README |   13 +++++++++++--
> > > >  1 files changed, 11 insertions(+), 2 deletions(-)
> > > >
> > > > diff --git a/meta-crownbay/README b/meta-crownbay/README index
> > > > 4bc9f31..3996a94 100644
> > > > --- a/meta-crownbay/README
> > > > +++ b/meta-crownbay/README
> > > > @@ -2,13 +2,22 @@ This README file contains information on
> > > > building the meta-crownbay  BSP layer, and booting the images
> > > > contained in the
> > > /binary directory.
> > > >  Please see the corresponding sections below for details.
> > > >
> > > > -The Crown Bay platform consists of the Intel Atom Z6xx processor,
> > > > +The Crown Bay platform consists of the Intel Atom E6xx processor,
> > > >  plus the Intel EG20T Platform Controller Hub (Tunnel Creek + Topcliff).
> > > >
> > > >  It also supports the E6xx embedded on-chip graphics via the Intel
> > > > Embedded Media and Graphics Driver (EMGD) 1.14 Driver.
> > > >
> > > >
> > > > +WebTitle: Intel Atom E6xx processor with Intel EG20T Controller
> > > > +Hub development kit (crownbay)
> > > > +
> > >
> > > I'm not sure this kind of thing should be in the README since we can
> > > have multiple downloadable BSPs per layer e.g. crownbay vs
> > > crownbay-noemgd.  I suppose in keeping with the build system you
> > > could have separate WebTitle_crownbay and WebTitle_crownbay-
> noemgd
> > > lines. ;-) (and it would be nice if you could get rid of the
> > > CamelCaps too)
> > >
> > > Why not put this info in the machine.conf, where we already have
> > > fields meant to be machine parseable e.g.
> > >
> > > #@TYPE: Machine
> > > #@NAME: crownbay
> > >
> > > #@WEBTITLE: ...
> > >
> > > Or maybe just use the exisiting #@DESCRIPTION for that...
> >
> > For example in the current way the BSPs are published, this is shown
> > on the YP website for crownbay
> >
> > Intel Atom Processor E660 with Intel Platform Controller Hub EG20T
> > Development Kit
> > Version: 7.0 "Denzil"
> > Release date: 29 Jun 2012
> > Type: BSP
> > Download Links:
> > Crown Bay
> > Crown Bay no EMGD
> > Release Notes
> >
> > So there is one BSP list item per h/w with multiple links to different BSP
> tarballs for the same hardware.
> > If we move the WebTitle in machine file, then we will have multiple items
> in the BSP list for the same hardware.
> > I am not sure which is better from the downloader's point of view. But this
> is worth considering for this change.
> >
> 
> Yeah, on the one hand if we have text that's the same for all BSPs in the
> layer, it could go in the README for lack of a better common place.
> 
> But we should consider whether we want to lay things out as the crownbay
> above, or more like the cedartrail, which has:
> 
> Intel® Atom™ Processor N2000 and D2000 Series-based Platform (CEDAR
> TRAIL) with PowerVR Graphics
> 
> (there's no corresponding -nopvr version available, though I suspect that's an
> oversight and would have been something like:
> 
> Intel® Atom™ Processor N2000 and D2000 Series-based Platform (CEDAR
> TRAIL) with VESA Graphics
> 
> I'm not sure the field(s) need to map exactly to the page layout, but all the
> information should be there to allow the page to be generated or laid out by
> hand without having to ask questions, in either case.  Did you have any idea
> as to how for example to distinguish between the emgd and -noemgd
> versions (side note: there's nothing in the current entry that tells the user
> what EMGD even is - should it at least be spelled out in the title, or do we
> need a separate subtext element to describe
> that?)
> 

I think for crownbay we should add in the title "with proprietary IEMGD accelerated graphics drivers", and for crownbay-noemgd we should add "with open source VESA graphics drivers" 
And then these can go in the machine.conf files. It will make our list of BSPs bigger, but it will be clearer to people, who want to download a BSP from YP site. 
 Shall we add these title requirements in the BSP standard format, so that other BSP provider's follow the same practice?

Nitin

> Tom
> 
> > >
> > > > +
> > > > +Compliance:
> > > > +============
> > >
> > > For consistency with the rest of the README, please remove the colon
> > > and clean up the underlining.
> >
> > Will do.
> >
> > Thanks,
> > Nitin
> > >
> > > Thanks,
> > >
> > > Tom
> > >
> > > > +This BSP is compliant with Yocto Project as per requirements listed
> here:
> > > > +http://www.yoctoproject.org/yocto-project-compatible-registration
> > > > +
> > > > +
> > > >  Dependencies
> > > >  ============
> > > >
> > > > @@ -22,7 +31,7 @@ This layer depends on:
> > > >    branch: master
> > > >
> > > >    URI: git://git.yoctoproject.org/meta-intel
> > > > -  layers: intel
> > > > +  layers: meta-intel, meta-crownbay
> > > >    branch: master
> > > >
> > > >
> > >
> >
> 

Re: [PATCH 3/6] crownbay README: add WebTitle & Compliance information

[Sean Liming]

> -----Original Message-----
> From: yocto-bounces@yoctoproject.org [mailto:yocto-
> bounces@yoctoproject.org] On Behalf Of Tom Zanussi
> Sent: Wednesday, October 24, 2012 9:43 AM
> To: Kamble, Nitin A
> Cc: yocto@yoctoproject.org; Hart, Darren
> Subject: Re: [yocto] [PATCH 3/6] crownbay README: add WebTitle &
> Compliance information
> 
> On Wed, 2012-10-24 at 11:06 -0500, Kamble, Nitin A wrote:
> >
> > > -----Original Message-----
> > > From: Zanussi, Tom
> > > Sent: Tuesday, October 23, 2012 2:16 PM
> > > To: Kamble, Nitin A
> > > Cc: yocto@yoctoproject.org; Hart, Darren
> > > Subject: Re: [PATCH 3/6] crownbay README: add WebTitle & Compliance
> > > information
> > >
> > > On Tue, 2012-10-23 at 13:24 -0700, nitin.a.kamble@intel.com wrote:
> > > > From: Nitin A Kamble <nitin.a.kamble@intel.com>
> > > >
> > > > The WebTitle will be used to publish the BSP on the Yocto Project
> Website.
> > > > And adding the Yocto Project Compliance information for the 1.3
> release.
> > > > Also specifying all the layers used from meta-intel repository.
> > > >
> > > > Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
> > > > ---
> > > >  meta-crownbay/README |   13 +++++++++++--
> > > >  1 files changed, 11 insertions(+), 2 deletions(-)
> > > >
> > > > diff --git a/meta-crownbay/README b/meta-crownbay/README index
> > > > 4bc9f31..3996a94 100644
> > > > --- a/meta-crownbay/README
> > > > +++ b/meta-crownbay/README
> > > > @@ -2,13 +2,22 @@ This README file contains information on
> > > > building the meta-crownbay  BSP layer, and booting the images
> > > > contained in the
> > > /binary directory.
> > > >  Please see the corresponding sections below for details.
> > > >
> > > > -The Crown Bay platform consists of the Intel Atom Z6xx processor,
> > > > +The Crown Bay platform consists of the Intel Atom E6xx processor,
> > > >  plus the Intel EG20T Platform Controller Hub (Tunnel Creek + Topcliff).
> > > >
> > > >  It also supports the E6xx embedded on-chip graphics via the Intel
> > > > Embedded Media and Graphics Driver (EMGD) 1.14 Driver.
> > > >
> > > >
> > > > +WebTitle: Intel Atom E6xx processor with Intel EG20T Controller
> > > > +Hub development kit (crownbay)
> > > > +
> > >
> > > I'm not sure this kind of thing should be in the README since we can
> > > have multiple downloadable BSPs per layer e.g. crownbay vs
> > > crownbay-noemgd.  I suppose in keeping with the build system you
> > > could have separate WebTitle_crownbay and WebTitle_crownbay-
> noemgd
> > > lines. ;-) (and it would be nice if you could get rid of the
> > > CamelCaps too)
> > >
> > > Why not put this info in the machine.conf, where we already have
> > > fields meant to be machine parseable e.g.
> > >
> > > #@TYPE: Machine
> > > #@NAME: crownbay
> > >
> > > #@WEBTITLE: ...
> > >
> > > Or maybe just use the exisiting #@DESCRIPTION for that...
> >
> > For example in the current way the BSPs are published, this is shown
> > on the YP website for crownbay
> >
> > Intel Atom Processor E660 with Intel Platform Controller Hub EG20T
> > Development Kit
> > Version: 7.0 "Denzil"
> > Release date: 29 Jun 2012
> > Type: BSP
> > Download Links:
> > Crown Bay
> > Crown Bay no EMGD
> > Release Notes
> >
> > So there is one BSP list item per h/w with multiple links to different BSP
> tarballs for the same hardware.
> > If we move the WebTitle in machine file, then we will have multiple items
> in the BSP list for the same hardware.
> > I am not sure which is better from the downloader's point of view. But this
> is worth considering for this change.
> >
> 
> Yeah, on the one hand if we have text that's the same for all BSPs in the
> layer, it could go in the README for lack of a better common place.
> 
> But we should consider whether we want to lay things out as the crownbay
> above, or more like the cedartrail, which has:
> 
> Intel® Atom™ Processor N2000 and D2000 Series-based Platform (CEDAR
> TRAIL) with PowerVR Graphics
> 
> (there's no corresponding -nopvr version available, though I suspect that's an
> oversight and would have been something like:
> 
> Intel® Atom™ Processor N2000 and D2000 Series-based Platform (CEDAR
> TRAIL) with VESA Graphics
> 
> I'm not sure the field(s) need to map exactly to the page layout, but all the
> information should be there to allow the page to be generated or laid out by
> hand without having to ask questions, in either case.  Did you have any idea
> as to how for example to distinguish between the emgd and -noemgd
> versions (side note: there's nothing in the current entry that tells the user
> what EMGD even is - should it at least be spelled out in the title, or do we
> need a separate subtext element to describe
> that?)
> 
> Tom
> 

I am working with CEDAR trail and Crown Bay-like (SYS940X-ECX) systems. For Crown Bay, it is a little confusing to know which tar ball to download. It would be clearer to have one BSP with an option switch to enable the video. 

Also, it would help to know how the EMGD has been configure in the BSP and for what output ports. Having worked with EMGD there are many options. For the SYS940X-ECX, the video driver (VGA-output) doesn't load so X doesn't start. It would be nice to use EMGD to configure this myself and then add the driver, but if this can already be down in the configuration file, it is not clear how to do this.

Regards,

Sean Liming
Owner
Annabooks
Tel: 714-970-7523 / Cell: 858-774-3176



> > >
> > > > +
> > > > +Compliance:
> > > > +============
> > >
> > > For consistency with the rest of the README, please remove the colon
> > > and clean up the underlining.
> >
> > Will do.
> >
> > Thanks,
> > Nitin
> > >
> > > Thanks,
> > >
> > > Tom
> > >
> > > > +This BSP is compliant with Yocto Project as per requirements listed
> here:
> > > > +http://www.yoctoproject.org/yocto-project-compatible-registration
> > > > +
> > > > +
> > > >  Dependencies
> > > >  ============
> > > >
> > > > @@ -22,7 +31,7 @@ This layer depends on:
> > > >    branch: master
> > > >
> > > >    URI: git://git.yoctoproject.org/meta-intel
> > > > -  layers: intel
> > > > +  layers: meta-intel, meta-crownbay
> > > >    branch: master
> > > >
> > > >
> > >
> >
> 
> 
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

Re: [PATCH 3/6] crownbay README: add WebTitle & Compliance information

[Kamble, Nitin A]

> -----Original Message-----
> From: yocto-bounces@yoctoproject.org [mailto:yocto-
> bounces@yoctoproject.org] On Behalf Of Sean Liming
> Sent: Wednesday, October 24, 2012 11:16 AM
> To: yocto@yoctoproject.org
> Subject: Re: [yocto] [PATCH 3/6] crownbay README: add WebTitle &
> Compliance information
> 
> > -----Original Message-----
> > From: yocto-bounces@yoctoproject.org [mailto:yocto-
> > bounces@yoctoproject.org] On Behalf Of Tom Zanussi
> > Sent: Wednesday, October 24, 2012 9:43 AM
> > To: Kamble, Nitin A
> > Cc: yocto@yoctoproject.org; Hart, Darren
> > Subject: Re: [yocto] [PATCH 3/6] crownbay README: add WebTitle &
> > Compliance information
> >
> > On Wed, 2012-10-24 at 11:06 -0500, Kamble, Nitin A wrote:
> > >
> > > > -----Original Message-----
> > > > From: Zanussi, Tom
> > > > Sent: Tuesday, October 23, 2012 2:16 PM
> > > > To: Kamble, Nitin A
> > > > Cc: yocto@yoctoproject.org; Hart, Darren
> > > > Subject: Re: [PATCH 3/6] crownbay README: add WebTitle &
> > > > Compliance information
> > > >
> > > > On Tue, 2012-10-23 at 13:24 -0700, nitin.a.kamble@intel.com wrote:
> > > > > From: Nitin A Kamble <nitin.a.kamble@intel.com>
> > > > >
> > > > > The WebTitle will be used to publish the BSP on the Yocto
> > > > > Project
> > Website.
> > > > > And adding the Yocto Project Compliance information for the 1.3
> > release.
> > > > > Also specifying all the layers used from meta-intel repository.
> > > > >
> > > > > Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
> > > > > ---
> > > > >  meta-crownbay/README |   13 +++++++++++--
> > > > >  1 files changed, 11 insertions(+), 2 deletions(-)
> > > > >
> > > > > diff --git a/meta-crownbay/README b/meta-crownbay/README
> index
> > > > > 4bc9f31..3996a94 100644
> > > > > --- a/meta-crownbay/README
> > > > > +++ b/meta-crownbay/README
> > > > > @@ -2,13 +2,22 @@ This README file contains information on
> > > > > building the meta-crownbay  BSP layer, and booting the images
> > > > > contained in the
> > > > /binary directory.
> > > > >  Please see the corresponding sections below for details.
> > > > >
> > > > > -The Crown Bay platform consists of the Intel Atom Z6xx
> > > > > processor,
> > > > > +The Crown Bay platform consists of the Intel Atom E6xx
> > > > > +processor,
> > > > >  plus the Intel EG20T Platform Controller Hub (Tunnel Creek +
> Topcliff).
> > > > >
> > > > >  It also supports the E6xx embedded on-chip graphics via the
> > > > > Intel Embedded Media and Graphics Driver (EMGD) 1.14 Driver.
> > > > >
> > > > >
> > > > > +WebTitle: Intel Atom E6xx processor with Intel EG20T Controller
> > > > > +Hub development kit (crownbay)
> > > > > +
> > > >
> > > > I'm not sure this kind of thing should be in the README since we
> > > > can have multiple downloadable BSPs per layer e.g. crownbay vs
> > > > crownbay-noemgd.  I suppose in keeping with the build system you
> > > > could have separate WebTitle_crownbay and WebTitle_crownbay-
> > noemgd
> > > > lines. ;-) (and it would be nice if you could get rid of the
> > > > CamelCaps too)
> > > >
> > > > Why not put this info in the machine.conf, where we already have
> > > > fields meant to be machine parseable e.g.
> > > >
> > > > #@TYPE: Machine
> > > > #@NAME: crownbay
> > > >
> > > > #@WEBTITLE: ...
> > > >
> > > > Or maybe just use the exisiting #@DESCRIPTION for that...
> > >
> > > For example in the current way the BSPs are published, this is shown
> > > on the YP website for crownbay
> > >
> > > Intel Atom Processor E660 with Intel Platform Controller Hub EG20T
> > > Development Kit
> > > Version: 7.0 "Denzil"
> > > Release date: 29 Jun 2012
> > > Type: BSP
> > > Download Links:
> > > Crown Bay
> > > Crown Bay no EMGD
> > > Release Notes
> > >
> > > So there is one BSP list item per h/w with multiple links to
> > > different BSP
> > tarballs for the same hardware.
> > > If we move the WebTitle in machine file, then we will have multiple
> > > items
> > in the BSP list for the same hardware.
> > > I am not sure which is better from the downloader's point of view.
> > > But this
> > is worth considering for this change.
> > >
> >
> > Yeah, on the one hand if we have text that's the same for all BSPs in
> > the layer, it could go in the README for lack of a better common place.
> >
> > But we should consider whether we want to lay things out as the
> > crownbay above, or more like the cedartrail, which has:
> >
> > Intel® Atom™ Processor N2000 and D2000 Series-based Platform (CEDAR
> > TRAIL) with PowerVR Graphics
> >
> > (there's no corresponding -nopvr version available, though I suspect
> > that's an oversight and would have been something like:
> >
> > Intel® Atom™ Processor N2000 and D2000 Series-based Platform (CEDAR
> > TRAIL) with VESA Graphics
> >
> > I'm not sure the field(s) need to map exactly to the page layout, but
> > all the information should be there to allow the page to be generated
> > or laid out by hand without having to ask questions, in either case.
> > Did you have any idea as to how for example to distinguish between the
> > emgd and -noemgd versions (side note: there's nothing in the current
> > entry that tells the user what EMGD even is - should it at least be
> > spelled out in the title, or do we need a separate subtext element to
> > describe
> > that?)
> >
> > Tom
> >
> 
> I am working with CEDAR trail and Crown Bay-like (SYS940X-ECX) systems. For
> Crown Bay, it is a little confusing to know which tar ball to download. It would
> be clearer to have one BSP with an option switch to enable the video.
> 
> Also, it would help to know how the EMGD has been configure in the BSP
> and for what output ports. Having worked with EMGD there are many
> options. For the SYS940X-ECX, the video driver (VGA-output) doesn't load so
> X doesn't start. It would be nice to use EMGD to configure this myself and
> then add the driver, but if this can already be down in the configuration file, it
> is not clear how to do this.
> 
> Regards,
> 
> Sean Liming
> Owner
> Annabooks
> Tel: 714-970-7523 / Cell: 858-774-3176

Sean,
  We have another BSP called sys940x I guess that would be better match for you than the crownbay BSP. And you can look at the EMGD documentation at their website for instructions on how to configure it. http://www.intel.com/p/en_US/embedded/hwsw/software/emgd

Thanks,
Nitin

> 
> 
> 
> > > >
> > > > > +
> > > > > +Compliance:
> > > > > +============
> > > >
> > > > For consistency with the rest of the README, please remove the
> > > > colon and clean up the underlining.
> > >
> > > Will do.
> > >
> > > Thanks,
> > > Nitin
> > > >
> > > > Thanks,
> > > >
> > > > Tom
> > > >
> > > > > +This BSP is compliant with Yocto Project as per requirements
> > > > > +listed
> > here:
> > > > > +http://www.yoctoproject.org/yocto-project-compatible-registrati
> > > > > +on
> > > > > +
> > > > > +
> > > > >  Dependencies
> > > > >  ============
> > > > >
> > > > > @@ -22,7 +31,7 @@ This layer depends on:
> > > > >    branch: master
> > > > >
> > > > >    URI: git://git.yoctoproject.org/meta-intel
> > > > > -  layers: intel
> > > > > +  layers: meta-intel, meta-crownbay
> > > > >    branch: master
> > > > >
> > > > >
> > > >
> > >
> >
> >
> > _______________________________________________
> > yocto mailing list
> > yocto@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
> 
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

Re: [PATCH 3/6] crownbay README: add WebTitle & Compliance information

[Sean Liming]

> -----Original Message-----
> From: Sean Liming [mailto:sean.liming@annabooks.com]
> Sent: Wednesday, October 24, 2012 11:51 AM
> To: 'Kamble, Nitin A'
> Subject: RE: [yocto] [PATCH 3/6] crownbay README: add WebTitle &
> Compliance information
> 
> 
> 
> 
> > -----Original Message-----
> > From: Kamble, Nitin A [mailto:nitin.a.kamble@intel.com]
> > Sent: Wednesday, October 24, 2012 11:38 AM
> > To: Sean Liming; yocto@yoctoproject.org
> > Subject: RE: [yocto] [PATCH 3/6] crownbay README: add WebTitle &
> > Compliance information
> >
> >
> >
> > > -----Original Message-----
> > > From: yocto-bounces@yoctoproject.org [mailto:yocto-
> > > bounces@yoctoproject.org] On Behalf Of Sean Liming
> > > Sent: Wednesday, October 24, 2012 11:16 AM
> > > To: yocto@yoctoproject.org
> > > Subject: Re: [yocto] [PATCH 3/6] crownbay README: add WebTitle &
> > > Compliance information
> > >
> > > > -----Original Message-----
> > > > From: yocto-bounces@yoctoproject.org [mailto:yocto-
> > > > bounces@yoctoproject.org] On Behalf Of Tom Zanussi
> > > > Sent: Wednesday, October 24, 2012 9:43 AM
> > > > To: Kamble, Nitin A
> > > > Cc: yocto@yoctoproject.org; Hart, Darren
> > > > Subject: Re: [yocto] [PATCH 3/6] crownbay README: add WebTitle &
> > > > Compliance information
> > > >
> > > > On Wed, 2012-10-24 at 11:06 -0500, Kamble, Nitin A wrote:
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Zanussi, Tom
> > > > > > Sent: Tuesday, October 23, 2012 2:16 PM
> > > > > > To: Kamble, Nitin A
> > > > > > Cc: yocto@yoctoproject.org; Hart, Darren
> > > > > > Subject: Re: [PATCH 3/6] crownbay README: add WebTitle &
> > > > > > Compliance information
> > > > > >
> > > > > > On Tue, 2012-10-23 at 13:24 -0700, nitin.a.kamble@intel.com wrote:
> > > > > > > From: Nitin A Kamble <nitin.a.kamble@intel.com>
> > > > > > >
> > > > > > > The WebTitle will be used to publish the BSP on the Yocto
> > > > > > > Project
> > > > Website.
> > > > > > > And adding the Yocto Project Compliance information for the
> > > > > > > 1.3
> > > > release.
> > > > > > > Also specifying all the layers used from meta-intel repository.
> > > > > > >
> > > > > > > Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
> > > > > > > ---
> > > > > > >  meta-crownbay/README |   13 +++++++++++--
> > > > > > >  1 files changed, 11 insertions(+), 2 deletions(-)
> > > > > > >
> > > > > > > diff --git a/meta-crownbay/README b/meta-crownbay/README
> > > index
> > > > > > > 4bc9f31..3996a94 100644
> > > > > > > --- a/meta-crownbay/README
> > > > > > > +++ b/meta-crownbay/README
> > > > > > > @@ -2,13 +2,22 @@ This README file contains information on
> > > > > > > building the meta-crownbay  BSP layer, and booting the
> > > > > > > images contained in the
> > > > > > /binary directory.
> > > > > > >  Please see the corresponding sections below for details.
> > > > > > >
> > > > > > > -The Crown Bay platform consists of the Intel Atom Z6xx
> > > > > > > processor,
> > > > > > > +The Crown Bay platform consists of the Intel Atom E6xx
> > > > > > > +processor,
> > > > > > >  plus the Intel EG20T Platform Controller Hub (Tunnel Creek
> > > > > > > +
> > > Topcliff).
> > > > > > >
> > > > > > >  It also supports the E6xx embedded on-chip graphics via the
> > > > > > > Intel Embedded Media and Graphics Driver (EMGD) 1.14 Driver.
> > > > > > >
> > > > > > >
> > > > > > > +WebTitle: Intel Atom E6xx processor with Intel EG20T
> > > > > > > +Controller Hub development kit (crownbay)
> > > > > > > +
> > > > > >
> > > > > > I'm not sure this kind of thing should be in the README since
> > > > > > we can have multiple downloadable BSPs per layer e.g. crownbay
> > > > > > vs crownbay-noemgd.  I suppose in keeping with the build
> > > > > > system you could have separate WebTitle_crownbay and
> > > > > > WebTitle_crownbay-
> > > > noemgd
> > > > > > lines. ;-) (and it would be nice if you could get rid of the
> > > > > > CamelCaps too)
> > > > > >
> > > > > > Why not put this info in the machine.conf, where we already
> > > > > > have fields meant to be machine parseable e.g.
> > > > > >
> > > > > > #@TYPE: Machine
> > > > > > #@NAME: crownbay
> > > > > >
> > > > > > #@WEBTITLE: ...
> > > > > >
> > > > > > Or maybe just use the exisiting #@DESCRIPTION for that...
> > > > >
> > > > > For example in the current way the BSPs are published, this is
> > > > > shown on the YP website for crownbay
> > > > >
> > > > > Intel Atom Processor E660 with Intel Platform Controller Hub
> > > > > EG20T Development Kit
> > > > > Version: 7.0 "Denzil"
> > > > > Release date: 29 Jun 2012
> > > > > Type: BSP
> > > > > Download Links:
> > > > > Crown Bay
> > > > > Crown Bay no EMGD
> > > > > Release Notes
> > > > >
> > > > > So there is one BSP list item per h/w with multiple links to
> > > > > different BSP
> > > > tarballs for the same hardware.
> > > > > If we move the WebTitle in machine file, then we will have
> > > > > multiple items
> > > > in the BSP list for the same hardware.
> > > > > I am not sure which is better from the downloader's point of view.
> > > > > But this
> > > > is worth considering for this change.
> > > > >
> > > >
> > > > Yeah, on the one hand if we have text that's the same for all BSPs
> > > > in the layer, it could go in the README for lack of a better common
> place.
> > > >
> > > > But we should consider whether we want to lay things out as the
> > > > crownbay above, or more like the cedartrail, which has:
> > > >
> > > > Intel® Atom™ Processor N2000 and D2000 Series-based Platform
> > > > (CEDAR
> > > > TRAIL) with PowerVR Graphics
> > > >
> > > > (there's no corresponding -nopvr version available, though I
> > > > suspect that's an oversight and would have been something like:
> > > >
> > > > Intel® Atom™ Processor N2000 and D2000 Series-based Platform
> > > > (CEDAR
> > > > TRAIL) with VESA Graphics
> > > >
> > > > I'm not sure the field(s) need to map exactly to the page layout,
> > > > but all the information should be there to allow the page to be
> > > > generated or laid out by hand without having to ask questions, in
> > > > either
> > case.
> > > > Did you have any idea as to how for example to distinguish between
> > > > the emgd and -noemgd versions (side note: there's nothing in the
> > > > current entry that tells the user what EMGD even is - should it at
> > > > least be spelled out in the title, or do we need a separate
> > > > subtext element to describe
> > > > that?)
> > > >
> > > > Tom
> > > >
> > >
> > > I am working with CEDAR trail and Crown Bay-like (SYS940X-ECX)
> > > systems. For Crown Bay, it is a little confusing to know which tar
> > > ball to download. It would be clearer to have one BSP with an option
> > > switch
> > to enable the video.
> > >
> > > Also, it would help to know how the EMGD has been configure in the
> > > BSP and for what output ports. Having worked with EMGD there are
> > > many options. For the SYS940X-ECX, the video driver (VGA-output)
> > > doesn't load so X doesn't start. It would be nice to use EMGD to
> > > configure this myself and then add the driver, but if this can
> > > already be down in the configuration file, it is not clear how to do this.
> > >
> > > Regards,
> > >
> > > Sean Liming
> > > Owner
> > > Annabooks
> > > Tel: 714-970-7523 / Cell: 858-774-3176
> >
> > Sean,
> >   We have another BSP called sys940x I guess that would be better
> > match for you than the crownbay BSP. And you can look at the EMGD
> > documentation at their website for instructions on how to configure it.
> > http://www.intel.com/p/en_US/embedded/hwsw/software/emgd
> >
> > Thanks,
> > Nitin
> >
 Nitin,
 
 I have been testing that one too. Same result with the video.  The only way
 to test it was to download the 1.3 release candidates.  The release candidate
 is looking good BTW. Will the sys940x be a standard BSP, or left in the
 background for download? Is there a way to download for a specific release?
 
 Regards,
 
 Sean Liming
> > >
> > >
> > > > > >
> > > > > > > +
> > > > > > > +Compliance:
> > > > > > > +============
> > > > > >
> > > > > > For consistency with the rest of the README, please remove the
> > > > > > colon and clean up the underlining.
> > > > >
> > > > > Will do.
> > > > >
> > > > > Thanks,
> > > > > Nitin
> > > > > >
> > > > > > Thanks,
> > > > > >
> > > > > > Tom
> > > > > >
> > > > > > > +This BSP is compliant with Yocto Project as per
> > > > > > > +requirements listed
> > > > here:
> > > > > > > +http://www.yoctoproject.org/yocto-project-compatible-regist
> > > > > > > +ra
> > > > > > > +ti
> > > > > > > +on
> > > > > > > +
> > > > > > > +
> > > > > > >  Dependencies
> > > > > > >  ============
> > > > > > >
> > > > > > > @@ -22,7 +31,7 @@ This layer depends on:
> > > > > > >    branch: master
> > > > > > >
> > > > > > >    URI: git://git.yoctoproject.org/meta-intel
> > > > > > > -  layers: intel
> > > > > > > +  layers: meta-intel, meta-crownbay
> > > > > > >    branch: master
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > _______________________________________________
> > > > yocto mailing list
> > > > yocto@yoctoproject.org
> > > > https://lists.yoctoproject.org/listinfo/yocto
> > >
> > > _______________________________________________
> > > yocto mailing list
> > > yocto@yoctoproject.org
> > > https://lists.yoctoproject.org/listinfo/yocto

Re: [PATCH 3/6] crownbay README: add WebTitle & Compliance information

[Tom Zanussi]

On Wed, 2012-10-24 at 11:15 -0700, Sean Liming wrote:
> > -----Original Message-----
> > From: yocto-bounces@yoctoproject.org [mailto:yocto-
> > bounces@yoctoproject.org] On Behalf Of Tom Zanussi
> > Sent: Wednesday, October 24, 2012 9:43 AM
> > To: Kamble, Nitin A
> > Cc: yocto@yoctoproject.org; Hart, Darren
> > Subject: Re: [yocto] [PATCH 3/6] crownbay README: add WebTitle &
> > Compliance information
> > 
> > On Wed, 2012-10-24 at 11:06 -0500, Kamble, Nitin A wrote:
> > >
> > > > -----Original Message-----
> > > > From: Zanussi, Tom
> > > > Sent: Tuesday, October 23, 2012 2:16 PM
> > > > To: Kamble, Nitin A
> > > > Cc: yocto@yoctoproject.org; Hart, Darren
> > > > Subject: Re: [PATCH 3/6] crownbay README: add WebTitle & Compliance
> > > > information
> > > >
> > > > On Tue, 2012-10-23 at 13:24 -0700, nitin.a.kamble@intel.com wrote:
> > > > > From: Nitin A Kamble <nitin.a.kamble@intel.com>
> > > > >
> > > > > The WebTitle will be used to publish the BSP on the Yocto Project
> > Website.
> > > > > And adding the Yocto Project Compliance information for the 1.3
> > release.
> > > > > Also specifying all the layers used from meta-intel repository.
> > > > >
> > > > > Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
> > > > > ---
> > > > >  meta-crownbay/README |   13 +++++++++++--
> > > > >  1 files changed, 11 insertions(+), 2 deletions(-)
> > > > >
> > > > > diff --git a/meta-crownbay/README b/meta-crownbay/README index
> > > > > 4bc9f31..3996a94 100644
> > > > > --- a/meta-crownbay/README
> > > > > +++ b/meta-crownbay/README
> > > > > @@ -2,13 +2,22 @@ This README file contains information on
> > > > > building the meta-crownbay  BSP layer, and booting the images
> > > > > contained in the
> > > > /binary directory.
> > > > >  Please see the corresponding sections below for details.
> > > > >
> > > > > -The Crown Bay platform consists of the Intel Atom Z6xx processor,
> > > > > +The Crown Bay platform consists of the Intel Atom E6xx processor,
> > > > >  plus the Intel EG20T Platform Controller Hub (Tunnel Creek + Topcliff).
> > > > >
> > > > >  It also supports the E6xx embedded on-chip graphics via the Intel
> > > > > Embedded Media and Graphics Driver (EMGD) 1.14 Driver.
> > > > >
> > > > >
> > > > > +WebTitle: Intel Atom E6xx processor with Intel EG20T Controller
> > > > > +Hub development kit (crownbay)
> > > > > +
> > > >
> > > > I'm not sure this kind of thing should be in the README since we can
> > > > have multiple downloadable BSPs per layer e.g. crownbay vs
> > > > crownbay-noemgd.  I suppose in keeping with the build system you
> > > > could have separate WebTitle_crownbay and WebTitle_crownbay-
> > noemgd
> > > > lines. ;-) (and it would be nice if you could get rid of the
> > > > CamelCaps too)
> > > >
> > > > Why not put this info in the machine.conf, where we already have
> > > > fields meant to be machine parseable e.g.
> > > >
> > > > #@TYPE: Machine
> > > > #@NAME: crownbay
> > > >
> > > > #@WEBTITLE: ...
> > > >
> > > > Or maybe just use the exisiting #@DESCRIPTION for that...
> > >
> > > For example in the current way the BSPs are published, this is shown
> > > on the YP website for crownbay
> > >
> > > Intel Atom Processor E660 with Intel Platform Controller Hub EG20T
> > > Development Kit
> > > Version: 7.0 "Denzil"
> > > Release date: 29 Jun 2012
> > > Type: BSP
> > > Download Links:
> > > Crown Bay
> > > Crown Bay no EMGD
> > > Release Notes
> > >
> > > So there is one BSP list item per h/w with multiple links to different BSP
> > tarballs for the same hardware.
> > > If we move the WebTitle in machine file, then we will have multiple items
> > in the BSP list for the same hardware.
> > > I am not sure which is better from the downloader's point of view. But this
> > is worth considering for this change.
> > >
> > 
> > Yeah, on the one hand if we have text that's the same for all BSPs in the
> > layer, it could go in the README for lack of a better common place.
> > 
> > But we should consider whether we want to lay things out as the crownbay
> > above, or more like the cedartrail, which has:
> > 
> > Intel® Atom™ Processor N2000 and D2000 Series-based Platform (CEDAR
> > TRAIL) with PowerVR Graphics
> > 
> > (there's no corresponding -nopvr version available, though I suspect that's an
> > oversight and would have been something like:
> > 
> > Intel® Atom™ Processor N2000 and D2000 Series-based Platform (CEDAR
> > TRAIL) with VESA Graphics
> > 
> > I'm not sure the field(s) need to map exactly to the page layout, but all the
> > information should be there to allow the page to be generated or laid out by
> > hand without having to ask questions, in either case.  Did you have any idea
> > as to how for example to distinguish between the emgd and -noemgd
> > versions (side note: there's nothing in the current entry that tells the user
> > what EMGD even is - should it at least be spelled out in the title, or do we
> > need a separate subtext element to describe
> > that?)
> > 
> > Tom
> > 
> 
> I am working with CEDAR trail and Crown Bay-like (SYS940X-ECX) systems. For Crown Bay, it is a little confusing to know which tar ball to download. It would be clearer to have one BSP with an option switch to enable the video. 
> 

There is currently in the works a new web page that lists the available
BSPs in a table and which platforms they map to, along with their
differences.  That should be available soon and I'm sure will be
announced here when it's ready.

As for multiple BSPs, we put out there the most common configurations a
user trying out the hardware is likely to want, which we guessed would
be those two.  Ideally, as you hint at, we'd have a web page that would
allow you to 'custom order' a BSP to download and try out e.g. graphics
choice, input device choices, image type (minimal, sato, sato-sdk, etc),
but for now that's what we do.  Part of it is historical too - users
used to have to click on a EULA on the website to download the EMGD
version and we didn't want to force users to have to do that for a VESA
version too, which you'd have to do if you bundled them together.  Since
that's no longer the case, we could create a single image that could
switch between them, but so far it hasn't really been mentioned until
now.  Maybe something for a new feature in 1.4 or later?

> Also, it would help to know how the EMGD has been configure in the BSP and for what output ports. Having worked with EMGD there are many options. For the SYS940X-ECX, the video driver (VGA-output) doesn't load so X doesn't start. It would be nice to use EMGD to configure this myself and then add the driver, but if this can already be down in the configuration file, it is not clear how to do this.
> 

Yeah, this sounds like good information to be included in the README.
There originally was a link to the EMGD documentation in the README - at
a minimum it should probably be restored, but I agree, it doesn't hurt
to list out the details of configuration that the user's likely to
stumble upon.

Tom

Tom

> Regards,
> 
> Sean Liming
> Owner
> Annabooks
> Tel: 714-970-7523 / Cell: 858-774-3176
> 
> 
> 
> > > >
> > > > > +
> > > > > +Compliance:
> > > > > +============
> > > >
> > > > For consistency with the rest of the README, please remove the colon
> > > > and clean up the underlining.
> > >
> > > Will do.
> > >
> > > Thanks,
> > > Nitin
> > > >
> > > > Thanks,
> > > >
> > > > Tom
> > > >
> > > > > +This BSP is compliant with Yocto Project as per requirements listed
> > here:
> > > > > +http://www.yoctoproject.org/yocto-project-compatible-registration
> > > > > +
> > > > > +
> > > > >  Dependencies
> > > > >  ============
> > > > >
> > > > > @@ -22,7 +31,7 @@ This layer depends on:
> > > > >    branch: master
> > > > >
> > > > >    URI: git://git.yoctoproject.org/meta-intel
> > > > > -  layers: intel
> > > > > +  layers: meta-intel, meta-crownbay
> > > > >    branch: master
> > > > >
> > > > >
> > > >
> > >
> > 
> > 
> > _______________________________________________
> > yocto mailing list
> > yocto@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
> 
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

Re: [PATCH 3/6] crownbay README: add WebTitle & Compliance information

[Kamble, Nitin A]

> >
> > -The Crown Bay platform consists of the Intel Atom Z6xx processor,
> > +The Crown Bay platform consists of the Intel Atom E6xx processor,
> >  plus the Intel EG20T Platform Controller Hub (Tunnel Creek + Topcliff).
> 
> How can we distinguish this from Queens Bay, which I would describe in
> exactly the same terms?
> 
> --
> Darren
> 
> >

1st let us understand what are the differences in the crownbay & queens bay platforms? If there are not significant differences then we can also look at possibility of combining two BSPs into one. 

I can add bit more information in the crownbay readme, such as shellbay & littlebay boards. And for FRI2 you can talk about the extra M2M devices. And I am not clear how to differentiate crownbay BSP with sys94x BSP.

Nitin