From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail32c40.carrierzone.com (mail32c40.carrierzone.com [209.235.156.172]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id DD8DEE0032E for ; Wed, 24 Oct 2012 11:15:48 -0700 (PDT) X-Authenticated-User: sean.liming.annabooks.com Received: from Sean7 (cpe-76-95-171-22.socal.res.rr.com [76.95.171.22]) (authenticated bits=0) by mail32c40.carrierzone.com (8.13.6/8.13.1) with ESMTP id q9OIFjQx003575 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 24 Oct 2012 18:15:47 +0000 From: "Sean Liming" To: References: <1351026976.12186.70.camel@empanada> <1351096988.27553.19.camel@empanada> In-Reply-To: <1351096988.27553.19.camel@empanada> Date: Wed, 24 Oct 2012 11:15:39 -0700 Message-ID: <001501cdb213$93910550$bab30ff0$@annabooks.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQFbfpUGFmH3ZqVl06eUkhwgp2VYUQMW0MNcAl6wct8CRLsElgKtssYimFnn0kA= X-Antivirus: avast! (VPS 121024-0, 10/24/2012), Outbound message X-Antivirus-Status: Clean X-CSC: 0 X-CHA: v=1.1 cv=3heS3dTvrDjrvHauwyvFpNTURI2p5t08AU+DPyrsBaI= c=1 sm=1 a=dJzlXwD_2c0A:10 a=_DgR7O7FQkkA:10 a=IkcTkHD0fZMA:10 a=RqNIojzclRO/fVsPhA7IgQ==:17 a=iGHA9ds3AAAA:8 a=QyXUC8HyAAAA:8 a=6wmpYKpkKqaopk9cU0MA:9 a=QEXdDO2ut3YA:10 a=FCaQVidmf_IA:10 a=nHK3ipOpxeAA:10 a=XDKM753qmDAA:10 a=dGJ0OcVc7YAA:10 a=RqNIojzclRO/fVsPhA7IgQ==:117 X-CTCH-Spam: Unknown X-CTCH-RefID: str=0001.0A020201.50883053.007F, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0 Subject: Re: [PATCH 3/6] crownbay README: add WebTitle & Compliance information X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Oct 2012 18:15:49 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Content-Language: en-us > -----Original Message----- > From: yocto-bounces@yoctoproject.org [mailto:yocto- > bounces@yoctoproject.org] On Behalf Of Tom Zanussi > Sent: Wednesday, October 24, 2012 9:43 AM > To: Kamble, Nitin A > Cc: yocto@yoctoproject.org; Hart, Darren > Subject: Re: [yocto] [PATCH 3/6] crownbay README: add WebTitle & > Compliance information >=20 > On Wed, 2012-10-24 at 11:06 -0500, Kamble, Nitin A wrote: > > > > > -----Original Message----- > > > From: Zanussi, Tom > > > Sent: Tuesday, October 23, 2012 2:16 PM > > > To: Kamble, Nitin A > > > Cc: yocto@yoctoproject.org; Hart, Darren > > > Subject: Re: [PATCH 3/6] crownbay README: add WebTitle & = Compliance > > > information > > > > > > On Tue, 2012-10-23 at 13:24 -0700, nitin.a.kamble@intel.com wrote: > > > > From: Nitin A Kamble > > > > > > > > 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 > > > > --- > > > > meta-crownbay/README | 13 +++++++++++-- > > > > 1 files changed, 11 insertions(+), 2 deletions(-) > > > > > > > > diff --git a/meta-crownbay/README b/meta-crownbay/README index > > > > 4bc9f31..3996a94 100644 > > > > --- a/meta-crownbay/README > > > > +++ b/meta-crownbay/README > > > > @@ -2,13 +2,22 @@ This README file contains information on > > > > building the meta-crownbay BSP layer, and booting the images > > > > contained in the > > > /binary directory. > > > > Please see the corresponding sections below for details. > > > > > > > > -The Crown Bay platform consists of the Intel Atom Z6xx = processor, > > > > +The Crown Bay platform consists of the Intel Atom E6xx = processor, > > > > plus the Intel EG20T Platform Controller Hub (Tunnel Creek + = Topcliff). > > > > > > > > It also supports the E6xx embedded on-chip graphics via the = Intel > > > > Embedded Media and Graphics Driver (EMGD) 1.14 Driver. > > > > > > > > > > > > +WebTitle: Intel Atom E6xx processor with Intel EG20T Controller > > > > +Hub development kit (crownbay) > > > > + > > > > > > I'm not sure this kind of thing should be in the README since we = can > > > have multiple downloadable BSPs per layer e.g. crownbay vs > > > crownbay-noemgd. I suppose in keeping with the build system you > > > could have separate WebTitle_crownbay and WebTitle_crownbay- > noemgd > > > lines. ;-) (and it would be nice if you could get rid of the > > > CamelCaps too) > > > > > > Why not put this info in the machine.conf, where we already have > > > fields meant to be machine parseable e.g. > > > > > > #@TYPE: Machine > > > #@NAME: crownbay > > > > > > #@WEBTITLE: ... > > > > > > Or maybe just use the exisiting #@DESCRIPTION for that... > > > > For example in the current way the BSPs are published, this is shown > > on the YP website for crownbay > > > > Intel Atom Processor E660 with Intel Platform Controller Hub EG20T > > Development Kit > > Version: 7.0 "Denzil" > > Release date: 29 Jun 2012 > > Type: BSP > > Download Links: > > Crown Bay > > Crown Bay no EMGD > > Release Notes > > > > So there is one BSP list item per h/w with multiple links to = different BSP > tarballs for the same hardware. > > If we move the WebTitle in machine file, then we will have multiple = items > in the BSP list for the same hardware. > > I am not sure which is better from the downloader's point of view. = But this > is worth considering for this change. > > >=20 > 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. >=20 > But we should consider whether we want to lay things out as the = crownbay > above, or more like the cedartrail, which has: >=20 > Intel=C2=AE Atom=E2=84=A2 Processor N2000 and D2000 Series-based = Platform (CEDAR > TRAIL) with PowerVR Graphics >=20 > (there's no corresponding -nopvr version available, though I suspect = that's an > oversight and would have been something like: >=20 > Intel=C2=AE Atom=E2=84=A2 Processor N2000 and D2000 Series-based = Platform (CEDAR > TRAIL) with VESA Graphics >=20 > 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?) >=20 > Tom >=20 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.=20 Also, it would help to know how the EMGD has been configure in the BSP = and for what output ports. Having worked with EMGD there are many = options. For the SYS940X-ECX, the video driver (VGA-output) doesn't load = so X doesn't start. It would be nice to use EMGD to configure this = myself and then add the driver, but if this can already be down in the = configuration file, it is not clear how to do this. Regards, Sean Liming Owner Annabooks Tel: 714-970-7523 / Cell: 858-774-3176 > > > > > > > + > > > > +Compliance: > > > > +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > > > > > For consistency with the rest of the README, please remove the = colon > > > and clean up the underlining. > > > > Will do. > > > > Thanks, > > Nitin > > > > > > Thanks, > > > > > > Tom > > > > > > > +This BSP is compliant with Yocto Project as per requirements = listed > here: > > > > = +http://www.yoctoproject.org/yocto-project-compatible-registration > > > > + > > > > + > > > > Dependencies > > > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > > > > > > > @@ -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 > > > > > > > > > > > > > >=20 >=20 > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto