Date   

[PATCH] mpc8315e-rdb: Set TARGET_FPU correct

Kumar Gala <galak@...>
 

The MPC8315E has a e300c3 core in it with 'classic' or normal PPC
floating point.

'SPE' floating point is what exists on the e500v2 core.

Signed-off-by: Kumar Gala <galak@...>
---
meta-yocto/conf/machine/mpc8315e-rdb.conf | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/meta-yocto/conf/machine/mpc8315e-rdb.conf b/meta-yocto/conf/machine/mpc8315e-rdb.conf
index 095d113..3f946a0 100644
--- a/meta-yocto/conf/machine/mpc8315e-rdb.conf
+++ b/meta-yocto/conf/machine/mpc8315e-rdb.conf
@@ -2,7 +2,7 @@
#@DESCRIPTION: Machine configuration for running

TARGET_ARCH = "powerpc"
-TARGET_FPU = "spe"
+TARGET_FPU = "hard"

require conf/machine/include/tune-ppc603e.inc

--
1.7.3.4


Re: toolchain queries

Bruce Ashfield <bruce.ashfield@...>
 

On 11-07-14 10:36 PM, Kumar Gala wrote:
Where is the best place to ask questions and try and get support for adding some toolchain variations in?
Here can work, or the oe-core lists.


I'm wanting to add support in for a few different flavors of PPC that are not currently supported:

* e500v2 (gcc needs --enable-e500_double, eglibc
* e5500 (64-bit embedded ppc)
There are oe and oe-dev references for at least the e500v2
(that's what I've been working on importing .. slowly), and
I haven't looked for others yet. So that's a good place to
look for real world examples.

Once I get a few kernel-3.0 issues sorted out, I'll be back
to this and could definitely collaborate on these items.

Cheers,

Bruce

* e5500 - multilib support for 32/64-bit

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


[PATCH 1/1] Remove unused target tree data for Hob

Ke Liping <liping.ke@...>
 

From: Liping Ke <liping.ke@...>

Since Hob only needes package dependency information, we can
create a new version of package information retrieving methods,
remove task dependency information, so that we can greatly
reduce data loading time for Hob

Signed-off-by: Liping Ke <liping.ke@...>
---
bitbake/lib/bb/cooker.py | 96 +++++++++++++++++++++++++++++++++++++---------
1 files changed, 77 insertions(+), 19 deletions(-)

diff --git a/bitbake/lib/bb/cooker.py b/bitbake/lib/bb/cooker.py
index 8badd2d..26ed2ae 100644
--- a/bitbake/lib/bb/cooker.py
+++ b/bitbake/lib/bb/cooker.py
@@ -296,13 +296,12 @@ class BBCooker:
if data.getVarFlag( e, 'python', envdata ):
logger.plain("\npython %s () {\n%s}\n", e, data.getVar(e, envdata, 1))

- def prepareTreeData(self, pkgs_to_build, task):
+ def prepareTreeData(self, pkgs_to_build, task, runqueue=True):
"""
Prepare a runqueue and taskdata object for iteration over pkgs_to_build
"""
# Need files parsed
self.updateCache()
-
# If we are told to do the None task then query the default task
if (task == None):
task = self.configuration.cmd
@@ -322,12 +321,22 @@ class BBCooker:
runlist.append([k, "do_%s" % task])
taskdata.add_unresolved(localdata, self.status)

- rq = bb.runqueue.RunQueue(self, self.configuration.data, self.status, taskdata, runlist)
- rq.rqdata.prepare()
-
- return taskdata, rq
-
- def generateDepTreeData(self, pkgs_to_build, task, more_meta=False):
+ # For some users, take Hob as example, we only need less dependency data
+ # mark this kind of user as "less_meta" data requester
+ if (runqueue):
+ rq = bb.runqueue.RunQueue(self, self.configuration.data, self.status, taskdata, runlist)
+ rq.rqdata.prepare()
+ return taskdata, rq
+ else:
+ tasks_fnid = []
+ if len(taskdata.tasks_name) == 0:
+ # Nothing to do
+ return
+ for task in xrange(len(taskdata.tasks_name)):
+ tasks_fnid.append(taskdata.tasks_fnid[task])
+ return taskdata, tasks_fnid
+
+ def generateTaskDepTreeData(self, pkgs_to_build, task):
"""
Create a dependency tree of pkgs_to_build, returning the data.
When more_meta is set to True include summary, license and group
@@ -351,18 +360,10 @@ class BBCooker:
fn = taskdata.fn_index[fnid]
pn = self.status.pkg_fn[fn]
version = "%s:%s-%s" % self.status.pkg_pepvpr[fn]
- if more_meta:
- summary = self.status.summary[fn]
- lic = self.status.license[fn]
- section = self.status.section[fn]
if pn not in depend_tree["pn"]:
depend_tree["pn"][pn] = {}
depend_tree["pn"][pn]["filename"] = fn
depend_tree["pn"][pn]["version"] = version
- if more_meta:
- depend_tree["pn"][pn]["summary"] = summary
- depend_tree["pn"][pn]["license"] = lic
- depend_tree["pn"][pn]["section"] = section
for dep in rq.rqdata.runq_depends[task]:
depfn = taskdata.fn_index[rq.rqdata.runq_fnid[dep]]
deppn = self.status.pkg_fn[depfn]
@@ -407,12 +408,69 @@ class BBCooker:
return depend_tree


+ def generatePkgDepTreeData(self, pkgs_to_build, task):
+ """
+ Create a dependency tree of pkgs_to_build, returning the data.
+ When more_meta is set to True include summary, license and group
+ information in the returned tree.
+ """
+ taskdata, tasks_fnid = self.prepareTreeData(pkgs_to_build, task, False)
+
+ seen_fnids = []
+ depend_tree = {}
+ depend_tree["depends"] = {}
+ depend_tree["pn"] = {}
+ depend_tree["rdepends-pn"] = {}
+ depend_tree["packages"] = {}
+ depend_tree["rdepends-pkg"] = {}
+
+ for task in xrange(len(tasks_fnid)):
+ fnid = tasks_fnid[task]
+ fn = taskdata.fn_index[fnid]
+ pn = self.status.pkg_fn[fn]
+ version = "%s:%s-%s" % self.status.pkg_pepvpr[fn]
+ summary = self.status.summary[fn]
+ lic = self.status.license[fn]
+ section = self.status.section[fn]
+ if pn not in depend_tree["pn"]:
+ depend_tree["pn"][pn] = {}
+ depend_tree["pn"][pn]["filename"] = fn
+ depend_tree["pn"][pn]["version"] = version
+ depend_tree["pn"][pn]["summary"] = summary
+ depend_tree["pn"][pn]["license"] = lic
+ depend_tree["pn"][pn]["section"] = section
+
+ if fnid not in seen_fnids:
+ seen_fnids.append(fnid)
+ packages = []
+
+ depend_tree["depends"][pn] = []
+ for dep in taskdata.depids[fnid]:
+ depend_tree["depends"][pn].append(taskdata.build_names_index[dep])
+
+ depend_tree["rdepends-pn"][pn] = []
+ for rdep in taskdata.rdepids[fnid]:
+ depend_tree["rdepends-pn"][pn].append(taskdata.run_names_index[rdep])
+
+ rdepends = self.status.rundeps[fn]
+ for package in rdepends:
+ packages.append(package)
+
+ for package in packages:
+ if package not in depend_tree["packages"]:
+ depend_tree["packages"][package] = {}
+ depend_tree["packages"][package]["pn"] = pn
+ depend_tree["packages"][package]["filename"] = fn
+ depend_tree["packages"][package]["version"] = version
+
+ return depend_tree
+
def generateDepTreeEvent(self, pkgs_to_build, task):
"""
Create a task dependency graph of pkgs_to_build.
Generate an event with the result
"""
- depgraph = self.generateDepTreeData(pkgs_to_build, task)
+ depgraph = self.generateTaskDepTreeData(pkgs_to_build, task)
bb.event.fire(bb.event.DepTreeGenerated(depgraph), self.configuration.data)

def generateDotGraphFiles(self, pkgs_to_build, task):
@@ -421,7 +479,7 @@ class BBCooker:
Save the result to a set of .dot files.
"""

- depgraph = self.generateDepTreeData(pkgs_to_build, task)
+ depgraph = self.generateTaskDepTreeData(pkgs_to_build, task)

# Prints a flattened form of package-depends below where subpackages of a package are merged into the main pn
depends_file = file('pn-depends.dot', 'w' )
@@ -628,7 +686,7 @@ class BBCooker:
pkgs = pkgs + extra_pkgs

# generate a dependency tree for all our packages
- tree = self.generateDepTreeData(pkgs, 'build', more_meta=True)
+ tree = self.generatePkgDepTreeData(pkgs, 'build')
bb.event.fire(bb.event.TargetsTreeGenerated(tree), self.configuration.data)

def buildWorldTargetList(self):
--
1.7.0.4


[PATCH 0/1][Image Creator] Remove unused target tree data for Hob

Ke Liping <liping.ke@...>
 

From: Liping Ke <liping.ke@...>

Since Hob only needes package dependency information, we can
create a new version of package information retrieving methods,
remove task dependency information, so that we can greatly
reduce data loading time for Hob

The following changes since commit fa4bcfdb73167f8159b88e5a4d711c0d37627a70:
Darren Hart (1):
bb-matrix: correct BB and PM number canonicalization

are available in the git repository at:

git://git.pokylinux.org/poky-contrib lke/hob_perf
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=lke/hob_perf

Liping Ke (1):
Remove unused target tree data for Hob

bitbake/lib/bb/cooker.py | 96 +++++++++++++++++++++++++++++++++++++---------
1 files changed, 77 insertions(+), 19 deletions(-)


Re: toolchain queries

niqingliang
 

may be meta/conf/machine/include.

On Fri, 2011-07-15 at 10:36 +0800, Kumar Gala wrote:
Where is the best place to ask questions and try and get support for adding some toolchain variations in?

I'm wanting to add support in for a few different flavors of PPC that are not currently supported:

* e500v2 (gcc needs --enable-e500_double, eglibc
* e5500 (64-bit embedded ppc)
* e5500 - multilib support for 32/64-bit

- k
_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto
--
倪庆亮
TEL: 13588371863
E-MAIL: niqingliang@...
BLOG: http://niqingliang2003.wordpress.com


toolchain queries

Kumar Gala <galak@...>
 

Where is the best place to ask questions and try and get support for adding some toolchain variations in?

I'm wanting to add support in for a few different flavors of PPC that are not currently supported:

* e500v2 (gcc needs --enable-e500_double, eglibc
* e5500 (64-bit embedded ppc)
* e5500 - multilib support for 32/64-bit

- k


[PATCH 6/6] meta-emenlow: use common .inc files

tom.zanussi@...
 

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

Have emenlow.conf use the common-bsp-* .inc files and remove the
open-coded machine settings.

Signed-off-by: Tom Zanussi <tom.zanussi@...>
---
meta-emenlow/conf/machine/emenlow.conf | 17 ++---------------
1 files changed, 2 insertions(+), 15 deletions(-)

diff --git a/meta-emenlow/conf/machine/emenlow.conf b/meta-emenlow/conf/machine/emenlow.conf
index b0b7d5e..209f029 100644
--- a/meta-emenlow/conf/machine/emenlow.conf
+++ b/meta-emenlow/conf/machine/emenlow.conf
@@ -8,15 +8,11 @@ TARGET_ARCH = "i586"

include conf/machine/include/tune-atom.inc

-BASE_PACKAGE_ARCH="core2"
-
-MACHINE_FEATURES = "kernel26 screen keyboard pci usbhost ext2 ext3 x86 \
- acpi serial usbgadget"
-
-KERNEL_IMAGETYPE = "bzImage"
+include ../common/common-bsp-mach.inc

PREFERRED_PROVIDER_virtual/kernel = "linux-yocto"
PREFERRED_PROVIDER_linux-libc-headers ?= "linux-libc-headers-yocto"
+
PREFERRED_PROVIDER_libdrm = "libdrm-poulsbo"
PREFERRED_PROVIDER_drm = "libdrm-poulsbo"
PREFERRED_PROVIDER_virtual/libx11 = "libx11-trim"
@@ -29,12 +25,3 @@ XSERVER ?= "xserver-psb \
xf86-input-mouse \
xf86-input-keyboard \
xf86-input-evdev"
-
-SERIAL_CONSOLE = "115200 ttyS0"
-
-MACHINE_EXTRA_RRECOMMENDS = "kernel-modules eee-acpi-scripts"
-
-IMAGE_FSTYPES ?= "ext3 cpio.gz"
-
-GLIBC_ADDONS = "nptl"
-GLIBC_EXTRA_OECONF = "--with-tls"
--
1.7.0.4


[PATCH 5/6] meta-jasperforest: use common .inc files

tom.zanussi@...
 

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

Have jasperforest.conf use the common-bsp-* .inc files and remove the
open-coded machine settings.

Signed-off-by: Tom Zanussi <tom.zanussi@...>
---
meta-jasperforest/conf/machine/jasperforest.conf | 22 +++-------------------
1 files changed, 3 insertions(+), 19 deletions(-)

diff --git a/meta-jasperforest/conf/machine/jasperforest.conf b/meta-jasperforest/conf/machine/jasperforest.conf
index 3f8591a..b603d16 100644
--- a/meta-jasperforest/conf/machine/jasperforest.conf
+++ b/meta-jasperforest/conf/machine/jasperforest.conf
@@ -9,18 +9,14 @@ PACKAGE_EXTRA_ARCHS = "x86 xeon"

BASE_PACKAGE_ARCH="xeon"

-MACHINE_FEATURES = "kernel26 screen keyboard pci usbhost ext2 ext3 x86 \
- acpi serial usbgadget"
+TARGET_CC_ARCH = "-m64"

-KERNEL_IMAGETYPE = "bzImage"
+include ../common/common-bsp-mach.inc
+include ../common/common-bsp-x.inc

PREFERRED_PROVIDER_virtual/kernel = "linux-yocto"
PREFERRED_PROVIDER_linux-libc-headers ?= "linux-libc-headers-yocto"

-PREFERRED_PROVIDER_virtual/libx11 ?= "libx11-trim"
-PREFERRED_PROVIDER_virtual/libgl ?= "mesa-dri"
-PREFERRED_PROVIDER_virtual/xserver ?= "xserver-xf86-dri-lite"
-PREFERRED_PROVIDER_virtual/xserver-xf86 ?= "xserver-xf86-dri-lite"
XSERVER ?= "xserver-xf86-dri-lite \
xf86-input-mouse \
xf86-input-keyboard \
@@ -28,17 +24,5 @@ XSERVER ?= "xserver-xf86-dri-lite \
xf86-input-synaptics \
xf86-video-vesa"

-SERIAL_CONSOLE = "115200 ttyS0"
-
-MACHINE_EXTRA_RRECOMMENDS = "kernel-modules eee-acpi-scripts"
-
-IMAGE_FSTYPES ?= "ext3 cpio.gz"
-
-GLIBC_ADDONS = "nptl"
-GLIBC_EXTRA_OECONF = "--with-tls"
-
MACHINE_ESSENTIAL_EXTRA_RDEPENDS = "grub"
PREFERRED_VERSION_grub ?= "1.98"
-
-TARGET_CC_ARCH = "-m64"
-
--
1.7.0.4


[PATCH 4/6] meta-fishriver: use common .inc files

tom.zanussi@...
 

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

Have fishriver.conf use the common-bsp-* .inc files and remove the
open-coded machine settings.

Signed-off-by: Tom Zanussi <tom.zanussi@...>
---
meta-fishriver/conf/machine/fishriver.conf | 20 +++-----------------
1 files changed, 3 insertions(+), 17 deletions(-)

diff --git a/meta-fishriver/conf/machine/fishriver.conf b/meta-fishriver/conf/machine/fishriver.conf
index e692cac..e2f49d0 100644
--- a/meta-fishriver/conf/machine/fishriver.conf
+++ b/meta-fishriver/conf/machine/fishriver.conf
@@ -8,29 +8,15 @@ TARGET_ARCH = "i586"

include conf/machine/include/tune-atom.inc

-MACHINE_FEATURES = "kernel26 screen keyboard pci usbhost ext2 ext3 x86 \
- acpi serial usbgadget"
-
-KERNEL_IMAGETYPE = "bzImage"
+include ../common/common-bsp-mach.inc
+include ../common/common-bsp-x.inc

PREFERRED_PROVIDER_virtual/kernel = "linux-yocto"
PREFERRED_PROVIDER_linux-libc-headers ?= "linux-libc-headers-yocto"
-PREFERRED_PROVIDER_virtual/libx11 ?= "libx11-trim"
-PREFERRED_PROVIDER_virtual/libgl ?= "mesa-dri"
-PREFERRED_PROVIDER_virtual/xserver ?= "xserver-xf86-dri-lite"
-PREFERRED_PROVIDER_virtual/xserver-xf86 ?= "xserver-xf86-dri-lite"
+
XSERVER ?= "xserver-xf86-dri-lite \
xf86-input-mouse \
xf86-input-keyboard \
xf86-input-evdev \
xf86-input-synaptics \
xf86-video-vesa"
-
-SERIAL_CONSOLE = "115200 ttyS0"
-
-MACHINE_EXTRA_RRECOMMENDS = "kernel-modules eee-acpi-scripts"
-
-IMAGE_FSTYPES ?= "ext3 cpio.gz"
-
-GLIBC_ADDONS = "nptl"
-GLIBC_EXTRA_OECONF = "--with-tls"
--
1.7.0.4


[PATCH 3/6] meta-crownbay: use common .inc files

tom.zanussi@...
 

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

Have crownbay.conf and crownbay-noemgd.conf use the common-bsp-* .inc
files and remove the open-coded machine settings.

Signed-off-by: Tom Zanussi <tom.zanussi@...>
---
meta-crownbay/conf/machine/crownbay-noemgd.conf | 19 ++-----------------
meta-crownbay/conf/machine/crownbay.conf | 19 ++-----------------
2 files changed, 4 insertions(+), 34 deletions(-)

diff --git a/meta-crownbay/conf/machine/crownbay-noemgd.conf b/meta-crownbay/conf/machine/crownbay-noemgd.conf
index cc0b2eb..5abdd3d 100644
--- a/meta-crownbay/conf/machine/crownbay-noemgd.conf
+++ b/meta-crownbay/conf/machine/crownbay-noemgd.conf
@@ -8,29 +8,14 @@ TARGET_ARCH = "i586"

include conf/machine/include/tune-atom.inc

-MACHINE_FEATURES = "kernel26 screen keyboard pci usbhost ext2 ext3 x86 \
- acpi serial usbgadget"
-
-KERNEL_IMAGETYPE = "bzImage"
+include ../common/common-bsp-mach.inc
+include ../common/common-bsp-x.inc

PREFERRED_PROVIDER_virtual/kernel = "linux-yocto"
PREFERRED_PROVIDER_linux-libc-headers ?= "linux-libc-headers-yocto"
-PREFERRED_PROVIDER_virtual/libx11 ?= "libx11-trim"
-PREFERRED_PROVIDER_virtual/libgl ?= "mesa-dri"
-PREFERRED_PROVIDER_virtual/xserver ?= "xserver-xf86-dri-lite"
-PREFERRED_PROVIDER_virtual/xserver-xf86 ?= "xserver-xf86-dri-lite"
XSERVER ?= "xserver-xf86-dri-lite \
xf86-input-mouse \
xf86-input-keyboard \
xf86-input-evdev \
xf86-input-synaptics \
xf86-video-vesa"
-
-SERIAL_CONSOLE = "115200 ttyS0"
-
-MACHINE_EXTRA_RRECOMMENDS = "kernel-modules eee-acpi-scripts"
-
-IMAGE_FSTYPES ?= "ext3 cpio.gz"
-
-GLIBC_ADDONS = "nptl"
-GLIBC_EXTRA_OECONF = "--with-tls"
diff --git a/meta-crownbay/conf/machine/crownbay.conf b/meta-crownbay/conf/machine/crownbay.conf
index c66b859..8469011 100644
--- a/meta-crownbay/conf/machine/crownbay.conf
+++ b/meta-crownbay/conf/machine/crownbay.conf
@@ -8,17 +8,11 @@ TARGET_ARCH = "i586"

include conf/machine/include/tune-atom.inc

-MACHINE_FEATURES = "kernel26 screen keyboard pci usbhost ext2 ext3 x86 \
- acpi serial usbgadget"
-
-KERNEL_IMAGETYPE = "bzImage"
+include ../common/common-bsp-mach.inc
+include ../common/common-bsp-x.inc

PREFERRED_PROVIDER_virtual/kernel = "linux-yocto"
PREFERRED_PROVIDER_linux-libc-headers ?= "linux-libc-headers-yocto"
-PREFERRED_PROVIDER_virtual/libx11 ?= "libx11-trim"
-PREFERRED_PROVIDER_virtual/libgl ?= "mesa-dri"
-PREFERRED_PROVIDER_virtual/xserver ?= "xserver-xf86-dri-lite"
-PREFERRED_PROVIDER_virtual/xserver-xf86 ?= "xserver-xf86-dri-lite"
XSERVER ?= "xserver-xf86-dri-lite \
emgd-driver-bin \
xf86-input-mouse \
@@ -29,12 +23,3 @@ XSERVER ?= "xserver-xf86-dri-lite \

PREFERRED_VERSION_xserver-xf86-dri-lite ?= "1.9.3"
PREFERRED_VERSION_emgd-driver-bin ?= "1.6"
-
-SERIAL_CONSOLE = "115200 ttyS0"
-
-MACHINE_EXTRA_RRECOMMENDS = "kernel-modules eee-acpi-scripts"
-
-IMAGE_FSTYPES ?= "ext3 cpio.gz"
-
-GLIBC_ADDONS = "nptl"
-GLIBC_EXTRA_OECONF = "--with-tls"
--
1.7.0.4


[PATCH 2/6] meta-sugarbay: use common .inc files

tom.zanussi@...
 

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

Have sugarbay.conf use the common-bsp-* .inc files and remove the
open-coded machine settings.

Signed-off-by: Tom Zanussi <tom.zanussi@...>
---
meta-sugarbay/conf/machine/sugarbay.conf | 22 +++-------------------
1 files changed, 3 insertions(+), 19 deletions(-)

diff --git a/meta-sugarbay/conf/machine/sugarbay.conf b/meta-sugarbay/conf/machine/sugarbay.conf
index ebc6dbc..ed82506 100644
--- a/meta-sugarbay/conf/machine/sugarbay.conf
+++ b/meta-sugarbay/conf/machine/sugarbay.conf
@@ -9,18 +9,14 @@ PACKAGE_EXTRA_ARCHS = "x86 snb"

BASE_PACKAGE_ARCH="snb"

-MACHINE_FEATURES = "kernel26 screen keyboard pci usbhost ext2 ext3 x86 \
- acpi serial usbgadget"
+TARGET_CC_ARCH = "-m64"

-KERNEL_IMAGETYPE = "bzImage"
+include ../common/common-bsp-mach.inc
+include ../common/common-bsp-x.inc

PREFERRED_PROVIDER_virtual/kernel = "linux-yocto"
PREFERRED_PROVIDER_linux-libc-headers ?= "linux-libc-headers-yocto"

-PREFERRED_PROVIDER_virtual/libx11 ?= "libx11-trim"
-PREFERRED_PROVIDER_virtual/libgl ?= "mesa-dri"
-PREFERRED_PROVIDER_virtual/xserver ?= "xserver-xf86-dri-lite"
-PREFERRED_PROVIDER_virtual/xserver-xf86 ?= "xserver-xf86-dri-lite"
XSERVER ?= "xserver-xf86-dri-lite \
xf86-input-mouse \
xf86-input-keyboard \
@@ -30,17 +26,5 @@ XSERVER ?= "xserver-xf86-dri-lite \
mesa-dri \
mesa-dri-driver-i965"

-SERIAL_CONSOLE = "115200 ttyS0"
-
-MACHINE_EXTRA_RRECOMMENDS = "kernel-modules eee-acpi-scripts"
-
-IMAGE_FSTYPES ?= "ext3 cpio.gz"
-
-GLIBC_ADDONS = "nptl"
-GLIBC_EXTRA_OECONF = "--with-tls"
-
MACHINE_ESSENTIAL_EXTRA_RDEPENDS = "grub"
-
-TARGET_CC_ARCH = "-m64"
-
PREFERRED_VERSION_grub ?= "1.98"
--
1.7.0.4


[PATCH 1/6] meta-intel: add a couple common .inc files

tom.zanussi@...
 

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

The meta-intel BSPs currently have a number of machine settings common
to all - factor these out into a couple common include files.

Signed-off-by: Tom Zanussi <tom.zanussi@...>
---
common/common-bsp-mach.inc | 13 +++++++++++++
common/common-bsp-x.inc | 4 ++++
2 files changed, 17 insertions(+), 0 deletions(-)
create mode 100644 common/common-bsp-mach.inc
create mode 100644 common/common-bsp-x.inc

diff --git a/common/common-bsp-mach.inc b/common/common-bsp-mach.inc
new file mode 100644
index 0000000..b020a84
--- /dev/null
+++ b/common/common-bsp-mach.inc
@@ -0,0 +1,13 @@
+MACHINE_FEATURES = "kernel26 screen keyboard pci usbhost ext2 ext3 x86 \
+ acpi serial usbgadget"
+
+KERNEL_IMAGETYPE = "bzImage"
+
+SERIAL_CONSOLE = "115200 ttyS0"
+
+MACHINE_EXTRA_RRECOMMENDS = "kernel-modules eee-acpi-scripts"
+
+IMAGE_FSTYPES ?= "ext3 cpio.gz"
+
+GLIBC_ADDONS = "nptl"
+GLIBC_EXTRA_OECONF = "--with-tls"
diff --git a/common/common-bsp-x.inc b/common/common-bsp-x.inc
new file mode 100644
index 0000000..c012efd
--- /dev/null
+++ b/common/common-bsp-x.inc
@@ -0,0 +1,4 @@
+PREFERRED_PROVIDER_virtual/libx11 ?= "libx11-trim"
+PREFERRED_PROVIDER_virtual/libgl ?= "mesa-dri"
+PREFERRED_PROVIDER_virtual/xserver ?= "xserver-xf86-dri-lite"
+PREFERRED_PROVIDER_virtual/xserver-xf86 ?= "xserver-xf86-dri-lite"
--
1.7.0.4


[PATCH 0/6] factor out some common meta-intel settings

tom.zanussi@...
 

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

The meta-intel BSPs have some common settings - this just moves
them out int separate .inc files to simplify them and ease
maintenance.

I compiled and boot-tested into graphics using sato-live images
for each, with the exception of fishriver (I accidentally pulled
out a cable so can't boot into graphics at the moment) and
crownbay-noemgd (same as crownbay, pretty much).

I also didn't touch n450, since it's already factored out and
simplified.

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/mach-cleanup
http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/log/?h=tzanussi/mach-cleanup

Tom Zanussi (6):
meta-intel: add a couple common .inc files
meta-sugarbay: use common .inc files
meta-crownbay: use common .inc files
meta-fishriver: use common .inc files
meta-jasperforest: use common .inc files
meta-emenlow: use common .inc files

common/common-bsp-mach.inc | 13 +++++++++++++
common/common-bsp-x.inc | 4 ++++
meta-crownbay/conf/machine/crownbay-noemgd.conf | 19 ++-----------------
meta-crownbay/conf/machine/crownbay.conf | 19 ++-----------------
meta-emenlow/conf/machine/emenlow.conf | 17 ++---------------
meta-fishriver/conf/machine/fishriver.conf | 20 +++-----------------
meta-jasperforest/conf/machine/jasperforest.conf | 22 +++-------------------
meta-sugarbay/conf/machine/sugarbay.conf | 22 +++-------------------
8 files changed, 32 insertions(+), 104 deletions(-)
create mode 100644 common/common-bsp-mach.inc
create mode 100644 common/common-bsp-x.inc


the proper way to report bitbake fetch errors?

Robert P. J. Day
 

just so i'm doing this the right way, what is the appropriate way to
report bitbake fetch errors? with a fully-updated git repo, i just
ran:

$ bitbake -c fetchall -k core-image-sato

and got fetch errors for both of:

* sat-solver
* linux-libc-headers

should i post the more detailed output of the command? the contents
of the log files? etc, etc.

rday

--

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

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


Re: why does quick start guide refer to non-provided "poky-image-sato"?

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

I do have two branches (master and Bernard) in my yocto-docs contrib area. The master branch is used for updates to the upcoming release and is in various states of correctness/completeness. I guess I will need to take the time to do a push for every change I make to my local copy of yocto-docs master.

The docs that are on the website are Bernard only until we release.

ScottR

-----Original Message-----
From: yocto-bounces@... [mailto:yocto-bounces@...] On Behalf Of Richard Purdie
Sent: Thursday, July 14, 2011 4:15 PM
To: Robert P. J. Day
Cc: yocto@...
Subject: Re: [yocto] why does quick start guide refer to non-provided "poky-image-sato"?

On Thu, 2011-07-14 at 19:10 -0400, Robert P. J. Day wrote:
On Thu, 14 Jul 2011, Joshua Lock wrote:

As I understand it documentation repository updates are reflected on
the website so the docs tend to reflect the released version.

It would be nice to be able to provide development & release
documentation but I can't see it happening any time soon.
ok, that explains it but it doesn't defend it. IMHO, any single
versioned tarball or repository checkout should always be internally
consistent, and that includes embedded documentation. when i do a
"git pull" of any software, i expect the contents of any docs/
directory to reflect what's there.

if you want to publicly publish the docs that reflect the last
official release, then build those docs from the appropriate git tag.
I agree that the docs in master should reflect the code in master and
that the docs on the bernard branch should be the ones which make the
bernard references.

Which or both can end up on the website as needed which is a separate
issue.

I thought this had been fixed and Scott had two branches so what's going
wrong? :/

Cheers,

Richard

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


Re: why does quick start guide refer to non-provided "poky-image-sato"?

Richard Purdie
 

On Thu, 2011-07-14 at 19:10 -0400, Robert P. J. Day wrote:
On Thu, 14 Jul 2011, Joshua Lock wrote:

As I understand it documentation repository updates are reflected on
the website so the docs tend to reflect the released version.

It would be nice to be able to provide development & release
documentation but I can't see it happening any time soon.
ok, that explains it but it doesn't defend it. IMHO, any single
versioned tarball or repository checkout should always be internally
consistent, and that includes embedded documentation. when i do a
"git pull" of any software, i expect the contents of any docs/
directory to reflect what's there.

if you want to publicly publish the docs that reflect the last
official release, then build those docs from the appropriate git tag.
I agree that the docs in master should reflect the code in master and
that the docs on the bernard branch should be the ones which make the
bernard references.

Which or both can end up on the website as needed which is a separate
issue.

I thought this had been fixed and Scott had two branches so what's going
wrong? :/

Cheers,

Richard


Re: why does quick start guide refer to non-provided "poky-image-sato"?

Robert P. J. Day
 

On Thu, 14 Jul 2011, Joshua Lock wrote:

As I understand it documentation repository updates are reflected on
the website so the docs tend to reflect the released version.

It would be nice to be able to provide development & release
documentation but I can't see it happening any time soon.
ok, that explains it but it doesn't defend it. IMHO, any single
versioned tarball or repository checkout should always be internally
consistent, and that includes embedded documentation. when i do a
"git pull" of any software, i expect the contents of any docs/
directory to reflect what's there.

if you want to publicly publish the docs that reflect the last
official release, then build those docs from the appropriate git tag.

rday

--

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

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


Re: why does quick start guide refer to non-provided "poky-image-sato"?

Joshua Lock <josh@...>
 

On Thu, 2011-07-14 at 18:01 -0400, Robert P. J. Day wrote:
On Thu, 14 Jul 2011, Rifenbark, Scott M wrote:

Robert,

My understanding was that the target for this sample command could
not be 'core-image-sato' for the QS version on the website, which
supports Bernard. Maybe someone out there has a bit more
information on details to your question.

ScottR

-----Original Message-----
From: yocto-bounces@... [mailto:yocto-bounces@...] On Behalf Of Robert P. J. Day
Sent: Thursday, July 14, 2011 2:32 PM
To: Yocto discussion list
Subject: [yocto] why does quick start guide refer to non-provided "poky-image-sato"?


maybe i'm misreading something, but the yocto QS guide provides the
sample command:

$ bitbake -k poky-image-sato

however, nothing provides that target. i can see the git log entry:

commit 1947b17478187bb623da74484747e470ce42d206
Author: Scott Rifenbark <scott.m.rifenbark@...>
Date: Tue May 10 12:50:36 2011 -0500

documentation/yocto-project-qs/yocto-project-qs.xml: changed build command

The command used in the example to build an image was using
'bitbake core-image-sato', which is only available in master and
not Bernard. So, I changed the command to be 'bitbake poky-image-sato'
at Dave Stewart's request. He located and pointed out the error.

(From yocto-docs rev: 3fa83550aaec5a3549825814a77fa7a823a2daea)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@...>
Signed-off-by: Richard Purdie <richard.purdie@...>

but it seems that "core-image-sato" is perfectly valid, at least at
the moment. clarification?
currently, scripts/oe-setup-builddir lists one of the common targets
as "core-image-sato", so certainly *something* is out of sync.
As I understand it documentation repository updates are reflected on the
website so the docs tend to reflect the released version.

It would be nice to be able to provide development & release
documentation but I can't see it happening any time soon.

Joshua
--
Joshua Lock
Yocto Project "Johannes Factotum"
Intel Open Source Technology Centre


[PATCH 1/1] mm: use alloc_bootmem_node_nopanic() on really needed path

Darren Hart <darren@...>
 

From: Yinghai Lu <yinghai@...>

commit 8f389a99b652aab5b42297280bd94d95933ad12f upstream.

Stefan found nobootmem does not work on his system that has only 8M of
RAM. This causes an early panic:

BIOS-provided physical RAM map:
BIOS-88: 0000000000000000 - 000000000009f000 (usable)
BIOS-88: 0000000000100000 - 0000000000840000 (usable)
bootconsole [earlyser0] enabled
Notice: NX (Execute Disable) protection missing in CPU or disabled in BIOS!
DMI not present or invalid.
last_pfn = 0x840 max_arch_pfn = 0x100000
init_memory_mapping: 0000000000000000-0000000000840000
8MB LOWMEM available.
mapped low ram: 0 - 00840000
low ram: 0 - 00840000
Zone PFN ranges:
DMA 0x00000001 -> 0x00001000
Normal empty
Movable zone start PFN for each node
early_node_map[2] active PFN ranges
0: 0x00000001 -> 0x0000009f
0: 0x00000100 -> 0x00000840
BUG: Int 6: CR2 (null)
EDI c034663c ESI (null) EBP c0329f38 ESP c0329ef4
EBX c0346380 EDX 00000006 ECX ffffffff EAX fffffff4
err (null) EIP c0353191 CS c0320060 flg 00010082
Stack: (null) c030c533 000007cd (null) c030c533 00000001 (null) (null)
00000003 0000083f 00000018 00000002 00000002 c0329f6c c03534d6 (null)
(null) 00000100 00000840 (null) c0329f64 00000001 00001000 (null)
Pid: 0, comm: swapper Not tainted 2.6.36 #5
Call Trace:
[<c02e3707>] ? 0xc02e3707
[<c035e6e5>] 0xc035e6e5
[<c0353191>] ? 0xc0353191
[<c03534d6>] 0xc03534d6
[<c034f1cd>] 0xc034f1cd
[<c034a824>] 0xc034a824
[<c03513cb>] ? 0xc03513cb
[<c0349432>] 0xc0349432
[<c0349066>] 0xc0349066

It turns out that we should ignore the low limit of 16M.

Use alloc_bootmem_node_nopanic() in this case.

[akpm@...: less mess]
Signed-off-by: Yinghai LU <yinghai@...>
Reported-by: Stefan Hellermann <stefan@...>
Tested-by: Stefan Hellermann <stefan@...>
Cc: Ingo Molnar <mingo@...>
Cc: "H. Peter Anvin" <hpa@...>
Cc: Thomas Gleixner <tglx@...>
Cc: <stable@...> [2.6.34+]
Signed-off-by: Andrew Morton <akpm@...>
Signed-off-by: Linus Torvalds <torvalds@...>

Applied to linux-yocto-2.6.37

Signed-off-by: Darren Hart <dvhart@...>
---
include/linux/bootmem.h | 2 ++
mm/page_alloc.c | 7 ++++---
2 files changed, 6 insertions(+), 3 deletions(-)

diff --git a/include/linux/bootmem.h b/include/linux/bootmem.h
index 499dfe9..552875f 100644
--- a/include/linux/bootmem.h
+++ b/include/linux/bootmem.h
@@ -115,6 +115,8 @@ extern void *__alloc_bootmem_low_node(pg_data_t *pgdat,
__alloc_bootmem_nopanic(x, PAGE_SIZE, __pa(MAX_DMA_ADDRESS))
#define alloc_bootmem_node(pgdat, x) \
__alloc_bootmem_node(pgdat, x, SMP_CACHE_BYTES, __pa(MAX_DMA_ADDRESS))
+#define alloc_bootmem_node_nopanic(pgdat, x) \
+ __alloc_bootmem_node_nopanic(pgdat, x, SMP_CACHE_BYTES, __pa(MAX_DMA_ADDRESS))
#define alloc_bootmem_pages_node(pgdat, x) \
__alloc_bootmem_node(pgdat, x, PAGE_SIZE, __pa(MAX_DMA_ADDRESS))
#define alloc_bootmem_pages_node_nopanic(pgdat, x) \
diff --git a/mm/page_alloc.c b/mm/page_alloc.c
index b8b32aa..1c28e48 100644
--- a/mm/page_alloc.c
+++ b/mm/page_alloc.c
@@ -3464,7 +3464,7 @@ int zone_wait_table_init(struct zone *zone, unsigned long zone_size_pages)

if (!slab_is_available()) {
zone->wait_table = (wait_queue_head_t *)
- alloc_bootmem_node(pgdat, alloc_size);
+ alloc_bootmem_node_nopanic(pgdat, alloc_size);
} else {
/*
* This case means that a zone whose size was 0 gets new memory
@@ -4037,7 +4037,8 @@ static void __init setup_usemap(struct pglist_data *pgdat,
unsigned long usemapsize = usemap_size(zonesize);
zone->pageblock_flags = NULL;
if (usemapsize)
- zone->pageblock_flags = alloc_bootmem_node(pgdat, usemapsize);
+ zone->pageblock_flags = alloc_bootmem_node_nopanic(pgdat,
+ usemapsize);
}
#else
static void inline setup_usemap(struct pglist_data *pgdat,
@@ -4203,7 +4204,7 @@ static void __init_refok alloc_node_mem_map(struct pglist_data *pgdat)
size = (end - start) * sizeof(struct page);
map = alloc_remap(pgdat->node_id, size);
if (!map)
- map = alloc_bootmem_node(pgdat, size);
+ map = alloc_bootmem_node_nopanic(pgdat, size);
pgdat->node_mem_map = map + (pgdat->node_start_pfn - start);
}
#ifndef CONFIG_NEED_MULTIPLE_NODES
--
1.7.1


[PATCH 0/1][linux-yocto] Fix boot failure with less than 17 MB RAM

Darren Hart <darren@...>
 

From: Darren Hart <dvhart@...>

The following patch from mainline addresses an issues that prevented my
qemu testing from booting in less than 17M of memory. With this page,
the kernel can boot to init in 8M of memory.

Apply to yocto/standard/base

The following changes since commit bb8e31f2c99f5e007660d4540df246fb7ecfa746:

USB: ehci: remove structure packing from ehci_def (2011-06-22 14:23:26 -0400)

are available in the git repository at:
git://git.yoctoproject.org/linux-yocto-2.6.37-contrib dvhart/mm
http://git.yoctoproject.org/cgit.cgi/linux-yocto-2.6.37-contrib/log/?h=dvhart/mm

Yinghai Lu (1):
mm: use alloc_bootmem_node_nopanic() on really needed path

include/linux/bootmem.h | 2 ++
mm/page_alloc.c | 7 ++++---
2 files changed, 6 insertions(+), 3 deletions(-)