* why does dev manual, "Supported Board Support Packages", mention only meta-intel?
@ 2014-07-30 19:24 Robert P. J. Day
2014-07-30 20:06 ` Khem Raj
2014-07-31 5:50 ` Rifenbark, Scott M
0 siblings, 2 replies; 8+ messages in thread
From: Robert P. J. Day @ 2014-07-30 19:24 UTC (permalink / raw)
To: Yocto discussion list
also from current dev manual, chapter 2, there is a bullet point
entitled "Supported Board Support Packages" which mentions *only*
meta-intel as if its the only such layer.
that seems sort of ... incomplete.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: why does dev manual, "Supported Board Support Packages", mention only meta-intel? 2014-07-30 19:24 why does dev manual, "Supported Board Support Packages", mention only meta-intel? Robert P. J. Day @ 2014-07-30 20:06 ` Khem Raj 2014-07-31 5:50 ` Rifenbark, Scott M 1 sibling, 0 replies; 8+ messages in thread From: Khem Raj @ 2014-07-30 20:06 UTC (permalink / raw) To: Robert P. J. Day; +Cc: Yocto discussion list On Wed, Jul 30, 2014 at 12:24 PM, Robert P. J. Day <rpjday@crashcourse.ca> wrote: > > also from current dev manual, chapter 2, there is a bullet point > entitled "Supported Board Support Packages" which mentions *only* > meta-intel as if its the only such layer. > > that seems sort of ... incomplete. a list from something like this http://downloads.yoctoproject.org/releases/yocto/yocto-1.6.1/machines/ would be more appropriate. > > rday > > -- > > ======================================================================== > Robert P. J. Day Ottawa, Ontario, CANADA > http://crashcourse.ca > > Twitter: http://twitter.com/rpjday > LinkedIn: http://ca.linkedin.com/in/rpjday > ======================================================================== > > -- > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: why does dev manual, "Supported Board Support Packages", mention only meta-intel? 2014-07-30 19:24 why does dev manual, "Supported Board Support Packages", mention only meta-intel? Robert P. J. Day 2014-07-30 20:06 ` Khem Raj @ 2014-07-31 5:50 ` Rifenbark, Scott M 2014-07-31 6:35 ` Khem Raj 2014-07-31 7:07 ` Robert P. J. Day 1 sibling, 2 replies; 8+ messages in thread From: Rifenbark, Scott M @ 2014-07-31 5:50 UTC (permalink / raw) To: Robert P. J. Day, Yocto discussion list The bold title of the bullet item should probably not be so restrictive. The point of the section is to show how to set up the meta-intel repository. I can re-write this section to indicate the wider BSP support and still use the main meta-intel git clone example. Scott >-----Original Message----- >From: yocto-bounces@yoctoproject.org [mailto:yocto- >bounces@yoctoproject.org] On Behalf Of Robert P. J. Day >Sent: Wednesday, July 30, 2014 12:25 PM >To: Yocto discussion list >Subject: [yocto] why does dev manual, "Supported Board Support Packages", >mention only meta-intel? > > > also from current dev manual, chapter 2, there is a bullet point entitled >"Supported Board Support Packages" which mentions *only* meta-intel as if its >the only such layer. > > that seems sort of ... incomplete. > >rday > >-- > >================================================================= >======= >Robert P. J. Day Ottawa, Ontario, CANADA > http://crashcourse.ca > >Twitter: http://twitter.com/rpjday >LinkedIn: http://ca.linkedin.com/in/rpjday >================================================================= >======= > >-- >_______________________________________________ >yocto mailing list >yocto@yoctoproject.org >https://lists.yoctoproject.org/listinfo/yocto ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: why does dev manual, "Supported Board Support Packages", mention only meta-intel? 2014-07-31 5:50 ` Rifenbark, Scott M @ 2014-07-31 6:35 ` Khem Raj 2014-07-31 6:42 ` Rifenbark, Scott M 2014-07-31 7:07 ` Robert P. J. Day 1 sibling, 1 reply; 8+ messages in thread From: Khem Raj @ 2014-07-31 6:35 UTC (permalink / raw) To: Rifenbark, Scott M; +Cc: Yocto discussion list On Wed, Jul 30, 2014 at 10:50 PM, Rifenbark, Scott M <scott.m.rifenbark@intel.com> wrote: > The point of the section is to show how to set up the meta-intel repository I think it should cover the general case. ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: why does dev manual, "Supported Board Support Packages", mention only meta-intel? 2014-07-31 6:35 ` Khem Raj @ 2014-07-31 6:42 ` Rifenbark, Scott M 2014-07-31 16:51 ` Robert P. J. Day 0 siblings, 1 reply; 8+ messages in thread From: Rifenbark, Scott M @ 2014-07-31 6:42 UTC (permalink / raw) To: Khem Raj; +Cc: Yocto discussion list Yes - that is what I meant by fixing it up to be less-restrictive. I need to find out some stuff on BSPs in general and then I will get to it. >-----Original Message----- >From: Khem Raj [mailto:raj.khem@gmail.com] >Sent: Wednesday, July 30, 2014 11:35 PM >To: Rifenbark, Scott M >Cc: Robert P. J. Day; Yocto discussion list >Subject: Re: [yocto] why does dev manual, "Supported Board Support Packages", >mention only meta-intel? > >On Wed, Jul 30, 2014 at 10:50 PM, Rifenbark, Scott M ><scott.m.rifenbark@intel.com> wrote: >> The point of the section is to show how to set up the meta-intel >> repository > >I think it should cover the general case. ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: why does dev manual, "Supported Board Support Packages", mention only meta-intel? 2014-07-31 6:42 ` Rifenbark, Scott M @ 2014-07-31 16:51 ` Robert P. J. Day 2014-08-01 6:10 ` Rifenbark, Scott M 0 siblings, 1 reply; 8+ messages in thread From: Robert P. J. Day @ 2014-07-31 16:51 UTC (permalink / raw) To: Rifenbark, Scott M; +Cc: Yocto discussion list (SIDE NOTE: i'm being this picky since i want to use these manuals straight out as training material, so i want them to be precise and accurate.) On Thu, 31 Jul 2014, Rifenbark, Scott M wrote: > Yes - that is what I meant by fixing it up to be less-restrictive. > I need to find out some stuff on BSPs in general and then I will get > to it. looking at that entire section 2.2 in the dev manual ("Getting Set Up"), it might be worth stepping back and asking what that section is meant to accomplish -- one would think, listing the really basic stuff one needs to, say, build their first image. with that in mind, the list in that section seems a bit odd in places, and a couple other notes about it. first, "You should also have about 50 Gbytes of free disk space for building images" seems a bit, um, harsh. you can build an entire bootable qemuarm image in less than 16G, so scaring the reader by mentioning 50G seems slightly extreme. next, given that first-time users are probably going to just go with the kernel provided and configured for their machine of choice, it's not clear that that section needs to get into checking out a kernel manually, or mentioning meta-yocto-kernel-extras. but that's just me. finally, about BSPs, i'm not sure what that section needs to say at this point beyond, "depending on what MACHINE you're building for, you may need to manually check out the specific BSP layer for that machine," then just point the reader at the layers page. it might be sufficient to say something like: "in terms of BSPs, you will already have support for a number of machines. OE provides support for a number of QEMU images, while the yocto layer adds support for five 'reference' boards [LIST THEM]. beyond that, you will need to locate and download the BSP layer for the machine you want." if you truly want to give an example of downloading a BSP layer, pick a *simple* one -- i always use meta-raspberrypi since it is a single checkout that defines a single machine. with all due respect, using meta-intel as an example is probably the worst choice in that it is a single checkout that is a layer, with numerous sublayers as part of the checkout, and do you really want to get into that? anyway, i would keep that entire section as simple as possible, and refer readers to the more advanced sections in other manuals. movin' on ... rday -- ======================================================================== Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ======================================================================== ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: why does dev manual, "Supported Board Support Packages", mention only meta-intel? 2014-07-31 16:51 ` Robert P. J. Day @ 2014-08-01 6:10 ` Rifenbark, Scott M 0 siblings, 0 replies; 8+ messages in thread From: Rifenbark, Scott M @ 2014-08-01 6:10 UTC (permalink / raw) To: Robert P. J. Day; +Cc: Yocto discussion list This section probably does need a fresh look in light of the current manual structure now. When I wrote it, I had some detailed examples in the dev-manual that stepped people through building a kernel image and an image for crown-bay. Those detailed examples have gone by the wayside. I will take a look at this section. Scott >-----Original Message----- >From: Robert P. J. Day [mailto:rpjday@crashcourse.ca] >Sent: Thursday, July 31, 2014 9:52 AM >To: Rifenbark, Scott M >Cc: Khem Raj; Yocto discussion list >Subject: RE: [yocto] why does dev manual, "Supported Board Support Packages", >mention only meta-intel? > > >(SIDE NOTE: i'm being this picky since i want to use these manuals straight out >as training material, so i want them to be precise and >accurate.) > >On Thu, 31 Jul 2014, Rifenbark, Scott M wrote: > >> Yes - that is what I meant by fixing it up to be less-restrictive. >> I need to find out some stuff on BSPs in general and then I will get >> to it. > > looking at that entire section 2.2 in the dev manual ("Getting Set Up"), it might >be worth stepping back and asking what that section is meant to accomplish -- >one would think, listing the really basic stuff one needs to, say, build their first >image. > > with that in mind, the list in that section seems a bit odd in places, and a couple >other notes about it. > > first, "You should also have about 50 Gbytes of free disk space for building >images" seems a bit, um, harsh. you can build an entire bootable qemuarm >image in less than 16G, so scaring the reader by mentioning 50G seems slightly >extreme. > > next, given that first-time users are probably going to just go with the kernel >provided and configured for their machine of choice, it's not clear that that >section needs to get into checking out a kernel manually, or mentioning meta- >yocto-kernel-extras. but that's just me. > > finally, about BSPs, i'm not sure what that section needs to say at this point >beyond, "depending on what MACHINE you're building for, you may need to >manually check out the specific BSP layer for that machine," then just point the >reader at the layers page. > > it might be sufficient to say something like: > > "in terms of BSPs, you will already have support for a number of machines. OE >provides support for a number of QEMU images, while the yocto layer adds >support for five 'reference' boards [LIST THEM]. >beyond that, you will need to locate and download the BSP layer for the machine >you want." > > if you truly want to give an example of downloading a BSP layer, pick a >*simple* one -- i always use meta-raspberrypi since it is a single checkout that >defines a single machine. with all due respect, using meta-intel as an example is >probably the worst choice in that it is a single checkout that is a layer, with >numerous sublayers as part of the checkout, and do you really want to get into >that? > > anyway, i would keep that entire section as simple as possible, and refer >readers to the more advanced sections in other manuals. > > movin' on ... > >rday > >-- > >================================================================= >======= >Robert P. J. Day Ottawa, Ontario, CANADA > http://crashcourse.ca > >Twitter: http://twitter.com/rpjday >LinkedIn: http://ca.linkedin.com/in/rpjday >================================================================= >======= > ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: why does dev manual, "Supported Board Support Packages", mention only meta-intel? 2014-07-31 5:50 ` Rifenbark, Scott M 2014-07-31 6:35 ` Khem Raj @ 2014-07-31 7:07 ` Robert P. J. Day 1 sibling, 0 replies; 8+ messages in thread From: Robert P. J. Day @ 2014-07-31 7:07 UTC (permalink / raw) To: Rifenbark, Scott M; +Cc: Yocto discussion list On Thu, 31 Jul 2014, Rifenbark, Scott M wrote: > The bold title of the bullet item should probably not be so > restrictive. The point of the section is to show how to set up the > meta-intel repository. I can re-write this section to indicate the > wider BSP support and still use the main meta-intel git clone > example. > > Scott i think that's all that's necessary -- just not implying that meta-intel is the only possibility. rday -- ======================================================================== Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ======================================================================== ^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2014-08-01 6:10 UTC | newest] Thread overview: 8+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2014-07-30 19:24 why does dev manual, "Supported Board Support Packages", mention only meta-intel? Robert P. J. Day 2014-07-30 20:06 ` Khem Raj 2014-07-31 5:50 ` Rifenbark, Scott M 2014-07-31 6:35 ` Khem Raj 2014-07-31 6:42 ` Rifenbark, Scott M 2014-07-31 16:51 ` Robert P. J. Day 2014-08-01 6:10 ` Rifenbark, Scott M 2014-07-31 7:07 ` Robert P. J. Day
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.