Skip to contentSkip to conversation

why does dev manual, "Supported Board Support Packages", mention only meta-intel?

DISCUSSION Robert P. J. Day 3 participants 8 messages Jul 30, 2014 – Aug 1, 2014

lore
Share & tools
lore
#0 lore raw

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

Signature · 7 lines
========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================
#1 lore raw
Quoted 6 lines · Robert P. J. Day

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.

Quoted 18 lines

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
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

#2 lore raw
In reply to Robert P. J. Day

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

Quoted 34 lines

-----Original Message-----
From: [email protected] [mailto:yocto- [email protected]] 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
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

#3 lore raw
Quoted 1 line · Scott M

The point of the section is to show how to set up the meta-intel repository

I think it should cover the general case.

#4 lore raw

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.

Quoted 14 lines

-----Original Message-----
From: Khem Raj [mailto:[email protected]]
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?

Quoted 2 lines · Scott M

The point of the section is to show how to set up the meta-intel repository

I think it should cover the general case.

#7 lore raw
In reply to Rifenbark, Scott M
Quoted 7 lines · Scott M

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

Signature · 7 lines
========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================
#5 lore raw
In reply to Rifenbark, Scott M

(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.)

Quoted 3 lines · Scott M

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

Signature · 7 lines
========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================
#6 lore raw

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

Quoted 76 lines

-----Original Message-----
From: Robert P. J. Day [mailto:[email protected]]
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.)

Quoted 3 lines · Scott M

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

=================================================================
=======