Date   

[PATCH] DOCS: Tidy up a couple git commands in the kernel manual.

Robert P. J. Day
 

Fix missing prompt, missing "git" and break overly long command in
two since it disappears off the page in the PDF output.

Signed-off-by: Robert P. J. Day <rpjday@...>

---

these fixes should be self-evident.

diff --git a/documentation/kernel-manual/kernel-how-to.xml b/documentation/kernel-manual/kernel-how-to.xml
index 0cb7154..5a0d975 100644
--- a/documentation/kernel-manual/kernel-how-to.xml
+++ b/documentation/kernel-manual/kernel-how-to.xml
@@ -727,7 +727,7 @@ repository.
<para>
Use this command form to push the changes:
<literallayout class='monospaced'>
- git push ssh://&lt;master server&gt;/&lt;path to repo&gt; &lt;local branch&gt;:&lt;remote branch&gt;
+ &gt; git push ssh://&lt;master server&gt;/&lt;path to repo&gt; &lt;local branch&gt;:&lt;remote branch&gt;
</literallayout>
</para>

@@ -736,7 +736,8 @@ repository.
<filename>yocto/standard/common-pc/base</filename> to the remote branch with the same name
in the master repository <filename>//git.mycompany.com/pub/git/kernel-2.6.37</filename>.
<literallayout class='monospaced'>
- &gt; push ssh://git.mycompany.com/pub/git/kernel-2.6.37 yocto/standard/common-pc/base:yocto/standard/common-pc/base
+ &gt; git push ssh://git.mycompany.com/pub/git/kernel-2.6.37 \
+ yocto/standard/common-pc/base:yocto/standard/common-pc/base
</literallayout>
</para>


--

========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================


Re: IMAGE_FSTYPES that are supported?

Kumar Gala <galak@...>
 

On Jul 14, 2011, at 11:24 AM, Bruce Ashfield wrote:

On 07/14/11 12:21, Koen Kooi wrote:

Op 14 jul 2011, om 18:20 heeft Kumar Gala het volgende geschreven:


On Jul 14, 2011, at 8:56 AM, Bruce Ashfield wrote:

On 07/14/11 09:40, Koen Kooi wrote:

Op 14 jul 2011, om 15:13 heeft Bruce Ashfield het volgende geschreven:

On 07/14/11 09:05, Kumar Gala wrote:
Is there a list of which IMAGE_FSTYPES are supported. I didn't see anything in the docs. Looking to see if a u-boot 'mkimage' wrapped set of images is supported or not.
I'm not 100% where the list is, but I can confirm that
uImages are supported and work nicely. Assuming that
you are talking about the common use case, and not something
more exotic :)

I think he means partitioned uimages where you have a kernel + initrd in a single uimage. We don't support that *yet*, but all the needed blocks are there. And we finally get a usecase for having the loadadresses in the machine.conf files :)
Yah, that's what I wondered as well. I've done this locally,
but nothing out of the box .. so I had nagging doubts!

Cheers,

Bruce
What's the IMAGE_FSTYPE for a normal uImage ?
None, it's built by the kernel class, not the rootfs class.
and to expand a bit, the machine conf would have:

KERNEL_IMAGETYPE = "uImage"

So the kernel class will build and produce a uImage for deployment.
Ah, so there isnt support for getting a ramdisk wrapped via mkimage.

- k


Re: Menu configuration

Kumar Gala <galak@...>
 

On Jul 14, 2011, at 8:52 AM, Richard Purdie wrote:

On Thu, 2011-07-14 at 08:06 -0500, Kumar Gala wrote:
On Jul 12, 2011, at 3:43 AM, Richard Purdie wrote:

On Mon, 2011-07-11 at 10:00 -0700, Turner Randy wrote:
Hello list,

Is there a interactive menu-based configuration for yocto/poky builds
similar to that provided in Buildroot? Or is someone working on this?
At present there is not any interactive menu based configuration but
there is work ongoing on a UI called hob which allows you to select
packages and construct images of those packages so its a graphical front
end to the system.

We're also in the process of starting to better markup configuration
variables in the metadata so that writing some kind of menu based
configuration system would be easier in the future.

We're certainly open to any help in those areas too!

Cheers,

Richard
Are there any docs for hob at this point?
Not specifically. "bitbake -u hob" should let you see where things are
at. Please keep in mind that its under active development at the moment
and can be considered "alpha" quality but feedback is welcome.
Are they thread of email discussion or anything. I tried playing with it, but a little confused on exactly what its trying to accomplish and what the 'cfg' that is saved off ends up being.

- k


Re: IMAGE_FSTYPES that are supported?

Bruce Ashfield <bruce.ashfield@...>
 

On 07/14/11 12:21, Koen Kooi wrote:

Op 14 jul 2011, om 18:20 heeft Kumar Gala het volgende geschreven:


On Jul 14, 2011, at 8:56 AM, Bruce Ashfield wrote:

On 07/14/11 09:40, Koen Kooi wrote:

Op 14 jul 2011, om 15:13 heeft Bruce Ashfield het volgende geschreven:

On 07/14/11 09:05, Kumar Gala wrote:
Is there a list of which IMAGE_FSTYPES are supported. I didn't see anything in the docs. Looking to see if a u-boot 'mkimage' wrapped set of images is supported or not.
I'm not 100% where the list is, but I can confirm that
uImages are supported and work nicely. Assuming that
you are talking about the common use case, and not something
more exotic :)

I think he means partitioned uimages where you have a kernel + initrd in a single uimage. We don't support that *yet*, but all the needed blocks are there. And we finally get a usecase for having the loadadresses in the machine.conf files :)
Yah, that's what I wondered as well. I've done this locally,
but nothing out of the box .. so I had nagging doubts!

Cheers,

Bruce
What's the IMAGE_FSTYPE for a normal uImage ?
None, it's built by the kernel class, not the rootfs class.
and to expand a bit, the machine conf would have:

KERNEL_IMAGETYPE = "uImage"

So the kernel class will build and produce a uImage for deployment.

Cheers,

Bruce


Re: IMAGE_FSTYPES that are supported?

Koen Kooi
 

Op 14 jul 2011, om 18:20 heeft Kumar Gala het volgende geschreven:


On Jul 14, 2011, at 8:56 AM, Bruce Ashfield wrote:

On 07/14/11 09:40, Koen Kooi wrote:

Op 14 jul 2011, om 15:13 heeft Bruce Ashfield het volgende geschreven:

On 07/14/11 09:05, Kumar Gala wrote:
Is there a list of which IMAGE_FSTYPES are supported. I didn't see anything in the docs. Looking to see if a u-boot 'mkimage' wrapped set of images is supported or not.
I'm not 100% where the list is, but I can confirm that
uImages are supported and work nicely. Assuming that
you are talking about the common use case, and not something
more exotic :)

I think he means partitioned uimages where you have a kernel + initrd in a single uimage. We don't support that *yet*, but all the needed blocks are there. And we finally get a usecase for having the loadadresses in the machine.conf files :)
Yah, that's what I wondered as well. I've done this locally,
but nothing out of the box .. so I had nagging doubts!

Cheers,

Bruce
What's the IMAGE_FSTYPE for a normal uImage ?
None, it's built by the kernel class, not the rootfs class.


Re: IMAGE_FSTYPES that are supported?

Kumar Gala <galak@...>
 

On Jul 14, 2011, at 8:56 AM, Bruce Ashfield wrote:

On 07/14/11 09:40, Koen Kooi wrote:

Op 14 jul 2011, om 15:13 heeft Bruce Ashfield het volgende geschreven:

On 07/14/11 09:05, Kumar Gala wrote:
Is there a list of which IMAGE_FSTYPES are supported. I didn't see anything in the docs. Looking to see if a u-boot 'mkimage' wrapped set of images is supported or not.
I'm not 100% where the list is, but I can confirm that
uImages are supported and work nicely. Assuming that
you are talking about the common use case, and not something
more exotic :)

I think he means partitioned uimages where you have a kernel + initrd in a single uimage. We don't support that *yet*, but all the needed blocks are there. And we finally get a usecase for having the loadadresses in the machine.conf files :)
Yah, that's what I wondered as well. I've done this locally,
but nothing out of the box .. so I had nagging doubts!

Cheers,

Bruce
What's the IMAGE_FSTYPE for a normal uImage ?

- k


[PATCH 1/1] meta-emenlow: fix glx bug

tom.zanussi@...
 

From: Tom Zanussi <tom.zanussi@...>

AIGLX wasn't finding a couple libraries, causing errors such as Yocto
bug #1235 - 'Running glxinfo and glxgears commands failed.'. This
provides symlinks allowing it to find the needed libraries.

Fixes [YOCTO #1235]

Signed-off-by: Tom Zanussi <tom.zanussi@...>
---
.../libdrm-poulsbo/libdrm-poulsbo_2.3.0.bb | 6 +++++-
.../recipes-graphics/xpsb-glx/xpsb-glx_0.18.bb | 3 ++-
2 files changed, 7 insertions(+), 2 deletions(-)

diff --git a/meta-emenlow/recipes-graphics/libdrm-poulsbo/libdrm-poulsbo_2.3.0.bb b/meta-emenlow/recipes-graphics/libdrm-poulsbo/libdrm-poulsbo_2.3.0.bb
index d0e14a5..5153054 100644
--- a/meta-emenlow/recipes-graphics/libdrm-poulsbo/libdrm-poulsbo_2.3.0.bb
+++ b/meta-emenlow/recipes-graphics/libdrm-poulsbo/libdrm-poulsbo_2.3.0.bb
@@ -1,7 +1,7 @@
DESCRIPTION = "Userspace interface to kernel DRM services"
LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://MIT_License.txt;md5=732825ecdcf420261531d935fcd914a7"
-PR = "r4"
+PR = "r5"

PROVIDES = "libdrm-poulsbo"

@@ -17,3 +17,7 @@ do_configure_prepend() {
sed -e 's/-ldrm/-ldrm_poulsbo/' -e 's/libdrm/libdrm_poulsbo/' \
< ${S}/libdrm.pc.in > ${S}/libdrm_poulsbo.pc.in
}
+
+do_install_append() {
+ ln -s libdrm_poulsbo.so.2.3.0 ${D}${libdir}/libdrm.so.2
+}
diff --git a/meta-emenlow/recipes-graphics/xpsb-glx/xpsb-glx_0.18.bb b/meta-emenlow/recipes-graphics/xpsb-glx/xpsb-glx_0.18.bb
index f4b43ab..0d675c6 100644
--- a/meta-emenlow/recipes-graphics/xpsb-glx/xpsb-glx_0.18.bb
+++ b/meta-emenlow/recipes-graphics/xpsb-glx/xpsb-glx_0.18.bb
@@ -4,7 +4,7 @@ DESCRIPTION = "X11 drivers for Poulsbo (psb) 3D acceleration"
# not Intel proprietary, but it has no obvious license attached to it.
LICENSE = "Intel-binary-only"
LIC_FILES_CHKSUM = "file://${WORKDIR}/${PN}-${PV}/COPYING;md5=02c597a2f082b4581596065bb5a521a8"
-PR = "r6"
+PR = "r7"

inherit autotools

@@ -29,6 +29,7 @@ do_install() {
${D}/${libdir}/xorg/modules/dri
install -m 0644 ${WORKDIR}/${PN}-${PV}/drivers/* \
${D}/${libdir}/xorg/modules/drivers
+ ln -s ${libdir}/xorg/modules/dri ${D}${libdir}/dri
}

S = "${WORKDIR}/${PN}-${PV}/mesa"
--
1.7.0.4


[PATCH 0/1] emenlow glx bugfix

tom.zanussi@...
 

From: Tom Zanussi <tom.zanussi@...>

This is a fix for Yocto bug #1235.

The following changes since commit 92fc07a5f1b98779806cdcc2341487ff5ea5a238:
Dexuan Cui (1):
emenlow: fix some .bbappend files' name: poky -> core, etc.

are available in the git repository at:

git://git.yoctoproject.org/meta-intel.git tzanussi/bug-1235
http://git.yoctoproject.org/cgit.cgi/meta-intel/log/?h=tzanussi/bug-1235

Tom Zanussi (1):
meta-emenlow: fix glx bug

.../libdrm-poulsbo/libdrm-poulsbo_2.3.0.bb | 6 +++++-
.../recipes-graphics/xpsb-glx/xpsb-glx_0.18.bb | 3 ++-
2 files changed, 7 insertions(+), 2 deletions(-)


Re: docs: how to spell "bitbake", and docbook semantic markup for user input

Rifenbark, Scott M <scott.m.rifenbark@...>
 

Robert,

I know that and will work towards that end as well. There are a lot of holdover things in our docs.

Thanks,
Scott

-----Original Message-----
From: Robert P. J. Day [mailto:rpjday@...]
Sent: Thursday, July 14, 2011 7:29 AM
To: Rifenbark, Scott M
Cc: Richard Purdie; Darren Hart; yocto@...
Subject: RE: [yocto] docs: how to spell "bitbake", and docbook semantic markup for user input

On Thu, 14 Jul 2011, Rifenbark, Scott M wrote:

Agreed that BitBake is the correct spelling. I will be sure to make
a sweep through our Yocto manuals and make sure that when we are
referring to the tool and not indicating the command they say
"BitBake".
and while you're at it, i was once lectured sternly that the proper
spelling is "Git" when talking about the tool and "git" when referring
to the actual command. never "GIT". at least that what i was told.
do with that what you wish.

rday

p.s. since i am, at this very moment, immersed in an XML publishing
toolchain, i will probably have some thoughts on docbook markup in the
near future. stay tuned ...


Re: docs: how to spell "bitbake", and docbook semantic markup for user input

Robert P. J. Day
 

On Thu, 14 Jul 2011, Rifenbark, Scott M wrote:

Agreed that BitBake is the correct spelling. I will be sure to make
a sweep through our Yocto manuals and make sure that when we are
referring to the tool and not indicating the command they say
"BitBake".
and while you're at it, i was once lectured sternly that the proper
spelling is "Git" when talking about the tool and "git" when referring
to the actual command. never "GIT". at least that what i was told.
do with that what you wish.

rday

p.s. since i am, at this very moment, immersed in an XML publishing
toolchain, i will probably have some thoughts on docbook markup in the
near future. stay tuned ...


Re: [PATCH] scripts: Rename "adt-install" to "adt-installer" in user help.

Richard Purdie
 

On Wed, 2011-07-13 at 07:43 -0400, Robert P. J. Day wrote:
Signed-off-by: Robert P. J. Day <rpjday@...>

---

i'm hoping the following is correct -- it's just user help output so
it's not fatal but it should still be correct.

diff --git a/scripts/oe-setup-builddir b/scripts/oe-setup-builddir
index bc4962a..d278c24 100755
--- a/scripts/oe-setup-builddir
+++ b/scripts/oe-setup-builddir
@@ -118,7 +118,7 @@ Common targets are:
core-image-sato
meta-toolchain
meta-toolchain-sdk
- adt-install
+ adt-installer
meta-ide-support

You can also run generated qemu images with a command like 'runqemu qemux86'
Merged to master, thanks.

Richard


Re: docs: how to spell "bitbake", and docbook semantic markup for user input

Rifenbark, Scott M <scott.m.rifenbark@...>
 

Agreed that BitBake is the correct spelling. I will be sure to make a sweep through our Yocto manuals and make sure that when we are referring to the tool and not indicating the command they say "BitBake".

Thanks,
ScottR

-----Original Message-----
From: Richard Purdie [mailto:richard.purdie@...]
Sent: Thursday, July 14, 2011 3:02 AM
To: Robert P. J. Day
Cc: Darren Hart; yocto@...; Rifenbark, Scott M
Subject: Re: [yocto] docs: how to spell "bitbake", and docbook semantic markup for user input

On Thu, 2011-07-14 at 05:46 -0400, Robert P. J. Day wrote:
On Wed, 13 Jul 2011, Darren Hart wrote:

On 07/13/2011 03:48 PM, Joshua Lock wrote:
On Wed, 2011-07-13 at 06:57 -0400, Robert P. J. Day wrote:
just perusing the documentation in my typically pedantic fashion and
a couple questions about style. first, is the proper spelling
"Bitbake" or "BitBake" since the doc source seems to bounce back and
forth and it really should be consistent.
I believe it's the latter, at least that's what I've always use.
Agreed:

The man page:
BitBake - simple tool for the execution of tasks

The user manual:
BitBake User Manual

Those seem like the two lines of documentation that are most likely to
be correct :-) So unless Richard or Chris pipe up, I'd go with BitBake.
i thought as much, i'm going with that. not high on any list of
priorities but while i'm perusing the docs, i might as well make notes
of what can change, and submit patches for the more obvious stuff.

are the small changes i've posted here in acceptable format? do
they get ACKed at some point so i can verify they were accepted?
The pieces in poky's documentation directory are part of the yocto-docs
repo which is maintained by Scott (cc'd). Scott is a tech writer rather
than a developer and loves git, er, I mean we might need to help him get
the patches in ;-). Please do send them and we'll figure that bit out
though and will send an acknowledgement when they're merged.

Cheers,

Richard


Re: IMAGE_FSTYPES that are supported?

Bruce Ashfield <bruce.ashfield@...>
 

On 07/14/11 09:40, Koen Kooi wrote:

Op 14 jul 2011, om 15:13 heeft Bruce Ashfield het volgende geschreven:

On 07/14/11 09:05, Kumar Gala wrote:
Is there a list of which IMAGE_FSTYPES are supported. I didn't see anything in the docs. Looking to see if a u-boot 'mkimage' wrapped set of images is supported or not.
I'm not 100% where the list is, but I can confirm that
uImages are supported and work nicely. Assuming that
you are talking about the common use case, and not something
more exotic :)

I think he means partitioned uimages where you have a kernel + initrd in a single uimage. We don't support that *yet*, but all the needed blocks are there. And we finally get a usecase for having the loadadresses in the machine.conf files :)
Yah, that's what I wondered as well. I've done this locally,
but nothing out of the box .. so I had nagging doubts!

Cheers,

Bruce


Re: Menu configuration

Richard Purdie
 

On Thu, 2011-07-14 at 08:06 -0500, Kumar Gala wrote:
On Jul 12, 2011, at 3:43 AM, Richard Purdie wrote:

On Mon, 2011-07-11 at 10:00 -0700, Turner Randy wrote:
Hello list,

Is there a interactive menu-based configuration for yocto/poky builds
similar to that provided in Buildroot? Or is someone working on this?
At present there is not any interactive menu based configuration but
there is work ongoing on a UI called hob which allows you to select
packages and construct images of those packages so its a graphical front
end to the system.

We're also in the process of starting to better markup configuration
variables in the metadata so that writing some kind of menu based
configuration system would be easier in the future.

We're certainly open to any help in those areas too!

Cheers,

Richard
Are there any docs for hob at this point?
Not specifically. "bitbake -u hob" should let you see where things are
at. Please keep in mind that its under active development at the moment
and can be considered "alpha" quality but feedback is welcome.

Cheers,

Richard


Re: IMAGE_FSTYPES that are supported?

Koen Kooi
 

Op 14 jul 2011, om 15:13 heeft Bruce Ashfield het volgende geschreven:

On 07/14/11 09:05, Kumar Gala wrote:
Is there a list of which IMAGE_FSTYPES are supported. I didn't see anything in the docs. Looking to see if a u-boot 'mkimage' wrapped set of images is supported or not.
I'm not 100% where the list is, but I can confirm that
uImages are supported and work nicely. Assuming that
you are talking about the common use case, and not something
more exotic :)

I think he means partitioned uimages where you have a kernel + initrd in a single uimage. We don't support that *yet*, but all the needed blocks are there. And we finally get a usecase for having the loadadresses in the machine.conf files :)


Re: IMAGE_FSTYPES that are supported?

Bruce Ashfield <bruce.ashfield@...>
 

On 07/14/11 09:05, Kumar Gala wrote:
Is there a list of which IMAGE_FSTYPES are supported. I didn't see anything in the docs. Looking to see if a u-boot 'mkimage' wrapped set of images is supported or not.
I'm not 100% where the list is, but I can confirm that
uImages are supported and work nicely. Assuming that
you are talking about the common use case, and not something
more exotic :)

Cheers,

Bruce


- k
_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto


Re: Menu configuration

Kumar Gala <galak@...>
 

On Jul 12, 2011, at 3:43 AM, Richard Purdie wrote:

On Mon, 2011-07-11 at 10:00 -0700, Turner Randy wrote:
Hello list,

Is there a interactive menu-based configuration for yocto/poky builds
similar to that provided in Buildroot? Or is someone working on this?
At present there is not any interactive menu based configuration but
there is work ongoing on a UI called hob which allows you to select
packages and construct images of those packages so its a graphical front
end to the system.

We're also in the process of starting to better markup configuration
variables in the metadata so that writing some kind of menu based
configuration system would be easier in the future.

We're certainly open to any help in those areas too!

Cheers,

Richard
Are there any docs for hob at this point?

- k


IMAGE_FSTYPES that are supported?

Kumar Gala <galak@...>
 

Is there a list of which IMAGE_FSTYPES are supported. I didn't see anything in the docs. Looking to see if a u-boot 'mkimage' wrapped set of images is supported or not.

- k


Re: docs: how to spell "bitbake", and docbook semantic markup for user input

Richard Purdie
 

On Thu, 2011-07-14 at 05:46 -0400, Robert P. J. Day wrote:
On Wed, 13 Jul 2011, Darren Hart wrote:

On 07/13/2011 03:48 PM, Joshua Lock wrote:
On Wed, 2011-07-13 at 06:57 -0400, Robert P. J. Day wrote:
just perusing the documentation in my typically pedantic fashion and
a couple questions about style. first, is the proper spelling
"Bitbake" or "BitBake" since the doc source seems to bounce back and
forth and it really should be consistent.
I believe it's the latter, at least that's what I've always use.
Agreed:

The man page:
BitBake - simple tool for the execution of tasks

The user manual:
BitBake User Manual

Those seem like the two lines of documentation that are most likely to
be correct :-) So unless Richard or Chris pipe up, I'd go with BitBake.
i thought as much, i'm going with that. not high on any list of
priorities but while i'm perusing the docs, i might as well make notes
of what can change, and submit patches for the more obvious stuff.

are the small changes i've posted here in acceptable format? do
they get ACKed at some point so i can verify they were accepted?
The pieces in poky's documentation directory are part of the yocto-docs
repo which is maintained by Scott (cc'd). Scott is a tech writer rather
than a developer and loves git, er, I mean we might need to help him get
the patches in ;-). Please do send them and we'll figure that bit out
though and will send an acknowledgement when they're merged.

Cheers,

Richard


Re: docs: how to spell "bitbake", and docbook semantic markup for user input

Robert P. J. Day
 

On Wed, 13 Jul 2011, Darren Hart wrote:

On 07/13/2011 03:48 PM, Joshua Lock wrote:
On Wed, 2011-07-13 at 06:57 -0400, Robert P. J. Day wrote:
just perusing the documentation in my typically pedantic fashion and
a couple questions about style. first, is the proper spelling
"Bitbake" or "BitBake" since the doc source seems to bounce back and
forth and it really should be consistent.
I believe it's the latter, at least that's what I've always use.
Agreed:

The man page:
BitBake - simple tool for the execution of tasks

The user manual:
BitBake User Manual

Those seem like the two lines of documentation that are most likely to
be correct :-) So unless Richard or Chris pipe up, I'd go with BitBake.
i thought as much, i'm going with that. not high on any list of
priorities but while i'm perusing the docs, i might as well make notes
of what can change, and submit patches for the more obvious stuff.

are the small changes i've posted here in acceptable format? do
they get ACKed at some point so i can verify they were accepted?

rday

--

========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================