[PATCH v2 1/6] MAINTAINERS: correct pathname

[PATCH v2 1/6] MAINTAINERS: correct 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 v2 2/6] chiefriver: 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                       |    8 +++++++-
 meta-chiefriver/conf/machine/chiefriver.conf |    2 ++
 2 files changed, 9 insertions(+), 1 deletions(-)

diff --git a/meta-chiefriver/README b/meta-chiefriver/README
index 7c47b02..249a389 100644
--- a/meta-chiefriver/README
+++ b/meta-chiefriver/README
@@ -7,6 +7,12 @@ plus the Panther Point PCH.  This BSP assumes that the Ivy Bridge
 integrated graphics are being used.
 
 
+Compliance
+==========
+This BSP is compliant with Yocto Project as per requirements listed here:
+http://www.yoctoproject.org/yocto-project-compatible-registration
+
+
 Dependencies
 ============
 
@@ -20,7 +26,7 @@ This layer depends on:
   branch: master
 
   URI: git://git.yoctoproject.org/meta-intel
-  layers: intel
+  layers: meta-intel, meta-chiefriver
   branch: master
 
 
diff --git a/meta-chiefriver/conf/machine/chiefriver.conf b/meta-chiefriver/conf/machine/chiefriver.conf
index b8b8754..5005ce0 100644
--- a/meta-chiefriver/conf/machine/chiefriver.conf
+++ b/meta-chiefriver/conf/machine/chiefriver.conf
@@ -1,6 +1,8 @@
 #@TYPE: Machine
 #@NAME: chiefriver
 
+#@WEBTITLE: Intel 3rd Generations Core Platforms: Core i3, i5, i7 (Ivy Bridge)
+
 #@DESCRIPTION: Machine configuration for Chief River systems
 # i.e. Ivy Bridge + Panther Point
 
-- 
1.7.3.4

[PATCH v2 3/6] crownbay: 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                            |   10 ++++++++--
 meta-crownbay/conf/machine/crownbay-noemgd.conf |    2 ++
 meta-crownbay/conf/machine/crownbay.conf        |    2 ++
 3 files changed, 12 insertions(+), 2 deletions(-)

diff --git a/meta-crownbay/README b/meta-crownbay/README
index 4bc9f31..f3ad506 100644
--- a/meta-crownbay/README
+++ b/meta-crownbay/README
@@ -2,13 +2,19 @@ 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.
 
 
+Compliance
+==========
+This BSP is compliant with Yocto Project as per requirements listed here:
+http://www.yoctoproject.org/yocto-project-compatible-registration
+
+
 Dependencies
 ============
 
@@ -22,7 +28,7 @@ This layer depends on:
   branch: master
 
   URI: git://git.yoctoproject.org/meta-intel
-  layers: intel
+  layers: meta-intel, meta-crownbay
   branch: master
 
 
diff --git a/meta-crownbay/conf/machine/crownbay-noemgd.conf b/meta-crownbay/conf/machine/crownbay-noemgd.conf
index 4c869ee..c3bdcb4 100644
--- a/meta-crownbay/conf/machine/crownbay-noemgd.conf
+++ b/meta-crownbay/conf/machine/crownbay-noemgd.conf
@@ -1,6 +1,8 @@
 #@TYPE: Machine
 #@NAME: crownbay-noemgd
 
+#@WEBTITLE: Intel Atom E6xx processor with Intel EG20T Controller Hub development kit (Crown Bay) with open source VESA graphics
+
 #@DESCRIPTION: Machine configuration for Crown Bay systems, without Intel-proprietary graphics bits
 # i.e. E660 + EG20T
 
diff --git a/meta-crownbay/conf/machine/crownbay.conf b/meta-crownbay/conf/machine/crownbay.conf
index d56ef64..5e4147c 100644
--- a/meta-crownbay/conf/machine/crownbay.conf
+++ b/meta-crownbay/conf/machine/crownbay.conf
@@ -1,6 +1,8 @@
 #@TYPE: Machine
 #@NAME: crownbay
 
+#@WEBTITLE: Intel Atom E6xx processor with Intel EG20T Controller Hub development kit (Crown Bay) with proprietary IEMGD accelerated graphics
+
 #@DESCRIPTION: Machine configuration for Crown Bay systems
 # i.e. E660 + EG20T
 
-- 
1.7.3.4

[PATCH v2 4/6] emenlow: 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                    |    8 +++++++-
 meta-emenlow/conf/machine/emenlow.conf |    2 ++
 2 files changed, 9 insertions(+), 1 deletions(-)

diff --git a/meta-emenlow/README b/meta-emenlow/README
index 3932718..8216af2 100644
--- a/meta-emenlow/README
+++ b/meta-emenlow/README
@@ -13,6 +13,12 @@ depending on which BSP tarball you downloaded.
 Please see the corresponding sections below for details.
 
 
+Compliance
+==========
+This BSP is compliant with Yocto Project as per requirements listed here:
+http://www.yoctoproject.org/yocto-project-compatible-registration
+
+
 Dependencies
 ============
 
@@ -26,7 +32,7 @@ This layer depends on:
   branch: master
 
   URI: git://git.yoctoproject.org/meta-intel
-  layers: intel
+  layers: meta-intel, meta-emenlow
   branch: master
 
 
diff --git a/meta-emenlow/conf/machine/emenlow.conf b/meta-emenlow/conf/machine/emenlow.conf
index d1efbc3..77cdbe6 100644
--- a/meta-emenlow/conf/machine/emenlow.conf
+++ b/meta-emenlow/conf/machine/emenlow.conf
@@ -1,6 +1,8 @@
 #@TYPE: Machine
 #@NAME: emenlow
 
+#@WEBTITLE: Platforms with Intel Atom Z5xx processor with Intel US15W Controller Hub (Emenlow)
+
 #@DESCRIPTION: Machine configuration for eMenlow based systems, like the
 # Webs-2120 box.
 
-- 
1.7.3.4

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

[nitin.a.kamble]

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

Changed the commits based on the feedback from Tom & Darren. We also need similar changes
for other BSPs for 1.3 release.

Thanks,
Nitin

The following changes since commit 62aa4ca25a943c864838b2910c5b506cca0c9323:

  fri2: Add grub-efi workaround for USB keyboard initialization (2012-10-24 13:16:00 -0700)

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: correct pathname
  chiefriver: add WEBTITLE & Compliance information
  crownbay: add WEBTITLE & Compliance information
  emenlow: add WEBTITLE & Compliance information
  jasperforest: add WEBTITLE & Compliance information
  sugarbay: add WEBTITLE & Compliance information

 MAINTAINERS                                      |    2 +-
 meta-chiefriver/README                           |    8 +++++++-
 meta-chiefriver/conf/machine/chiefriver.conf     |    2 ++
 meta-crownbay/README                             |   10 ++++++++--
 meta-crownbay/conf/machine/crownbay-noemgd.conf  |    2 ++
 meta-crownbay/conf/machine/crownbay.conf         |    2 ++
 meta-emenlow/README                              |    8 +++++++-
 meta-emenlow/conf/machine/emenlow.conf           |    2 ++
 meta-jasperforest/README                         |    8 +++++++-
 meta-jasperforest/conf/machine/jasperforest.conf |    2 ++
 meta-sugarbay/README                             |    8 +++++++-
 meta-sugarbay/conf/machine/sugarbay.conf         |    2 ++
 12 files changed, 49 insertions(+), 7 deletions(-)

-- 
1.7.3.4

[PATCH v2 5/6] jasperforest: 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                         |    8 +++++++-
 meta-jasperforest/conf/machine/jasperforest.conf |    2 ++
 2 files changed, 9 insertions(+), 1 deletions(-)

diff --git a/meta-jasperforest/README b/meta-jasperforest/README
index 12f84c2..6397ec7 100644
--- a/meta-jasperforest/README
+++ b/meta-jasperforest/README
@@ -8,6 +8,12 @@ combined with the Intel 3420 PCH chipset (Ibex Peak) make up the
 'Picket Post' CRB this BSP was developed on.
 
 
+Compliance
+==========
+This BSP is compliant with Yocto Project as per requirements listed here:
+http://www.yoctoproject.org/yocto-project-compatible-registration
+
+
 Dependencies
 ============
 
@@ -21,7 +27,7 @@ This layer depends on:
   branch: master
 
   URI: git://git.yoctoproject.org/meta-intel
-  layers: intel
+  layers: meta-intel, meta-jasperforest
   branch: master
 
 
diff --git a/meta-jasperforest/conf/machine/jasperforest.conf b/meta-jasperforest/conf/machine/jasperforest.conf
index d661f7b..8111deb 100644
--- a/meta-jasperforest/conf/machine/jasperforest.conf
+++ b/meta-jasperforest/conf/machine/jasperforest.conf
@@ -1,6 +1,8 @@
 #@TYPE: Machine
 #@NAME: jasperforest
 
+#@WEBTITLE: Platforms with Intel Xeon C5500/C3500 series processors with Intel 3420 PCH chipset (Jasper Forest)
+
 #@DESCRIPTION: Machine configuration for Jasper Forest Picket Post
 # systems i.e. Xeon C5500/C3500 + Intel 3420 chipset (Ibex Peak)
 
-- 
1.7.3.4

[PATCH v2 6/6] sugarbay: 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                     |    8 +++++++-
 meta-sugarbay/conf/machine/sugarbay.conf |    2 ++
 2 files changed, 9 insertions(+), 1 deletions(-)

diff --git a/meta-sugarbay/README b/meta-sugarbay/README
index c8a99d7..5b84bac 100644
--- a/meta-sugarbay/README
+++ b/meta-sugarbay/README
@@ -7,6 +7,12 @@ plus the Cougar Point PCH (Q67 Express or B65 Express chipsets).  This
 BSP assumes that the Sandy Bridge integrated graphics are being used.
 
 
+Compliance
+==========
+This BSP is compliant with Yocto Project as per requirements listed here:
+http://www.yoctoproject.org/yocto-project-compatible-registration
+
+
 Dependencies
 ============
 
@@ -20,7 +26,7 @@ This layer depends on:
   branch: master
 
   URI: git://git.yoctoproject.org/meta-intel
-  layers: intel
+  layers: meta-intel, meta-sugarbay
   branch: master
 
 
diff --git a/meta-sugarbay/conf/machine/sugarbay.conf b/meta-sugarbay/conf/machine/sugarbay.conf
index 1d0e68d..5fb0c59 100644
--- a/meta-sugarbay/conf/machine/sugarbay.conf
+++ b/meta-sugarbay/conf/machine/sugarbay.conf
@@ -1,6 +1,8 @@
 #@TYPE: Machine
 #@NAME: sugarbay
 
+#@WEBTITLE: Intel 2nd Generation Core Platforms: Core i3, i5, i7 (Sandy Bridge)
+
 #@DESCRIPTION: Machine configuration for Sugar Bay systems
 # i.e. Sandy Bridge + Cougar Point
 
-- 
1.7.3.4

Re: [PATCH v2 2/6] chiefriver: add WEBTITLE & Compliance information

[Tom Zanussi]

On Wed, 2012-10-24 at 13:25 -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-chiefriver/README                       |    8 +++++++-
>  meta-chiefriver/conf/machine/chiefriver.conf |    2 ++
>  2 files changed, 9 insertions(+), 1 deletions(-)
> 
> diff --git a/meta-chiefriver/README b/meta-chiefriver/README
> index 7c47b02..249a389 100644
> --- a/meta-chiefriver/README
> +++ b/meta-chiefriver/README
> @@ -7,6 +7,12 @@ plus the Panther Point PCH.  This BSP assumes that the Ivy Bridge
>  integrated graphics are being used.
>  
> 
> +Compliance
> +==========
> +This BSP is compliant with Yocto Project as per requirements listed here:
> +http://www.yoctoproject.org/yocto-project-compatible-registration
> +

To be consistent with the rest of the README, there should be a blank
line between the ===== and the 'This BSP... ' text.

Also, for readability, it would be nice to have the URL also separated
by a blank line from the preceding text, and indented a couple spaces
like similar lines in the README.

Also, I think the compliance text reads better as:

This BSP is compliant with the Yocto Project as per the requirements
listed here:

> +
>  Dependencies
>  ============
>  
> @@ -20,7 +26,7 @@ This layer depends on:
>    branch: master
>  
>    URI: git://git.yoctoproject.org/meta-intel
> -  layers: intel
> +  layers: meta-intel, meta-chiefriver

If you look at the meta-intel/conf/layer.conf, you see the layer
actually is 'intel'.

Also, this is the README for the chiefriver layer, so it can't depend on
itself i.e. meta-chiefriver or 'chiefriver' shouldn't be listed in
layers

>    branch: master
>  
> 
> diff --git a/meta-chiefriver/conf/machine/chiefriver.conf b/meta-chiefriver/conf/machine/chiefriver.conf
> index b8b8754..5005ce0 100644
> --- a/meta-chiefriver/conf/machine/chiefriver.conf
> +++ b/meta-chiefriver/conf/machine/chiefriver.conf
> @@ -1,6 +1,8 @@
>  #@TYPE: Machine
>  #@NAME: chiefriver
>  
> +#@WEBTITLE: Intel 3rd Generations Core Platforms: Core i3, i5, i7 (Ivy Bridge)
> +

Since this is text that will appear on the website, we need to be a
little picky about grammar: it should read '3rd Generation' rather than
'3rd Generations'

These comments apply to the other README files as well, so I won't
repeat them there, other than to fix any text that might appear on the
website for those as well...

Tom

>  #@DESCRIPTION: Machine configuration for Chief River systems
>  # i.e. Ivy Bridge + Panther Point
>  

Re: [PATCH v2 3/6] crownbay: add WEBTITLE & Compliance information

[Tom Zanussi]

On Wed, 2012-10-24 at 13:25 -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                            |   10 ++++++++--
>  meta-crownbay/conf/machine/crownbay-noemgd.conf |    2 ++
>  meta-crownbay/conf/machine/crownbay.conf        |    2 ++
>  3 files changed, 12 insertions(+), 2 deletions(-)
> 
> diff --git a/meta-crownbay/README b/meta-crownbay/README
> index 4bc9f31..f3ad506 100644
> --- a/meta-crownbay/README
> +++ b/meta-crownbay/README
> @@ -2,13 +2,19 @@ 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.
>  
> 
> +Compliance
> +==========
> +This BSP is compliant with Yocto Project as per requirements listed here:
> +http://www.yoctoproject.org/yocto-project-compatible-registration
> +
> +
>  Dependencies
>  ============
>  
> @@ -22,7 +28,7 @@ This layer depends on:
>    branch: master
>  
>    URI: git://git.yoctoproject.org/meta-intel
> -  layers: intel
> +  layers: meta-intel, meta-crownbay
>    branch: master
>  
> 
> diff --git a/meta-crownbay/conf/machine/crownbay-noemgd.conf b/meta-crownbay/conf/machine/crownbay-noemgd.conf
> index 4c869ee..c3bdcb4 100644
> --- a/meta-crownbay/conf/machine/crownbay-noemgd.conf
> +++ b/meta-crownbay/conf/machine/crownbay-noemgd.conf
> @@ -1,6 +1,8 @@
>  #@TYPE: Machine
>  #@NAME: crownbay-noemgd
>  
> +#@WEBTITLE: Intel Atom E6xx processor with Intel EG20T Controller Hub development kit (Crown Bay) with open source VESA graphics
> +

This should probably be capitalized as in the manual title:

Intel Atom E6xx Processor with Intel EG20T Controller Hub Development
Kit (Crown Bay) with open source VESA graphics

Same for the other one...

Tom

>  #@DESCRIPTION: Machine configuration for Crown Bay systems, without Intel-proprietary graphics bits
>  # i.e. E660 + EG20T
>  
> diff --git a/meta-crownbay/conf/machine/crownbay.conf b/meta-crownbay/conf/machine/crownbay.conf
> index d56ef64..5e4147c 100644
> --- a/meta-crownbay/conf/machine/crownbay.conf
> +++ b/meta-crownbay/conf/machine/crownbay.conf
> @@ -1,6 +1,8 @@
>  #@TYPE: Machine
>  #@NAME: crownbay
>  
> +#@WEBTITLE: Intel Atom E6xx processor with Intel EG20T Controller Hub development kit (Crown Bay) with proprietary IEMGD accelerated graphics
> +
>  #@DESCRIPTION: Machine configuration for Crown Bay systems
>  # i.e. E660 + EG20T
>  

Re: [PATCH v2 4/6] emenlow: add WEBTITLE & Compliance information

[Tom Zanussi]

On Wed, 2012-10-24 at 13:25 -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-emenlow/README                    |    8 +++++++-
>  meta-emenlow/conf/machine/emenlow.conf |    2 ++
>  2 files changed, 9 insertions(+), 1 deletions(-)
> 
> diff --git a/meta-emenlow/README b/meta-emenlow/README
> index 3932718..8216af2 100644
> --- a/meta-emenlow/README
> +++ b/meta-emenlow/README
> @@ -13,6 +13,12 @@ depending on which BSP tarball you downloaded.
>  Please see the corresponding sections below for details.
>  
> 
> +Compliance
> +==========
> +This BSP is compliant with Yocto Project as per requirements listed here:
> +http://www.yoctoproject.org/yocto-project-compatible-registration
> +
> +
>  Dependencies
>  ============
>  
> @@ -26,7 +32,7 @@ This layer depends on:
>    branch: master
>  
>    URI: git://git.yoctoproject.org/meta-intel
> -  layers: intel
> +  layers: meta-intel, meta-emenlow
>    branch: master
>  
> 
> diff --git a/meta-emenlow/conf/machine/emenlow.conf b/meta-emenlow/conf/machine/emenlow.conf
> index d1efbc3..77cdbe6 100644
> --- a/meta-emenlow/conf/machine/emenlow.conf
> +++ b/meta-emenlow/conf/machine/emenlow.conf
> @@ -1,6 +1,8 @@
>  #@TYPE: Machine
>  #@NAME: emenlow
>  
> +#@WEBTITLE: Platforms with Intel Atom Z5xx processor with Intel US15W Controller Hub (Emenlow)
> +

To be consistent with the other ones e.g crownbay, remove the 'Platforms
with' and also capitalize as:

Intel Atom Z5xx Processor with Intel US15W Platform Controller Hub
(Emenlow)

I think Emenlow is actually eMenlow...

Tom

>  #@DESCRIPTION: Machine configuration for eMenlow based systems, like the
>  # Webs-2120 box.
>  

Re: [PATCH v2 5/6] jasperforest: add WEBTITLE & Compliance information

[Tom Zanussi]

On Wed, 2012-10-24 at 13:25 -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-jasperforest/README                         |    8 +++++++-
>  meta-jasperforest/conf/machine/jasperforest.conf |    2 ++
>  2 files changed, 9 insertions(+), 1 deletions(-)
> 
> diff --git a/meta-jasperforest/README b/meta-jasperforest/README
> index 12f84c2..6397ec7 100644
> --- a/meta-jasperforest/README
> +++ b/meta-jasperforest/README
> @@ -8,6 +8,12 @@ combined with the Intel 3420 PCH chipset (Ibex Peak) make up the
>  'Picket Post' CRB this BSP was developed on.
>  
> 
> +Compliance
> +==========
> +This BSP is compliant with Yocto Project as per requirements listed here:
> +http://www.yoctoproject.org/yocto-project-compatible-registration
> +
> +
>  Dependencies
>  ============
>  
> @@ -21,7 +27,7 @@ This layer depends on:
>    branch: master
>  
>    URI: git://git.yoctoproject.org/meta-intel
> -  layers: intel
> +  layers: meta-intel, meta-jasperforest
>    branch: master
>  
> 
> diff --git a/meta-jasperforest/conf/machine/jasperforest.conf b/meta-jasperforest/conf/machine/jasperforest.conf
> index d661f7b..8111deb 100644
> --- a/meta-jasperforest/conf/machine/jasperforest.conf
> +++ b/meta-jasperforest/conf/machine/jasperforest.conf
> @@ -1,6 +1,8 @@
>  #@TYPE: Machine
>  #@NAME: jasperforest
>  
> +#@WEBTITLE: Platforms with Intel Xeon C5500/C3500 series processors with Intel 3420 PCH chipset (Jasper Forest)
> +

Similarly:

Intel Xeon C5500/C3500 Series Processors with Intel 3420 PCH Chipset
(Jasper Forest)

Tom

>  #@DESCRIPTION: Machine configuration for Jasper Forest Picket Post
>  # systems i.e. Xeon C5500/C3500 + Intel 3420 chipset (Ibex Peak)
>  

Re: [PATCH v2 2/6] chiefriver: add WEBTITLE & Compliance information

[Kamble, Nitin A]

> -----Original Message-----
> From: Zanussi, Tom
> Sent: Wednesday, October 24, 2012 5:15 PM
> To: Kamble, Nitin A
> Cc: yocto@yoctoproject.org; Hart, Darren
> Subject: Re: [PATCH v2 2/6] chiefriver: add WEBTITLE & Compliance
> information
> 
> On Wed, 2012-10-24 at 13:25 -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-chiefriver/README                       |    8 +++++++-
> >  meta-chiefriver/conf/machine/chiefriver.conf |    2 ++
> >  2 files changed, 9 insertions(+), 1 deletions(-)
> >
> > diff --git a/meta-chiefriver/README b/meta-chiefriver/README index
> > 7c47b02..249a389 100644
> > --- a/meta-chiefriver/README
> > +++ b/meta-chiefriver/README
> > @@ -7,6 +7,12 @@ plus the Panther Point PCH.  This BSP assumes that
> > the Ivy Bridge  integrated graphics are being used.
> >
> >
> > +Compliance
> > +==========
> > +This BSP is compliant with Yocto Project as per requirements listed here:
> > +http://www.yoctoproject.org/yocto-project-compatible-registration
> > +
> 
> To be consistent with the rest of the README, there should be a blank line
> between the ===== and the 'This BSP... ' text.
> 
> Also, for readability, it would be nice to have the URL also separated by a
> blank line from the preceding text, and indented a couple spaces like similar
> lines in the README.
> 
> Also, I think the compliance text reads better as:
> 
> This BSP is compliant with the Yocto Project as per the requirements listed
> here:
> 
> > +
> >  Dependencies
> >  ============
> >
> > @@ -20,7 +26,7 @@ This layer depends on:
> >    branch: master
> >
> >    URI: git://git.yoctoproject.org/meta-intel
> > -  layers: intel
> > +  layers: meta-intel, meta-chiefriver
> 
> If you look at the meta-intel/conf/layer.conf, you see the layer actually is
> 'intel'.
> 
> Also, this is the README for the chiefriver layer, so it can't depend on itself
> i.e. meta-chiefriver or 'chiefriver' shouldn't be listed in layers

Tom,
   As part of the compliance we need to list all the components/layers needed to build the BSP. So even though it is README from this layer I think it should be listed as one of dependency for building the BSP.
And I will incorporate the rest of the feedback in the next pull request.

Nitin

> 
> >    branch: master
> >
> >
> > diff --git a/meta-chiefriver/conf/machine/chiefriver.conf
> > b/meta-chiefriver/conf/machine/chiefriver.conf
> > index b8b8754..5005ce0 100644
> > --- a/meta-chiefriver/conf/machine/chiefriver.conf
> > +++ b/meta-chiefriver/conf/machine/chiefriver.conf
> > @@ -1,6 +1,8 @@
> >  #@TYPE: Machine
> >  #@NAME: chiefriver
> >
> > +#@WEBTITLE: Intel 3rd Generations Core Platforms: Core i3, i5, i7
> > +(Ivy Bridge)
> > +
> 
> Since this is text that will appear on the website, we need to be a little picky
> about grammar: it should read '3rd Generation' rather than '3rd Generations'
> 
> These comments apply to the other README files as well, so I won't repeat
> them there, other than to fix any text that might appear on the website for
> those as well...
> 
> Tom
> 
> >  #@DESCRIPTION: Machine configuration for Chief River systems  # i.e.
> > Ivy Bridge + Panther Point
> >
> 

Re: [PATCH v2 2/6] chiefriver: add WEBTITLE & Compliance information

[Kamble, Nitin A]

> >
> > If you look at the meta-intel/conf/layer.conf, you see the layer
> > actually is 'intel'.
> >
> > Also, this is the README for the chiefriver layer, so it can't depend
> > on itself i.e. meta-chiefriver or 'chiefriver' shouldn't be listed in
> > layers
> 
> Tom,
>    As part of the compliance we need to list all the components/layers needed
> to build the BSP. So even though it is README from this layer I think it should
> be listed as one of dependency for building the BSP.

Tom,
  It's ok, there are other places in the README where these layers are mentioned. 
So I can take this change out too.

Thanks,
Nitin