meta-intel: README updates
cover meta-intel: README updates
From: Nitin A Kamble <[email protected]>
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(-)
Signature · 1 line
1.7.3.4
PATCH 1/6 MAINTAINERS: corect pathname
From: Nitin A Kamble <[email protected]>
The commmon directory has more stuff than just recipes-core. All this need to be maintained together as part of the meta-intel layer.
--- MAINTAINERS | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-)
MAINTAINERS +1 -1
@@ -42,7 +42,7 @@ F: meta-chiefriver/ COMMON M: Nitin A Kamble<[email protected]> -F: common/recipes-core/ +F: common/ CROWNBAY M: Nitin A Kamble<[email protected]>
Signature · 1 line
1.7.3.4
PATCH 2/6 chiefriver README: add WebTitle & Compliance information
From: Nitin A Kamble <[email protected]>
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.
--- meta-chiefriver/README | 10 +++++++++- 1 files changed, 9 insertions(+), 1 deletions(-)
meta-chiefriver/README +9 -1
@@ -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
Signature · 1 line
1.7.3.4
Re: [PATCH 2/6] chiefriver README: add WebTitle & Compliance information
Quoted 16 lines · On 10/23/2012 01:24 PM, [email protected] wrote:
From: Nitin A Kamble <[email protected]>
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 <[email protected]>--- meta-chiefriver/README | 10 +++++++++- 1 files changed, 9 insertions(+), 1 deletions(-)meta-chiefriver/README +0
-0
meta-chiefriver/README The 'Chief River' platform consists of the Intel Ivy Bridge processor, · line 9
Quoted 4 lines
meta-chiefriver/README +1
-0@@ -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.
Quoted 20 lines
meta-chiefriver/README +8
-1+ + +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
Signature · 3 lines
Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel
PATCH 3/6 crownbay README: add WebTitle & Compliance information
In reply to [email protected]From: Nitin A Kamble <[email protected]>
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.
--- meta-crownbay/README | 13 +++++++++++-- 1 files changed, 11 insertions(+), 2 deletions(-)
meta-crownbay/README +11 -2
@@ -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
Signature · 1 line
1.7.3.4
Re: [PATCH 3/6] crownbay README: add WebTitle & Compliance information
Quoted 16 lines · On 10/23/2012 01:24 PM, [email protected] wrote:
From: Nitin A Kamble <[email protected]>
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 <[email protected]>--- meta-crownbay/README | 13 +++++++++++-- 1 files changed, 11 insertions(+), 2 deletions(-)meta-crownbay/README +0
-0
meta-crownbay/README This README file contains information on building the meta-crownbay · line 6
Quoted 6 lines
meta-crownbay/README +1
-1@@ -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
Quoted 27 lines
meta-crownbay/README +10
-1It 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
Signature · 3 lines
Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel
Re: [PATCH 3/6] crownbay README: add WebTitle & Compliance information
Quoted 8 lines
meta-crownbay/README This README file contains information on building the meta-crownbay · line 6
Quoted 4 lines
meta-crownbay/README +1
-1-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?
Quoted 4 lines
--
DarrenQuoted 1 line
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
Re: [PATCH 3/6] crownbay README: add WebTitle & Compliance information
In reply to [email protected]Quoted 19 lines · On Tue, 2012-10-23 at 13:24 -0700, [email protected] wrote:
From: Nitin A Kamble <[email protected]>
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 <[email protected]>--- meta-crownbay/README | 13 +++++++++++-- 1 files changed, 11 insertions(+), 2 deletions(-)meta-crownbay/README +0
-0@@ -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.
meta-crownbay/README This README file contains information on building the meta-crownbay · line 13
Quoted 10 lines
meta-crownbay/README +3
-1-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...
meta-crownbay/README This README file contains information on building the meta-crownbay · line 16
Quoted 3 lines
meta-crownbay/README +3
-0+ +Compliance: +============
For consistency with the rest of the README, please remove the colon and clean up the underlining.
Thanks,
Tom
Quoted 16 lines
meta-crownbay/README +5
-1+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
Quoted 11 lines · Tom Zanussi
Review
Quoted 2 lines · On Tue, 2012-10-23 at 13:24 -0700, [email protected] wrote:
(quoted diff) +2
-0+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_crownbayand WebTitle_crownbay-noemgd lines. ;-) (and it would be nice if you could get rid of the CamelCaps too)
Quoted 7 lines
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.
Signature · 3 lines
Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel
Re: [PATCH 3/6] crownbay README: add WebTitle & Compliance information
In reply to Tom ZanussiQuoted 52 lines
-----Original Message-----
From: Zanussi, Tom
Sent: Tuesday, October 23, 2012 2:16 PM
To: Kamble, Nitin A
Cc: [email protected]; Hart, Darren
Subject: Re: [PATCH 3/6] crownbay README: add WebTitle & Compliance informationQuoted 16 lines · On Tue, 2012-10-23 at 13:24 -0700, [email protected] wrote:
From: Nitin A Kamble <[email protected]>
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 <[email protected]>--- meta-crownbay/README | 13 +++++++++++-- 1 files changed, 11 insertions(+), 2 deletions(-)meta-crownbay/README index renamed from meta-crownbay/README +0
-04bc9f31..3996a94 100644
meta-crownbay/README +0
-0@@ -2,13 +2,22 @@ This README file contains information on buildingQuoted 1 line
the meta-crownbay BSP layer, and booting the images contained in the
/binary directory.
meta-crownbay/README
Quoted 13 lines
Please see the corresponding sections below for details.
meta-crownbay/README +1
-1-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 IntelEmbedded Media and Graphics Driver (EMGD) 1.14 Driver.
meta-crownbay/README +3
-0+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_crownbayand 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.
Quoted 6 lines
#@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.
Quoted 7 lines
meta-crownbay/README This README file contains information on building the meta-crownbay · line 16
Quoted 4 lines
meta-crownbay/README +3
-0+ +Compliance: +============For consistency with the rest of the README, please remove the colon and clean up the underlining.
Will do.
Thanks,
Nitin
Quoted 22 lines
Thanks,
Tom
Quoted 16 lines
meta-crownbay/README +5
-1+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
Quoted 69 lines · Nitin A
Quoted 51 lines
-----Original Message-----
From: Zanussi, Tom
Sent: Tuesday, October 23, 2012 2:16 PM
To: Kamble, Nitin A
Cc: [email protected]; Hart, Darren
Subject: Re: [PATCH 3/6] crownbay README: add WebTitle & Compliance informationQuoted 16 lines · On Tue, 2012-10-23 at 13:24 -0700, [email protected] wrote:
From: Nitin A Kamble <[email protected]>
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 <[email protected]>--- meta-crownbay/README | 13 +++++++++++-- 1 files changed, 11 insertions(+), 2 deletions(-)meta-crownbay/README index renamed from meta-crownbay/README +0
-04bc9f31..3996a94 100644
meta-crownbay/README +0
-0@@ -2,13 +2,22 @@ This README file contains information on buildingQuoted 1 line
the meta-crownbay BSP layer, and booting the images contained in the
/binary directory.
meta-crownbay/README
Quoted 13 lines
Please see the corresponding sections below for details.
meta-crownbay/README +1
-1-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 IntelEmbedded Media and Graphics Driver (EMGD) 1.14 Driver.
meta-crownbay/README +3
-0+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_crownbayand 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.
Quoted 6 lines
#@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
Quoted 4 lines
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
Quoted 35 lines
Quoted 7 lines
meta-crownbay/README This README file contains information on building the meta-crownbay · line 16
Quoted 4 lines
meta-crownbay/README +3
-0+ +Compliance: +============For consistency with the rest of the README, please remove the colon and clean up the underlining.
Will do.
Thanks,
NitinQuoted 22 lines
Thanks,
Tom
Quoted 16 lines
meta-crownbay/README +5
-1+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
Quoted 90 lines · Tom Zanussi
Quoted 69 lines · Nitin A
Quoted 51 lines
-----Original Message-----
From: Zanussi, Tom
Sent: Tuesday, October 23, 2012 2:16 PM
To: Kamble, Nitin A
Cc: [email protected]; Hart, Darren
Subject: Re: [PATCH 3/6] crownbay README: add WebTitle & Compliance informationQuoted 16 lines · On Tue, 2012-10-23 at 13:24 -0700, [email protected] wrote:
From: Nitin A Kamble <[email protected]>
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 <[email protected]>--- meta-crownbay/README | 13 +++++++++++-- 1 files changed, 11 insertions(+), 2 deletions(-)meta-crownbay/README index renamed from meta-crownbay/README +0
-04bc9f31..3996a94 100644
meta-crownbay/README +0
-0@@ -2,13 +2,22 @@ This README file contains information on buildingQuoted 1 line
the meta-crownbay BSP layer, and booting the images contained in the
/binary directory.
meta-crownbay/README
Quoted 13 lines
Please see the corresponding sections below for details.
meta-crownbay/README +1
-1-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 IntelEmbedded Media and Graphics Driver (EMGD) 1.14 Driver.
meta-crownbay/README +3
-0+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_crownbayand 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.
Quoted 6 lines
#@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 NotesQuoted 4 lines
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
Quoted 8 lines
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.
Signature · 3 lines
Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel
Re: [PATCH 3/6] crownbay README: add WebTitle & Compliance information
In reply to Tom ZanussiQuoted 110 lines
-----Original Message-----
From: Zanussi, Tom
Sent: Wednesday, October 24, 2012 9:43 AM
To: Kamble, Nitin A
Cc: [email protected]; Hart, Darren
Subject: Re: [PATCH 3/6] crownbay README: add WebTitle & Compliance informationQuoted 9 lines · Nitin A
Quoted 9 lines
-----Original Message-----
From: Zanussi, Tom
Sent: Tuesday, October 23, 2012 2:16 PM
To: Kamble, Nitin A
Cc: [email protected]; Hart, Darren
Subject: Re: [PATCH 3/6] crownbay README: add WebTitle & Compliance informationQuoted 4 lines
Quoted 4 lines · On Tue, 2012-10-23 at 13:24 -0700, [email protected] wrote:
Quoted 3 lines
From: Nitin A Kamble <[email protected]>
The WebTitle will be used to publish the BSP on the Yocto Project
Website.
Quoted 1 line
Quoted 1 line
Quoted 1 line
And adding the Yocto Project Compliance information for the 1.3
release.
Quoted 25 lines
Quoted 25 lines
Quoted 12 lines
Also specifying all the layers used from meta-intel repository.
Signed-off-by Nitin A Kamble <[email protected]>--- meta-crownbay/README | 13 +++++++++++-- 1 files changed, 11 insertions(+), 2 deletions(-)meta-crownbay/README index renamed from meta-crownbay/README +0
-04bc9f31..3996a94 100644
meta-crownbay/README +0
-0@@ -2,13 +2,22 @@ This README file contains information onQuoted 2 lines
building the meta-crownbay BSP layer, and booting the images contained in the
/binary directory.
Quoted 10 lines
Please see the corresponding sections below for details.
meta-crownbay/README +1
-1-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 IntelEmbedded Media and Graphics Driver (EMGD) 1.14 Driver.
Quoted 8 lines
Quoted 8 lines
meta-crownbay/README
Quoted 3 lines
meta-crownbay/README +3
-0+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_crownbayand WebTitle_crownbay-noemgd
Quoted 26 lines
Quoted 6 lines
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.
Quoted 6 lines
#@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 NotesQuoted 1 line
So there is one BSP list item per h/w with multiple links to different BSP
tarballs for the same hardware.
Quoted 1 line
If we move the WebTitle in machine file, then we will have multiple items
in the BSP list for the same hardware.
Quoted 1 line
I am not sure which is better from the downloader's point of view. But this
is worth considering for this change.
Quoted 1 line
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
Quoted 9 lines
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
Quoted 39 lines
Tom
Quoted 8 lines
Quoted 7 lines
meta-crownbay/README This README file contains information on building the meta-crownbay · line 16
Quoted 4 lines
meta-crownbay/README +3
-0+ +Compliance: +============For consistency with the rest of the README, please remove the colon and clean up the underlining.
Quoted 10 lines
Will do.
Thanks,
NitinQuoted 6 lines
Thanks,
Tom
Quoted 1 line
+This BSP is compliant with Yocto Project as per requirements listed
here:
Quoted 17 lines
Quoted 16 lines
Quoted 15 lines
meta-crownbay/README +4
-1+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
In reply to Tom ZanussiQuoted 118 lines
-----Original Message-----
From: [email protected] [mailto:yocto- [email protected]] On Behalf Of Tom Zanussi
Sent: Wednesday, October 24, 2012 9:43 AM
To: Kamble, Nitin A
Cc: [email protected]; Hart, Darren
Subject: Re: [yocto] [PATCH 3/6] crownbay README: add WebTitle & Compliance informationQuoted 9 lines · Nitin A
Quoted 9 lines
-----Original Message-----
From: Zanussi, Tom
Sent: Tuesday, October 23, 2012 2:16 PM
To: Kamble, Nitin A
Cc: [email protected]; Hart, Darren
Subject: Re: [PATCH 3/6] crownbay README: add WebTitle & Compliance informationQuoted 4 lines
Quoted 4 lines · On Tue, 2012-10-23 at 13:24 -0700, [email protected] wrote:
Quoted 3 lines
From: Nitin A Kamble <[email protected]>
The WebTitle will be used to publish the BSP on the Yocto Project
Website.
Quoted 1 line
Quoted 1 line
Quoted 1 line
And adding the Yocto Project Compliance information for the 1.3
release.
Quoted 25 lines
Quoted 25 lines
Quoted 12 lines
Also specifying all the layers used from meta-intel repository.
Signed-off-by Nitin A Kamble <[email protected]>--- meta-crownbay/README | 13 +++++++++++-- 1 files changed, 11 insertions(+), 2 deletions(-)meta-crownbay/README index renamed from meta-crownbay/README +0
-04bc9f31..3996a94 100644
meta-crownbay/README +0
-0@@ -2,13 +2,22 @@ This README file contains information onQuoted 2 lines
building the meta-crownbay BSP layer, and booting the images contained in the
/binary directory.
Quoted 10 lines
Please see the corresponding sections below for details.
meta-crownbay/README +1
-1-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 IntelEmbedded Media and Graphics Driver (EMGD) 1.14 Driver.
Quoted 8 lines
Quoted 8 lines
meta-crownbay/README
Quoted 3 lines
meta-crownbay/README +3
-0+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_crownbayand WebTitle_crownbay-noemgd
Quoted 26 lines
Quoted 6 lines
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.
Quoted 6 lines
#@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 NotesQuoted 1 line
So there is one BSP list item per h/w with multiple links to different BSP
tarballs for the same hardware.
Quoted 1 line
If we move the WebTitle in machine file, then we will have multiple items
in the BSP list for the same hardware.
Quoted 1 line
I am not sure which is better from the downloader's point of view. But this
is worth considering for this change.
Quoted 1 line
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?)
Quoted 2 lines
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
Quoted 42 lines
Quoted 8 lines
Quoted 7 lines
meta-crownbay/README This README file contains information on building the meta-crownbay · line 16
Quoted 4 lines
meta-crownbay/README +3
-0+ +Compliance: +============For consistency with the rest of the README, please remove the colon and clean up the underlining.
Quoted 10 lines
Will do.
Thanks,
NitinQuoted 6 lines
Thanks,
Tom
Quoted 1 line
+This BSP is compliant with Yocto Project as per requirements listed
here:
Quoted 9 lines
Quoted 9 lines
Quoted 9 lines
meta-crownbay/README +3
-0+http://www.yoctoproject.org/yocto-project-compatible-registration + + Dependencies ============@@ -22,7 +31,7 @@ This layer depends on: branch: masterQuoted 8 lines
Quoted 7 lines
meta-crownbay/README This layer depends on: · line 37
Quoted 6 lines
meta-crownbay/README +1
-1URI: git://git.yoctoproject.org/meta-intel - layers: intel + layers: meta-intel, meta-crownbay branch: master_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
Re: [PATCH 3/6] crownbay README: add WebTitle & Compliance information
Quoted 151 lines
-----Original Message-----
From: [email protected] [mailto:yocto- [email protected]] On Behalf Of Sean Liming
Sent: Wednesday, October 24, 2012 11:16 AM
To: [email protected]
Subject: Re: [yocto] [PATCH 3/6] crownbay README: add WebTitle & Compliance informationQuoted 27 lines
-----Original Message-----
From: [email protected] [mailto:yocto- [email protected]] On Behalf Of Tom Zanussi
Sent: Wednesday, October 24, 2012 9:43 AM
To: Kamble, Nitin A
Cc: [email protected]; Hart, Darren
Subject: Re: [yocto] [PATCH 3/6] crownbay README: add WebTitle & Compliance informationQuoted 9 lines · Nitin A
Quoted 9 lines
-----Original Message-----
From: Zanussi, Tom
Sent: Tuesday, October 23, 2012 2:16 PM
To: Kamble, Nitin A
Cc: [email protected]; Hart, Darren
Subject: Re: [PATCH 3/6] crownbay README: add WebTitle & Compliance informationQuoted 5 lines
Quoted 5 lines · On Tue, 2012-10-23 at 13:24 -0700, [email protected] wrote:
Quoted 4 lines
From: Nitin A Kamble <[email protected]>
The WebTitle will be used to publish the BSP on the Yocto Project
Website.
Quoted 1 line
Quoted 1 line
Quoted 1 line
And adding the Yocto Project Compliance information for the 1.3
release.
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
meta-crownbay/README
Quoted 8 lines
Also specifying all the layers used from meta-intel repository.
Signed-off-by Nitin A Kamble <[email protected]>--- meta-crownbay/README | 13 +++++++++++-- 1 files changed, 11 insertions(+), 2 deletions(-)meta-crownbay/README +0
-0index
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 6 lines
4bc9f31..3996a94 100644
meta-crownbay/README +0
-0@@ -2,13 +2,22 @@ This README file contains information onbuilding the meta-crownbay BSP layer, and booting the images contained in the
/binary directory.
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
meta-crownbay/README
Quoted 7 lines
Please see the corresponding sections below for details.
-The Crown Bay platform consists of the Intel Atom Z6xx processor,
meta-crownbay/README +2
-0+The Crown Bay platform consists of the Intel Atom E6xx +processor, plus the Intel EG20T Platform Controller Hub (Tunnel Creek +Topcliff).
Quoted 76 lines
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
It also supports the E6xx embedded on-chip graphics via the
Intel Embedded Media and Graphics Driver (EMGD) 1.14 Driver.Quoted 8 lines
Quoted 8 lines
meta-crownbay/README
Quoted 3 lines
meta-crownbay/README +3
-0+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_crownbayand WebTitle_crownbay-noemgd
Quoted 26 lines
Quoted 6 lines
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.
Quoted 6 lines
#@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 NotesQuoted 2 lines
So there is one BSP list item per h/w with multiple links to different BSP
tarballs for the same hardware.
Quoted 2 lines
If we move the WebTitle in machine file, then we will have multiple items
in the BSP list for the same hardware.
Quoted 2 lines
I am not sure which is better from the downloader's point of view. But this
is worth considering for this change.
Quoted 1 line
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?)Quoted 2 lines
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.
Quoted 6 lines
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
Quoted 52 lines
Quoted 43 lines
Quoted 16 lines
Quoted 10 lines
meta-crownbay/README This README file contains information on building the meta-crownbay · line 16
Quoted 7 lines
meta-crownbay/README +3
-0+ +Compliance: +============For consistency with the rest of the README, please remove the colon and clean up the underlining.
Will do.
Thanks,
NitinQuoted 1 line
Quoted 6 lines
Quoted 6 lines
Thanks,
Tom
meta-crownbay/README
Quoted 2 lines
meta-crownbay/README +2
-0+This BSP is compliant with Yocto Project as per requirements +listedhere:
Quoted 10 lines
Quoted 10 lines
Quoted 10 lines
meta-crownbay/README +4
-0+http://www.yoctoproject.org/yocto-project-compatible-registrati +on + + Dependencies ============@@ -22,7 +31,7 @@ This layer depends on: branch: masterQuoted 8 lines
Quoted 7 lines
meta-crownbay/README This layer depends on: · line 37
Quoted 6 lines
meta-crownbay/README +1
-1URI: git://git.yoctoproject.org/meta-intel - layers: intel + layers: meta-intel, meta-crownbay branch: masterQuoted 4 lines
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
Re: [PATCH 3/6] crownbay README: add WebTitle & Compliance information
Quoted 128 lines
-----Original Message-----
From: Sean Liming [mailto:[email protected]]
Sent: Wednesday, October 24, 2012 11:51 AM
To: 'Kamble, Nitin A'
Subject: RE: [yocto] [PATCH 3/6] crownbay README: add WebTitle & Compliance informationQuoted 117 lines
-----Original Message-----
From: Kamble, Nitin A [mailto:[email protected]]
Sent: Wednesday, October 24, 2012 11:38 AM
To: Sean Liming; [email protected]
Subject: RE: [yocto] [PATCH 3/6] crownbay README: add WebTitle & Compliance informationQuoted 108 lines
-----Original Message-----
From: [email protected] [mailto:yocto- [email protected]] On Behalf Of Sean Liming
Sent: Wednesday, October 24, 2012 11:16 AM
To: [email protected]
Subject: Re: [yocto] [PATCH 3/6] crownbay README: add WebTitle & Compliance informationQuoted 28 lines
-----Original Message-----
From: [email protected] [mailto:yocto- [email protected]] On Behalf Of Tom Zanussi
Sent: Wednesday, October 24, 2012 9:43 AM
To: Kamble, Nitin A
Cc: [email protected]; Hart, Darren
Subject: Re: [yocto] [PATCH 3/6] crownbay README: add WebTitle & Compliance informationQuoted 9 lines · Nitin A
Quoted 9 lines
-----Original Message-----
From: Zanussi, Tom
Sent: Tuesday, October 23, 2012 2:16 PM
To: Kamble, Nitin A
Cc: [email protected]; Hart, Darren
Subject: Re: [PATCH 3/6] crownbay README: add WebTitle & Compliance informationQuoted 5 lines
Quoted 5 lines · On Tue, 2012-10-23 at 13:24 -0700, [email protected] wrote:
Quoted 4 lines
From: Nitin A Kamble <[email protected]>
The WebTitle will be used to publish the BSP on the Yocto Project
Website.
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
And adding the Yocto Project Compliance information for the 1.3
release.
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
meta-crownbay/README
Quoted 8 lines
Also specifying all the layers used from meta-intel repository.
Signed-off-by Nitin A Kamble <[email protected]>--- meta-crownbay/README | 13 +++++++++++-- 1 files changed, 11 insertions(+), 2 deletions(-)meta-crownbay/README +0
-0index
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 6 lines
4bc9f31..3996a94 100644
meta-crownbay/README +0
-0@@ -2,13 +2,22 @@ This README file contains information onbuilding the meta-crownbay BSP layer, and booting the images contained in the
/binary directory.
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
meta-crownbay/README
Quoted 8 lines
Please see the corresponding sections below for details.
-The Crown Bay platform consists of the Intel Atom Z6xx processor,
meta-crownbay/README +3
-0+The Crown Bay platform consists of the Intel Atom E6xx +processor, plus the Intel EG20T Platform Controller Hub (Tunnel Creek +Topcliff).
Quoted 47 lines
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
It also supports the E6xx embedded on-chip graphics via the
Intel Embedded Media and Graphics Driver (EMGD) 1.14 Driver.Quoted 9 lines
Quoted 9 lines
meta-crownbay/README
Quoted 3 lines
meta-crownbay/README +3
-0+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_crownbayand WebTitle_crownbay-noemgd
Quoted 26 lines
Quoted 6 lines
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.
Quoted 6 lines
#@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 NotesQuoted 2 lines
So there is one BSP list item per h/w with multiple links to different BSP
tarballs for the same hardware.
Quoted 2 lines
If we move the WebTitle in machine file, then we will have multiple items
in the BSP list for the same hardware.
Quoted 67 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 2 lines
I am not sure which is better from the downloader's point of view. But this
is worth considering for this change.
Quoted 1 line
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.
Quoted 59 lines
Quoted 11 lines
Quoted 11 lines
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:
Quoted 8 lines
Quoted 8 lines
Intel® Atom™ Processor N2000 and D2000 Series-based Platform (CEDAR
TRAIL) with VESA GraphicsI'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.
Quoted 7 lines
Quoted 7 lines
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?)Quoted 7 lines
Quoted 2 lines
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.
Quoted 8 lines
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.
Quoted 6 lines
Regards,
Sean Liming
Owner
Annabooks
Tel: 714-970-7523 / Cell: 858-774-3176Sean,
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/emgdThanks,
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
Quoted 53 lines
Quoted 53 lines
Quoted 53 lines
Quoted 44 lines
Quoted 15 lines
Quoted 9 lines
meta-crownbay/README This README file contains information on building the meta-crownbay · line 16
Quoted 6 lines
meta-crownbay/README +3
-0+ +Compliance: +============For consistency with the rest of the README, please remove the colon and clean up the underlining.
Will do.
Thanks,
NitinQuoted 1 line
Quoted 6 lines
Quoted 6 lines
Thanks,
Tom
meta-crownbay/README
Quoted 2 lines
meta-crownbay/README +2
-0+This BSP is compliant with Yocto Project as per +requirements listedhere:
Quoted 12 lines
Quoted 12 lines
Quoted 12 lines
meta-crownbay/README +6
-0+http://www.yoctoproject.org/yocto-project-compatible-regist +ra +ti +on + + Dependencies ============@@ -22,7 +31,7 @@ This layer depends on: branch: masterQuoted 8 lines
Quoted 7 lines
meta-crownbay/README This layer depends on: · line 37
Quoted 6 lines
meta-crownbay/README +1
-1URI: git://git.yoctoproject.org/meta-intel - layers: intel + layers: meta-intel, meta-crownbay branch: masterQuoted 4 lines
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
Re: [PATCH 3/6] crownbay README: add WebTitle & Compliance information
In reply to Sean LimingQuoted 118 lines · Sean Liming
Quoted 118 lines
-----Original Message-----
From: [email protected] [mailto:yocto- [email protected]] On Behalf Of Tom Zanussi
Sent: Wednesday, October 24, 2012 9:43 AM
To: Kamble, Nitin A
Cc: [email protected]; Hart, Darren
Subject: Re: [yocto] [PATCH 3/6] crownbay README: add WebTitle & Compliance informationQuoted 9 lines · Nitin A
Quoted 9 lines
-----Original Message-----
From: Zanussi, Tom
Sent: Tuesday, October 23, 2012 2:16 PM
To: Kamble, Nitin A
Cc: [email protected]; Hart, Darren
Subject: Re: [PATCH 3/6] crownbay README: add WebTitle & Compliance informationQuoted 4 lines
Quoted 4 lines · On Tue, 2012-10-23 at 13:24 -0700, [email protected] wrote:
Quoted 3 lines
From: Nitin A Kamble <[email protected]>
The WebTitle will be used to publish the BSP on the Yocto Project
Website.
Quoted 1 line
Quoted 1 line
Quoted 1 line
And adding the Yocto Project Compliance information for the 1.3
release.
Quoted 25 lines
Quoted 25 lines
Quoted 12 lines
Also specifying all the layers used from meta-intel repository.
Signed-off-by Nitin A Kamble <[email protected]>--- meta-crownbay/README | 13 +++++++++++-- 1 files changed, 11 insertions(+), 2 deletions(-)meta-crownbay/README index renamed from meta-crownbay/README +0
-04bc9f31..3996a94 100644
meta-crownbay/README +0
-0@@ -2,13 +2,22 @@ This README file contains information onQuoted 2 lines
building the meta-crownbay BSP layer, and booting the images contained in the
/binary directory.
Quoted 10 lines
Please see the corresponding sections below for details.
meta-crownbay/README +1
-1-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 IntelEmbedded Media and Graphics Driver (EMGD) 1.14 Driver.
Quoted 8 lines
Quoted 8 lines
meta-crownbay/README
Quoted 3 lines
meta-crownbay/README +3
-0+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_crownbayand WebTitle_crownbay-noemgd
Quoted 26 lines
Quoted 6 lines
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.
Quoted 6 lines
#@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 NotesQuoted 1 line
So there is one BSP list item per h/w with multiple links to different BSP
tarballs for the same hardware.
Quoted 1 line
If we move the WebTitle in machine file, then we will have multiple items
in the BSP list for the same hardware.
Quoted 1 line
I am not sure which is better from the downloader's point of view. But this
is worth considering for this change.
Quoted 1 line
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?)
Quoted 5 lines
Quoted 2 lines
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?
Quoted 2 lines
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
Quoted 56 lines
Regards,
Sean Liming
Owner
Annabooks
Tel: 714-970-7523 / Cell: 858-774-3176Quoted 38 lines
Quoted 8 lines
Quoted 7 lines
meta-crownbay/README This README file contains information on building the meta-crownbay · line 16
Quoted 4 lines
meta-crownbay/README +3
-0+ +Compliance: +============For consistency with the rest of the README, please remove the colon and clean up the underlining.
Quoted 10 lines
Will do.
Thanks,
NitinQuoted 6 lines
Thanks,
Tom
Quoted 1 line
+This BSP is compliant with Yocto Project as per requirements listed
here:
Quoted 9 lines
Quoted 9 lines
Quoted 9 lines
meta-crownbay/README +3
-0+http://www.yoctoproject.org/yocto-project-compatible-registration + + Dependencies ============@@ -22,7 +31,7 @@ This layer depends on: branch: masterQuoted 8 lines
Quoted 7 lines
meta-crownbay/README This layer depends on: · line 37
Quoted 6 lines
meta-crownbay/README +1
-1URI: git://git.yoctoproject.org/meta-intel - layers: intel + layers: meta-intel, meta-crownbay branch: masterQuoted 4 lines
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
PATCH 4/6 emenlow README: add WebTitle & Compliance information
In reply to [email protected]From: Nitin A Kamble <[email protected]>
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.
--- meta-emenlow/README | 11 ++++++++++- 1 files changed, 10 insertions(+), 1 deletions(-)
meta-emenlow/README +10 -1
@@ -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
Signature · 1 line
1.7.3.4
PATCH 5/6 jasperforest README: add WebTitle & Compliance information
In reply to [email protected]From: Nitin A Kamble <[email protected]>
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.
--- meta-jasperforest/README | 11 ++++++++++- 1 files changed, 10 insertions(+), 1 deletions(-)
meta-jasperforest/README +10 -1
@@ -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
Signature · 1 line
1.7.3.4
PATCH 6/6 sugarbay README: add WebTitle & Compliance information
In reply to [email protected]From: Nitin A Kamble <[email protected]>
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.
--- meta-sugarbay/README | 9 ++++++++- 1 files changed, 8 insertions(+), 1 deletions(-)
meta-sugarbay/README +8 -1
@@ -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
Signature · 1 line
1.7.3.4
Re: [PATCH 6/6] sugarbay README: add WebTitle & Compliance information
Quoted 16 lines · On 10/23/2012 01:24 PM, [email protected] wrote:
From: Nitin A Kamble <[email protected]>
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 <[email protected]>--- meta-sugarbay/README | 9 ++++++++- 1 files changed, 8 insertions(+), 1 deletions(-)meta-sugarbay/README +0
-0
meta-sugarbay/README The 'Sugar Bay' platform consists of the Intel Sandy Bridge processor, · line 9
Quoted 4 lines
meta-sugarbay/README +1
-0@@ -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
Quoted 19 lines
meta-sugarbay/README +7
-1+ +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
Signature · 3 lines
Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel
These commits are for both danny & master branches of meta-intel.
Thanks,
Nitin
Quoted 43 lines
-----Original Message-----
From: Kamble, Nitin A
Sent: Tuesday, October 23, 2012 1:25 PM
To: [email protected]; Zanussi, Tom; Hart, Darren
Cc: Kamble, Nitin A
Subject: [PATCH 0/6] meta-intel: README updatesFrom: Nitin A Kamble <[email protected]>
For the YP 1.3 release, README changes for the BSPs I am maintaining.
Thanks,
NitinThe 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-contribnitin/misc
http://git.yoctoproject.org/cgit.cgi/meta-intel-contrib/log/?h=nitin/miscNitin 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 informationMAINTAINERS | 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