Date   

TARGET_FPU for mpc8315e-rdb listed as SPE??

Kumar Gala <galak@...>
 

Why does the meta/conf/machine/mpc8315e-rdb.conf list TARGET_FPU as SPE. This isn't correct for an MPC8313 SoC.

- k


[PULL] recipe upgrades in base section, Nov. 10

Qing He <qing.he@...>
 

most of them are simple upgrades that changes minor version,
also adds license info in procps

Thanks,
Qing

---
meta/recipes-bsp/pciutils/pciutils-3.1.5/configure.patch | 102 ---
meta/recipes-bsp/pciutils/pciutils-3.1.5/guess-fix.patch | 35 -
meta/recipes-bsp/pciutils/pciutils-3.1.5/lib-build-fix.patch | 92 --
meta/recipes-bsp/pciutils/pciutils-3.1.5/pcimodules-pciutils.diff | 338 ----------
meta/recipes-bsp/pciutils/pciutils-3.1.7/configure.patch | 102 +++
meta/recipes-bsp/pciutils/pciutils-3.1.7/guess-fix.patch | 35 +
meta/recipes-bsp/pciutils/pciutils-3.1.7/lib-build-fix.patch | 92 ++
meta/recipes-bsp/pciutils/pciutils-3.1.7/pcimodules-pciutils.diff | 338 ++++++++++
meta/recipes-bsp/pciutils/pciutils_3.1.5.bb | 57 -
meta/recipes-bsp/pciutils/pciutils_3.1.7.bb | 57 +
meta/recipes-connectivity/iproute2/iproute2-2.6.34/configure-cross.patch | 61 -
meta/recipes-connectivity/iproute2/iproute2-2.6.35/configure-cross.patch | 61 +
meta/recipes-connectivity/iproute2/iproute2_2.6.34.bb | 6
meta/recipes-connectivity/iproute2/iproute2_2.6.35.bb | 6
meta/recipes-connectivity/nfs-utils/nfs-utils_1.2.2.bb | 53 -
meta/recipes-connectivity/nfs-utils/nfs-utils_1.2.3.bb | 53 +
meta/recipes-extended/bzip2/bzip2-1.0.5/Makefile.am | 41 -
meta/recipes-extended/bzip2/bzip2-1.0.5/configure.ac | 14
meta/recipes-extended/bzip2/bzip2-1.0.6/Makefile.am | 41 +
meta/recipes-extended/bzip2/bzip2-1.0.6/configure.ac | 14
meta/recipes-extended/bzip2/bzip2_1.0.5.bb | 26
meta/recipes-extended/bzip2/bzip2_1.0.6.bb | 26
meta/recipes-extended/iptables/iptables_1.4.8.bb | 31
meta/recipes-extended/iptables/iptables_1.4.9.bb | 31
meta/recipes-extended/procps/procps-3.2.7/install.patch | 27
meta/recipes-extended/procps/procps-3.2.7/linux-limits.patch | 13
meta/recipes-extended/procps/procps-3.2.7/pagesz-not-constant.patch | 22
meta/recipes-extended/procps/procps-3.2.7/procmodule.patch | 36 -
meta/recipes-extended/procps/procps-3.2.7/procps.init | 6
meta/recipes-extended/procps/procps-3.2.7/psmodule.patch | 21
meta/recipes-extended/procps/procps-3.2.7/sysctl.conf | 64 -
meta/recipes-extended/procps/procps-3.2.8/install.patch | 27
meta/recipes-extended/procps/procps-3.2.8/linux-limits.patch | 13
meta/recipes-extended/procps/procps-3.2.8/pagesz-not-constant.patch | 22
meta/recipes-extended/procps/procps-3.2.8/procmodule.patch | 36 +
meta/recipes-extended/procps/procps-3.2.8/procps.init | 6
meta/recipes-extended/procps/procps-3.2.8/psmodule.patch | 21
meta/recipes-extended/procps/procps-3.2.8/sysctl.conf | 64 +
meta/recipes-extended/procps/procps.inc | 8
meta/recipes-extended/procps/procps_3.2.7.bb | 40 -
meta/recipes-extended/procps/procps_3.2.8.bb | 40 +
meta/recipes-extended/tzdata/tzdata_2010j.bb | 166 ----
meta/recipes-extended/tzdata/tzdata_2010o.bb | 166 ++++
meta/recipes-support/curl/curl_7.21.0.bb | 54 -
meta/recipes-support/curl/curl_7.21.2.bb | 54 +
meta/recipes-support/shared-mime-info/shared-mime-info.inc | 1
meta/recipes-support/shared-mime-info/shared-mime-info_0.71.bb | 1
meta/recipes-support/shared-mime-info/shared-mime-info_0.80.bb | 2
48 files changed, 1313 insertions(+), 1309 deletions(-)

Qing He (9):
bzip2: upgrade to version 1.0.6
shared-mime-info: upgrade to version 0.80
tzdata: upgrade to version 2010o
curl: upgrade to version 7.21.2
nfs-utils: upgrade to version 1.2.3
pciutils: upgrade to version 3.1.7
iproute2: upgrade to version 2.6.35
iptables: upgrade to version 1.4.9
procps: upgrade to version 3.2.8

Pull URL: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=qhe/distro


Re: Distro 1.0 Planning minutes

Esben Haabendal <eha@...>
 

"Kamble, Nitin A" <nitin.a.kamble@...> writes:

Dongxiao: sysroot per machine per recipe
Is it possible to elaborate on this topic? What was discussed and what
was the conclusion?

/Esben


Re: Distro 1.0 Planning minutes

Richard Purdie <rpurdie@...>
 

On Wed, 2010-11-10 at 10:50 +0100, Esben Haabendal wrote:
"Kamble, Nitin A" <nitin.a.kamble@...> writes:

Dongxiao: sysroot per machine per recipe
Is it possible to elaborate on this topic? What was discussed and what
was the conclusion?
This is what we discussed in person in Cambridge, the idea of making it
possible to have one sysroot per machine or one sysroot per recipe. Our
intention is to make this work in the next few months.

I pointed you at the existing task based sstate code which should make
this kind of thing relatively straight forward.

Cheers,

Richard


Re: Distro 1.0 Planning minutes

Esben Haabendal <eha@...>
 

Richard Purdie <rpurdie@...> writes:

On Wed, 2010-11-10 at 10:50 +0100, Esben Haabendal wrote:
"Kamble, Nitin A" <nitin.a.kamble@...> writes:

Dongxiao: sysroot per machine per recipe
Is it possible to elaborate on this topic? What was discussed and what
was the conclusion?
This is what we discussed in person in Cambridge, the idea of making it
possible to have one sysroot per machine or one sysroot per recipe. Our
intention is to make this work in the next few months.

I pointed you at the existing task based sstate code which should make
this kind of thing relatively straight forward.
This definitely sounds interesting.

Will it be possible to have recipe A (build) depend on B, which (build)
depends on C, without having C in the per recipe stage of A?

Will it be possible to have recipe A (build) depend on selected files
from B, f.x. only a subset of libraries built by a recipe?

/Esben


two layers: hardware and distro.

João Henrique Ferreira de Freitas
 

Hi,

I am novice yocto user.

My target is create a BSP to my hardware+application. Is Yocto a
suitable project to do it?

I want to create two layers:

bsp-myhardware: linux kernel, firmware, specific hardware configuration
bsp-myapplication: linux distro with all software need. Ex: net-snmp,
lksctp (the target is telecom applications)

Currently yocto does not have many recipes that I need. No problem, I
can get from OE. We use kernel 2.6.22 and I presume that I need a
recipe to it and put inside bsp-myhardware, right?


Thanks.

--
-----------------------------------------------------------
João Henrique Freitas - joaohf_at_gmail.com
Campinas-SP-Brasil
BSD051283
LPI 1
http://www.joaohfreitas.eti.br


Re: problem with fetching?

Tian, Kevin <kevin.tian@...>
 

From: Kumar Gala
Sent: Wednesday, November 10, 2010 2:42 PM

I'm trying to build the MPC8135E RDB and have the following setup in conf/local.conf:

# Uncomment and set to allow bitbake to execute multiple tasks at once.
# For a quadcore, BB_NUMBER_THREADS = "4", PARALLEL_MAKE = "-j 4" would
# be appropriate.
BB_NUMBER_THREADS = "16"
# Also, make can be passed flags so it run parallel threads e.g.:
PARALLEL_MAKE = "-j 16"

# The machine to target
MACHINE ?= "mpc8315e-rdb"

....

$ bitbake poky-image-minimal

I see errors likes:

Waiting for 1 active tasks to finish:
1: linux-libc-headers-2.6.34-r1 do_fetch (pid 6952)
NOTE: package binutils-cross-2.20.1-r3: task do_unpack: Succeeded
NOTE: linux-libc-headers-2.6.34:
http://kernel.org/pub/linux/kernel/v2.6/linux-2.6.34.tar.bz2 has no entry in
conf/checksums.ini, not checking URI
NOTE: package linux-libc-headers-2.6.34-r1: task do_fetch: Succeeded
ERROR:
'virtual:native:/local/home/galak/poky-laverne-4.0/meta/recipes-devtools/gnu-config/gn
u-config_20080123.bb' failed

---

if I re-run it gets further. ideas on what's going on?
Could you post a full log about the error? We have a plan to improve the error message
but for now it's normally messed with other build outputs in a parallel build. You can
perhaps grep those lines with "ERROR:".

Normally there're two possible reasons for that:
- poor parallel make support by the package, or
- some missing dependency problem

Above issues are usually worked around by re-run it, but it'd always good to figure out
the exact failure. :-)

Thanks
Kevin


Re: problem with fetching?

Kumar Gala <galak@...>
 

On Nov 10, 2010, at 6:20 AM, Tian, Kevin wrote:

From: Kumar Gala
Sent: Wednesday, November 10, 2010 2:42 PM

I'm trying to build the MPC8135E RDB and have the following setup in conf/local.conf:

# Uncomment and set to allow bitbake to execute multiple tasks at once.
# For a quadcore, BB_NUMBER_THREADS = "4", PARALLEL_MAKE = "-j 4" would
# be appropriate.
BB_NUMBER_THREADS = "16"
# Also, make can be passed flags so it run parallel threads e.g.:
PARALLEL_MAKE = "-j 16"

# The machine to target
MACHINE ?= "mpc8315e-rdb"

....

$ bitbake poky-image-minimal

I see errors likes:

Waiting for 1 active tasks to finish:
1: linux-libc-headers-2.6.34-r1 do_fetch (pid 6952)
NOTE: package binutils-cross-2.20.1-r3: task do_unpack: Succeeded
NOTE: linux-libc-headers-2.6.34:
http://kernel.org/pub/linux/kernel/v2.6/linux-2.6.34.tar.bz2 has no entry in
conf/checksums.ini, not checking URI
NOTE: package linux-libc-headers-2.6.34-r1: task do_fetch: Succeeded
ERROR:
'virtual:native:/local/home/galak/poky-laverne-4.0/meta/recipes-devtools/gnu-config/gn
u-config_20080123.bb' failed

---

if I re-run it gets further. ideas on what's going on?
Could you post a full log about the error? We have a plan to improve the error message
but for now it's normally messed with other build outputs in a parallel build. You can
perhaps grep those lines with "ERROR:".

Normally there're two possible reasons for that:
- poor parallel make support by the package, or
- some missing dependency problem

Above issues are usually worked around by re-run it, but it'd always good to figure out
the exact failure. :-)

Thanks
Kevin
ERROR: Task failed: Fetch failed: Unable to fetch URL cvs://anonymous@.../cvsroot/config;module=config;method=pserver;date=20080123 from any source.
NOTE: package gnu-config-native-0.1+cvs20080123-r1: task do_fetch: Failed
ERROR: Task 211 (virtual:native:/local/home/galak/poky-laverne-4.0/meta/recipes-devtools/gnu-config/gnu-config_20080123.bb, do_fetch) failed with 1
ERROR: 'virtual:native:/local/home/galak/poky-laverne-4.0/meta/recipes-devtools/gnu-config/gnu-config_20080123.bb' failed

Attached is the full log.

- k


Bug Fixer and Verifier

Yu, Ke <ke.yu@...>
 

Hi KangKang,

One case of the bug process need your input. In bug #467, Josh are both reporter and the one who fix this bug. When he fixed the bug, as a reporter, he also verify the bug according to the process (https://wiki.yoctoproject.org/wiki/Bugzilla_Configuration_and_Bug_Tracking) . I just wonder if it is appropriate that bug fixer and verifier be the same people?

Regards
Ke


Re: [PULL] Distro Updates and Locale Generation Change to Posix

Richard Purdie <rpurdie@...>
 

On Mon, 2010-11-08 at 16:38 -0800, Saul Wold wrote:
Dexuan Cui (2):
busybox: enable more options for tar to support more file formats.
eglibc: install the missing /etc/ld.so.conf into target

Jiajun Xu (1):
imagetest-qemu: Add test case for dmesg check in target

Qing He (1):
bzip2: upgrade to version 1.0.6

Saul Wold (5):
task-sdk-gmae: fix typo in SDK-EXTRAS and convert to ?= for
assignment
poky.conf: Change default locale to POSIX
ld.so.conf: create empty file
eglibc: add en-us locale generation
poky.conf: Default Locale Generation
I've merged these.

Xiaofeng Yan (1):
LSB: Add a new package
A minor nitpick but which GPL is this under? I'd like to get this fixed
before it gets merged.

Cheers,

Richard


Re: [PULL] Distro Updates: Kernel, scripts and gplv2 cleanup

Richard Purdie <rpurdie@...>
 

On Tue, 2010-11-09 at 12:32 -0800, Saul Wold wrote:
Saul Wold (1):
base.bbclass/poky.conf: Fix INCOMPATIBLE_LICENSE Whitelist checking
Please take a look at that commit, I've not taken it ;-).

I did take all the others.

Cheers,

Richard


Re: TARGET_FPU for mpc8315e-rdb listed as SPE??

Richard Purdie <rpurdie@...>
 

On Wed, 2010-11-10 at 00:46 -0600, Kumar Gala wrote:
Why does the meta/conf/machine/mpc8315e-rdb.conf list TARGET_FPU as
SPE. This isn't correct for an MPC8313 SoC.
I'm not familiar with that machine, please could you file a bug, maybe
with a patch showing what the correct values should be?

Cheers,

Richard


Re: problem with fetching?

Richard Purdie <rpurdie@...>
 

On Wed, 2010-11-10 at 06:32 -0600, Kumar Gala wrote:
ERROR: Task failed: Fetch failed: Unable to fetch URL cvs://anonymous@.../cvsroot/config;module=config;method=pserver;date=20080123 from any source.
NOTE: package gnu-config-native-0.1+cvs20080123-r1: task do_fetch: Failed
ERROR: Task 211 (virtual:native:/local/home/galak/poky-laverne-4.0/meta/recipes-devtools/gnu-config/gnu-config_20080123.bb, do_fetch) failed with 1
ERROR: 'virtual:native:/local/home/galak/poky-laverne-4.0/meta/recipes-devtools/gnu-config/gnu-config_20080123.bb' failed

Attached is the full log.
Are you behind some kind of proxy/firewall? Its interesting its a cvs
based recipe that is failing so it could be your cvs setup.

You could try placing
http://autobuilder.pokylinux.org/sources/config_cvs.sv.gnu.org__20080123.tar.gz

into the downloads directory manually and touching the
config_cvs.sv.gnu.org__20080123.tar.gz.md5 file there to show the
fetcher the fetch is complete. If that works it would suggest the mirror
fallback code in the fetcher isn't working as intended.

Cheers,

Richard


Re: problem with fetching?

Kumar Gala <galak@...>
 

On Nov 10, 2010, at 7:29 AM, Richard Purdie wrote:

On Wed, 2010-11-10 at 06:32 -0600, Kumar Gala wrote:
ERROR: Task failed: Fetch failed: Unable to fetch URL cvs://anonymous@.../cvsroot/config;module=config;method=pserver;date=20080123 from any source.
NOTE: package gnu-config-native-0.1+cvs20080123-r1: task do_fetch: Failed
ERROR: Task 211 (virtual:native:/local/home/galak/poky-laverne-4.0/meta/recipes-devtools/gnu-config/gnu-config_20080123.bb, do_fetch) failed with 1
ERROR: 'virtual:native:/local/home/galak/poky-laverne-4.0/meta/recipes-devtools/gnu-config/gnu-config_20080123.bb' failed

Attached is the full log.
Are you behind some kind of proxy/firewall? Its interesting its a cvs
based recipe that is failing so it could be your cvs setup.
Yes, behind a proxy/firewall. cvs is not normally allowed out.

You could try placing
http://autobuilder.pokylinux.org/sources/config_cvs.sv.gnu.org__20080123.tar.gz

into the downloads directory manually and touching the
config_cvs.sv.gnu.org__20080123.tar.gz.md5 file there to show the
fetcher the fetch is complete. If that works it would suggest the mirror
fallback code in the fetcher isn't working as intended.
I'm new to this, where would my download dir be?

- k


Re: two layers: hardware and distro.

Richard Purdie <rpurdie@...>
 

Hi,

On Wed, 2010-11-10 at 09:41 -0200, João Henrique Freitas wrote:
I am novice yocto user.

My target is create a BSP to my hardware+application. Is Yocto a
suitable project to do it?

I want to create two layers:

bsp-myhardware: linux kernel, firmware, specific hardware configuration
bsp-myapplication: linux distro with all software need. Ex: net-snmp,
lksctp (the target is telecom applications)

Currently yocto does not have many recipes that I need. No problem, I
can get from OE. We use kernel 2.6.22 and I presume that I need a
recipe to it and put inside bsp-myhardware, right?
Yes, this sounds like a very reasonable approach.

In general (this applies to anyone out there), we're interested to know
what kinds of software people use so please let us know what you're
putting into application layers anyone creates like this. Our focus is
currently on making sure there is a rock solid core for people to build
from but if there are core applications missing we'd like to know about
it.

Also, if anyone establishes a layer with a specific focus, we're happy
to provide a git repository for it on git.yoctoproject.org where you
could maintain and share this code with other people with a similar
goal.

Cheers,

Richard


Re: TARGET_FPU for mpc8315e-rdb listed as SPE??

Bruce Ashfield <bruce.ashfield@...>
 

On 10-11-10 01:46 AM, Kumar Gala wrote:
Why does the meta/conf/machine/mpc8315e-rdb.conf list TARGET_FPU as SPE. This isn't correct for an MPC8313 SoC.
It isn't used at the moment, so we can safely
ignore this.

It was a hold over from when I initially created
the BSP, and I've since changed it locally, but
haven't sent the updated BSP yet.

Cheers,

Bruce


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


Re: two layers: hardware and distro.

Bruce Ashfield <bruce.ashfield@...>
 

On 10-11-10 06:41 AM, João Henrique Freitas wrote:
Hi,

I am novice yocto user.

My target is create a BSP to my hardware+application. Is Yocto a
suitable project to do it?

I want to create two layers:

bsp-myhardware: linux kernel, firmware, specific hardware configuration
bsp-myapplication: linux distro with all software need. Ex: net-snmp,
lksctp (the target is telecom applications)

Currently yocto does not have many recipes that I need. No problem, I
can get from OE. We use kernel 2.6.22 and I presume that I need a
recipe to it and put inside bsp-myhardware, right?
Any interest in moving to a newer/different kernel ? The
supported kernel for yocto is at 2.6.34 and I'll have a
-dev tree tracking 2.6.37 shortly.

My interest is getting more BSPs using the same kernel
version so we can leverage the common set of issues,
bug fixes, CVEs, etc. It also helps me streamline the
BSP bootstrapping process, which is a primary focus of
mine at the moment.

Bruce



Thanks.


Re: problem with fetching?

Richard Purdie <rpurdie@...>
 

On Wed, 2010-11-10 at 07:31 -0600, Kumar Gala wrote:
On Nov 10, 2010, at 7:29 AM, Richard Purdie wrote:

On Wed, 2010-11-10 at 06:32 -0600, Kumar Gala wrote:
ERROR: Task failed: Fetch failed: Unable to fetch URL cvs://anonymous@.../cvsroot/config;module=config;method=pserver;date=20080123 from any source.
NOTE: package gnu-config-native-0.1+cvs20080123-r1: task do_fetch: Failed
ERROR: Task 211 (virtual:native:/local/home/galak/poky-laverne-4.0/meta/recipes-devtools/gnu-config/gnu-config_20080123.bb, do_fetch) failed with 1
ERROR: 'virtual:native:/local/home/galak/poky-laverne-4.0/meta/recipes-devtools/gnu-config/gnu-config_20080123.bb' failed

Attached is the full log.
Are you behind some kind of proxy/firewall? Its interesting its a cvs
based recipe that is failing so it could be your cvs setup.
Yes, behind a proxy/firewall. cvs is not normally allowed out.

You could try placing
http://autobuilder.pokylinux.org/sources/config_cvs.sv.gnu.org__20080123.tar.gz

into the downloads directory manually and touching the
config_cvs.sv.gnu.org__20080123.tar.gz.md5 file there to show the
fetcher the fetch is complete. If that works it would suggest the mirror
fallback code in the fetcher isn't working as intended.
I'm new to this, where would my download dir be?
It defaults to "build/downloads" so in the build directory unless you
changed it in local.conf.

Cheers,

Richard


Re: Distro 1.0 Planning minutes

Richard Purdie <rpurdie@...>
 

On Wed, 2010-11-10 at 11:52 +0100, Esben Haabendal wrote:
Richard Purdie <rpurdie@...> writes:

On Wed, 2010-11-10 at 10:50 +0100, Esben Haabendal wrote:
"Kamble, Nitin A" <nitin.a.kamble@...> writes:

Dongxiao: sysroot per machine per recipe
Is it possible to elaborate on this topic? What was discussed and what
was the conclusion?
This is what we discussed in person in Cambridge, the idea of making it
possible to have one sysroot per machine or one sysroot per recipe. Our
intention is to make this work in the next few months.

I pointed you at the existing task based sstate code which should make
this kind of thing relatively straight forward.
This definitely sounds interesting.

Will it be possible to have recipe A (build) depend on B, which (build)
depends on C, without having C in the per recipe stage of A?
Yes, that is the plan. I'm hoping this allows us to rigorously check
package dependencies and whilst we might not default to it all the time,
it would allow us to test this periodically.

Will it be possible to have recipe A (build) depend on selected files
from B, f.x. only a subset of libraries built by a recipe?
This currently isn't planned.

Cheers,

Richard


Re: TARGET_FPU for mpc8315e-rdb listed as SPE??

Bruce Ashfield <bruce.ashfield@...>
 

On 10-11-10 08:38 AM, Bruce Ashfield wrote:
On 10-11-10 01:46 AM, Kumar Gala wrote:
Why does the meta/conf/machine/mpc8315e-rdb.conf list TARGET_FPU as
SPE. This isn't correct for an MPC8313 SoC.
It isn't used at the moment, so we can safely
ignore this.

It was a hold over from when I initially created
the BSP, and I've since changed it locally, but
haven't sent the updated BSP yet.
To clarify on this point, the kernel configuration
is NOT using SPE for this, and I was attempting to
use the FPU setting to trigger some different gcc
flags during development the base of that test was
an e500 board, so the SPE setting leaked in, but is
unused.

At the moment, it is actually using soft-float, and
I had planned to submit a change to clarify that.

If there's another option, let me know and I'll
rebase my patches and change it again.

Cheers,

Bruce


Cheers,

Bruce


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

221 - 240 of 57770