Re: [Angstrom-devel] Build layout change branch of setup-scripts.
Op 13 nov. 2011, om 21:44 heeft Martin Jansa het volgende geschreven: On Sun, Nov 13, 2011 at 08:24:33PM +0100, Koen Kooi wrote: Op 13 nov. 2011, om 19:53 heeft Dmitry Eremin-Solenikov het volgende geschreven: On 11/12/2011 05:03 PM, Koen Kooi wrote: Good morning everyone! The setup-scripts repo now has a branch to experiment with the build layout: http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/setup-scripts/log/?h=layout-rework The biggest changes are: * build/tmp-DISTRO is now build/scratch I'd oppose this change. Currently I can use oebb.sh to generate both bleeding edge angstrom and angstrom-2010.x. And that's not talking about empty DISTRO and other DISTROs. Could you please reconsider this change? What about scratch-$DISTRO? scratch/$DISTRO? I'd like to keep the 'top' directory the same, it has proven to be confusing to new users when it changes name. * build/tmp-DISTRO/sstate-cache is now cache/sstate * build/tmp-DISTRO/deploy is now deploy Good ideas! I'd really like to find a better name for 'deploy', but 'output' or 'results' aren't a whole lot better, so suggestions appreciated! I'd vote for 'output', 'build-results' or 'built' I like 'build-results' :) * generate bblayers.conf from layers.txt With some sort of blacklist please! With your recent patches it's simple to switch layers on and off (especially BSP layers). But with autogenerated bblayers.conf it would be PITA. Exactly, I don't know how it's going to be implemented, but turning things off/on easily is certainly needed. Ideally oebb would only enable the BSP layers it needs for a given machine, but mixed repos (e.g.meta-smartphone) make that difficult. That's not a complaint against meta-smartphone, though. Is switching BSPs on and off good idea for stable feeds? And that's not complaint against generating bblayers.conf, just against idea to switch layers on and off because it's easy. It is most certainly not a good idea for stable feeds if you start removing layers. Because ie with few PRINC in BSP layer you can get PRs going backwards. I know you're aware of such problems and won't allow that to happen. Just pointing for others that layers are not such nice colorfull boxes from yocto diagram, one can stack easily and then switch them on and off everytime there is something nice or bad. I think the implementation should issue a big warning when removing layers, maybe we could even get packagehistory.bbclass to help us with that. regards, Koen Regards, * allow injection of patches into metadata (e.g. patches on top of oe-core) to avoid needing forks Do I miss something? oebb.sh works perfectly with patches applied on top of oe-core and other layers. Or you mean something else? It works great, but I'd like to have everyone use my patches on top of oe-core, without needing to fork the oe-core repo. regards, Koen ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel -- Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel signature.asc Description: Message signed with OpenPGP using GPGMail ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] [PATCH] angstrom-version.bb: fix LexToken(TOKEN, 'nobranch', 0, 0) error
Applied, thanks!
Op 14 nov. 2011, om 11:35 heeft Bernhard Guillon het volgende geschreven:
Strip braces from git revision string e.g. from (no branch)
to not confuse the tokenizing. Without the following error
occures on a detached (no branch) git branch :
File sources/bitbake/lib/bb/pysh/pyshyacc.py, line 646, in
p_error(p=LexToken(TOKEN,'nobranch',0,0)):
w(' %r\n' % n)
raise sherrors.ShellSyntaxError(''.join(msg))
ShellSyntaxError: LexToken(TOKEN,'nobranch',0,0)
followed by:
LexToken(RPARENS,')',0,0)
LexToken(TOKEN,':5260401eb0cfe37a7358296866b4b43a167817ff\nmeta
= ',0,0)
LexToken(LPARENS,'(',0,0)
LexToken(TOKEN,'nobranch',0,0)
LexToken(RPARENS,')',0,0)
Signed-off-by: Bernhard Guillon bernhard.guil...@hale.at
---
recipes-angstrom/angstrom/angstrom-version.bb |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/recipes-angstrom/angstrom/angstrom-version.bb
b/recipes-angstrom/angstrom/angstrom-version.bb
index eb3eade..c91db4a 100644
--- a/recipes-angstrom/angstrom/angstrom-version.bb
+++ b/recipes-angstrom/angstrom/angstrom-version.bb
@@ -2,7 +2,7 @@ LICENSE = MIT
LIC_FILES_CHKSUM =
file://${COREBASE}/LICENSE;md5=3f40d7994397109285ec7b81fdeb3b58
PV = ${DISTRO_VERSION}
-PR = r10
+PR = r11
PE = 2
SRC_URI = file://lsb_release
@@ -13,7 +13,7 @@ PACKAGE_ARCH = ${MACHINE_ARCH}
def get_layers(bb, d):
layers = (bb.data.getVar(BBLAYERS, d, 1) or ).split()
layers_branch_rev = [%-17s = \%s:%s\ % (os.path.basename(i), \
- base_get_metadata_git_branch(i, None).strip(), \
+ base_get_metadata_git_branch(i, None).strip().strip('()'), \
base_get_metadata_git_revision(i, None)) \
for i in layers]
i = len(layers_branch_rev)-1
--
1.7.1
--
Scanned by MailScanner.
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] [PATCH][scripts 1/7] scripts/listpaches: also print current status of repo
Op 13 nov. 2011, om 00:25 heeft Dmitry Eremin-Solenikov het volgende geschreven: On Sat, Nov 12, 2011 at 08:42:43AM +0100, Koen Kooi wrote: Do you have a repo where those patches can be git pulled from? The following changes since commit 45840ac30c549784fabb963cdb9a6b76820c0ff3: Merge branch 'oe-core' (2011-11-01 09:32:36 +0100) are available in the git repository at: g...@github.com:lumag/oe-setup-scripts.git for-koen Dmitry Eremin-Solenikov (5): scripts/listpaches: also print current status of repo scripts/listpending: add a script to list not yet used revisions bblayers: enable meta-handheld layer layers.txt: add meta-opie layer bblayers.conf: add meta-opie layer Applied, thanks! signature.asc Description: Message signed with OpenPGP using GPGMail ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Build layout change branch of setup-scripts.
Op 13 nov. 2011, om 19:53 heeft Dmitry Eremin-Solenikov het volgende geschreven: On 11/12/2011 05:03 PM, Koen Kooi wrote: Good morning everyone! The setup-scripts repo now has a branch to experiment with the build layout: http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/setup-scripts/log/?h=layout-rework The biggest changes are: * build/tmp-DISTRO is now build/scratch I'd oppose this change. Currently I can use oebb.sh to generate both bleeding edge angstrom and angstrom-2010.x. And that's not talking about empty DISTRO and other DISTROs. Could you please reconsider this change? What about scratch-$DISTRO? scratch/$DISTRO? I'd like to keep the 'top' directory the same, it has proven to be confusing to new users when it changes name. * build/tmp-DISTRO/sstate-cache is now cache/sstate * build/tmp-DISTRO/deploy is now deploy Good ideas! I'd really like to find a better name for 'deploy', but 'output' or 'results' aren't a whole lot better, so suggestions appreciated! I'd vote for 'output', 'build-results' or 'built' I like 'build-results' :) * generate bblayers.conf from layers.txt With some sort of blacklist please! With your recent patches it's simple to switch layers on and off (especially BSP layers). But with autogenerated bblayers.conf it would be PITA. Exactly, I don't know how it's going to be implemented, but turning things off/on easily is certainly needed. Ideally oebb would only enable the BSP layers it needs for a given machine, but mixed repos (e.g.meta-smartphone) make that difficult. That's not a complaint against meta-smartphone, though. * allow injection of patches into metadata (e.g. patches on top of oe-core) to avoid needing forks Do I miss something? oebb.sh works perfectly with patches applied on top of oe-core and other layers. Or you mean something else? It works great, but I'd like to have everyone use my patches on top of oe-core, without needing to fork the oe-core repo. regards, Koen signature.asc Description: Message signed with OpenPGP using GPGMail ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] [PATCH][scripts 3/7] local.conf: allow user to override DISTRO
Op 12 nov. 2011, om 12:42 heeft Dmitry Eremin-Solenikov het volgende geschreven: On Sat, Nov 12, 2011 at 11:44 AM, Koen Kooi k...@dominion.thruhere.net wrote: Op 12 nov. 2011, om 00:42 heeft Dmitry Eremin-Solenikov het volgende geschreven: oebb.sh is usefull with distributions other than angstrom. Allow users to override DISTRO from environment. This is handing people a loaded gun and pointing it at their feet, so: NAK Why is this a loaded gun? Could you please be a little bit more descriptive on this? These scripts are there to give people a known good setup, picking up too much environment vars is too dangerous. Changing distro should be a conscious choice requiring effort, since it deeply affects the build experience. regards, Koen signature.asc Description: Message signed with OpenPGP using GPGMail ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
[Angstrom-devel] Build layout change branch of setup-scripts.
Good morning everyone! The setup-scripts repo now has a branch to experiment with the build layout: http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/setup-scripts/log/?h=layout-rework The biggest changes are: * build/tmp-DISTRO is now build/scratch * build/tmp-DISTRO/sstate-cache is now cache/sstate * build/tmp-DISTRO/deploy is now deploy I'd really like to find a better name for 'deploy', but 'output' or 'results' aren't a whole lot better, so suggestions appreciated! These changes are guided by the following goals: 1) make the build output easier to find for new users 2) make sstate and sstate-mirrors easier to use 3) put all 'volatile' data into a scratch directory to make it clear that it can and will go away from time to time This is still a work in progress so ideas and patches are very welcome! Apart from the layout rework the following items are on the TODO list as well: * generate bblayers.conf from layers.txt * allow injection of patches into metadata (e.g. patches on top of oe-core) to avoid needing forks * a 'clean' command to remove scratch/pseudodone/sstate, etc * make oebb.sh less chatty and have a -v option * put more config under git control * have a 'combo repo' option that will create a combo-repo from the current state * external toolchain integration * add pointer to build output after successfull bitbake run (e.g. your image can be found at: location regards, Koen signature.asc Description: Message signed with OpenPGP using GPGMail ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Koen Kooi : oebb: pull OE from github mirror
Op 11 nov. 2011, om 10:04 heeft Angstrom Git Repos het volgende geschreven: Module: setup-scripts Branch: refs/tags/maintenance-2011.03 Commit: c714eecb0ed532f70cde435c05e420809d59a534 Author: Koen Kooi k...@dominion.thruhere.net Date: Tue May 10 11:16:47 2011 +0200 oebb: pull OE from github mirror Signed-off-by: Koen Kooi k...@dominion.thruhere.net This is a tag people can use when needing to build the good old maintenance branch instead of oe-core. regards, Koen signature.asc Description: Message signed with OpenPGP using GPGMail ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] [PATCH][scripts 1/7] scripts/listpaches: also print current status of repo
Do you have a repo where those patches can be git pulled from? Op 12 nov. 2011, om 00:42 heeft Dmitry Eremin-Solenikov het volgende geschreven: Signed-off-by: Dmitry Eremin-Solenikov dbarysh...@gmail.com --- scripts/listpatches.sh |1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/scripts/listpatches.sh b/scripts/listpatches.sh index 00e27ef..cbb1513 100755 --- a/scripts/listpatches.sh +++ b/scripts/listpatches.sh @@ -18,5 +18,6 @@ do cd $dir git log --pretty=oneline $rev..HEAD git diff --stat HEAD + git status -s cd - /dev/null done -- 1.7.2.5 ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel signature.asc Description: Message signed with OpenPGP using GPGMail ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] [PATCH][scripts 7/7] layers.txt: add meta-micro layer
Op 12 nov. 2011, om 00:42 heeft Dmitry Eremin-Solenikov het volgende geschreven: Add a layer with minimal distribution NAK, this is the angstrom setupscripts, minimal can fork the scripts as they did with angstrom if they want support. signature.asc Description: Message signed with OpenPGP using GPGMail ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] [PATCH][scripts 3/7] local.conf: allow user to override DISTRO
Op 12 nov. 2011, om 00:42 heeft Dmitry Eremin-Solenikov het volgende geschreven: oebb.sh is usefull with distributions other than angstrom. Allow users to override DISTRO from environment. This is handing people a loaded gun and pointing it at their feet, so: NAK signature.asc Description: Message signed with OpenPGP using GPGMail ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Automatic network device configuration
Op 10 nov. 2011, om 18:42 heeft Joel A Fernandes het volgende geschreven: Hi, I have a general question about network configuration in Angstrom, In angstrom we support the following method: 1) connman 2) networkmanager 3) ifupdown So there's not generic answer to networking questions, it depends on the set of installed packages in your rootfs. I'd advice you to ask the upstream projects for best practices. regards, Koen signature.asc Description: Message signed with OpenPGP using GPGMail ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] [PATCH] oebb.sh: Update MACHINE entry in auto.conf
Applied, thanks!
Op 21 okt. 2011, om 01:54 heeft Khem Raj het volgende geschreven:
Currently we dont update the machine entry in auto.conf
except for first time when autoconf is created. This
patch lets us edit auto.conf when we do
oebb.sh config machine subsequently. It will update
MACHINE entry in auto.conf
Signed-off-by: Khem Raj raj.k...@gmail.com
---
oebb.sh |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/oebb.sh b/oebb.sh
index f7247b8..a89d497 100755
--- a/oebb.sh
+++ b/oebb.sh
@@ -265,7 +265,8 @@ fi
cat ${OE_BUILD_DIR}/conf/auto.conf _EOF
MACHINE ?= ${MACHINE}
_EOF
-
+else
+ eval sed -i -e 's/^MACHINE.*$/MACHINE ?= ${MACHINE}/g'
${OE_BUILD_DIR}/conf/auto.conf
fi
}
--
1.7.5.4
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] [PATCH 1/2] angstrom-2010-preferred-versions: Pin xserver-xorg to 1.11.1
Applied, thanks! Op 21 okt. 2011, om 00:42 heeft Khem Raj het volgende geschreven: Signed-off-by: Khem Raj raj.k...@gmail.com --- .../include/angstrom-2010-preferred-versions.inc |3 +++ 1 files changed, 3 insertions(+), 0 deletions(-) diff --git a/conf/distro/include/angstrom-2010-preferred-versions.inc b/conf/distro/include/angstrom-2010-preferred-versions.inc index 7caa67b..f407ff8 100644 --- a/conf/distro/include/angstrom-2010-preferred-versions.inc +++ b/conf/distro/include/angstrom-2010-preferred-versions.inc @@ -67,6 +67,9 @@ PREFERRED_VERSION_wget = 1.11.4 PREFERRED_VERSION_xserver-common = 1.34 PREFERRED_VERSION_xserver-kdrive = 1.7.99.2 +#xserver +PREFERRED_VERSION_xserver-xorg = 1.11.1 + # # meta-moblin package SRCREVs # -- 1.7.5.4 ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] [PATCH 2/2] angstrom-2010-preferred-versions: Pin the libtool version to 2.4.2
Op 21 okt. 2011, om 00:42 heeft Khem Raj het volgende geschreven: Pull it after http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/gold-updates has been applied to oe-core Can you ping me if I'm too slow in applying this? ELC-E is around the corner and I need to finish my presentation :) Signed-off-by: Khem Raj raj.k...@gmail.com --- .../include/angstrom-2010-preferred-versions.inc |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/conf/distro/include/angstrom-2010-preferred-versions.inc b/conf/distro/include/angstrom-2010-preferred-versions.inc index f407ff8..1316817 100644 --- a/conf/distro/include/angstrom-2010-preferred-versions.inc +++ b/conf/distro/include/angstrom-2010-preferred-versions.inc @@ -1,6 +1,6 @@ ANGSTROM_MESA_VERSION = 7.11 ANGSTROM_QT_VERSION ?= 4.7.4 -ANGSTROM_LIBTOOL_VERSION = 2.4 +ANGSTROM_LIBTOOL_VERSION = 2.4.2 # Use new sysroot feature LIBTOOL_HAS_SYSROOT = yes -- 1.7.5.4 ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] ti-cgt6x_6.1.17 md5 hash
Op 21 okt. 2011, om 05:01 heeft Chris Whittenburg het volgende geschreven: Not sure if this is the right place to report this issue, but I've run into it a couple times lately... I think the md5 hash for ti_cgt_c6000_6.1.17_setup_linux_x86.bin has changed from the one in the recipe cgt6x_6.1.17.bb Perhaps TI changed the install file? TI did in fact change the file :( Updating the checksums will cause people who already downloaded the old file (e.g. me) to go thru pains without a guarantee that TI won't change the file again. regards, Koen ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] [PATCH] angstrom-2010.x: Suffix binutils-cross-canadian with TRANSLATED_TARGET_ARCH
Applied, thanks!
Op 21 okt. 2011, om 06:58 heeft Khem Raj het volgende geschreven:
Thats what PN is set to in binutils-cross-canadian recipes
so we should use that for locking PREFERRED_VERSION
Signed-off-by: Khem Raj raj.k...@gmail.com
---
conf/distro/angstrom-2010.x.conf |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/conf/distro/angstrom-2010.x.conf
b/conf/distro/angstrom-2010.x.conf
index 6421141..468459b 100644
--- a/conf/distro/angstrom-2010.x.conf
+++ b/conf/distro/angstrom-2010.x.conf
@@ -111,7 +111,7 @@ ANGSTROM_BINUTILS_VERSION?=
2.20.1
PREFERRED_VERSION_binutils ?=
${ANGSTROM_BINUTILS_VERSION}
PREFERRED_VERSION_binutils-cross ?=
${ANGSTROM_BINUTILS_VERSION}
PREFERRED_VERSION_binutils-crosssdk ?=
${ANGSTROM_BINUTILS_VERSION}
-PREFERRED_VERSION_binutils-cross-canadian?=
${ANGSTROM_BINUTILS_VERSION}
+PREFERRED_VERSION_binutils-cross-canadian-${TRANSLATED_TARGET_ARCH} ?=
${ANGSTROM_BINUTILS_VERSION}
PREFERRED_VERSION_gcc-cross-canadian-${TRANSLATED_TARGET_ARCH} ?=
${ANGSTROM_GCC_VERSION}
PREFERRED_VERSION_gcc?= ${ANGSTROM_GCC_VERSION}
--
1.7.5.4
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Modversion Problem
Op 21 okt. 2011, om 13:12 heeft Önder Kalacı het volgende geschreven: Hi, first of all, I look almost all previous threads but I have not seen any posts related to this, if I missed some sorry, in advance. Hi, I have a running tam3517 2.6.32 #238 Fri Jan 28 14:34:15 UTC 2011 armv7l unknown machine. I need to use cdc-acm.ko, so I try to use http://narcissus.angstrom-distribution.org/ to create a whole image and then copy the cdc-acm to my working system. When I use narcissus to to this, I have the following problem. When I try to insmod cdc-acm.ko, there is a format error and in the dmesg I see : cdc_acm: version magic '2.6.32 mod_unload modversions ARMv7 ' should be '2.6.32 mod_unload ARMv7 ' . What is this modversions, how can I create my kernel modules without that label? Thanks You need to rebuild your kernel, not try to change the labels, those are there for a reason :) The labels ensure your kernel and modules match. regards, Koen ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] [meta-ti][PATCH] signgp: Point S to WORKDIR
Op 21 okt. 2011, om 18:47 heeft Khem Raj het volgende geschreven:
This helps in bitbake finding the license files etc.
correctly
Signed-off-by: Khem Raj raj.k...@gmail.com
---
recipes-bsp/x-load/signgp.bb |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/recipes-bsp/x-load/signgp.bb b/recipes-bsp/x-load/signgp.bb
index 7aead67..2b60766 100644
--- a/recipes-bsp/x-load/signgp.bb
+++ b/recipes-bsp/x-load/signgp.bb
@@ -13,6 +13,8 @@ do_install() {
install -m 0755 signGP ${D}${bindir}
}
+S = ${WORKDIR}
+
Could you please add quotes around that?
regards,
Koen
NATIVE_INSTALL_WORKS = 1
BBCLASSEXTEND = native nativesdk
--
1.7.5.4
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] [PATCH meta-ti] sdcard_image: Copy user.txt/uEnv.txt if it exists in /boot
Op 20 okt. 2011, om 08:17 heeft Joel A Fernandes het volgende geschreven:
On Thu, Oct 20, 2011 at 12:40 AM, Koen Kooi k...@dominion.thruhere.net
wrote:
[added meta-ti list]
Op 20 okt. 2011, om 05:52 heeft Joel A Fernandes het volgende geschreven:
Pick up uEnv.txt/user.txt U-boot environment files installed in /boot
This doesn't match what the patch does :/
Yes it does
pick up implies you're adding something new instead of fixing it. Please
write better commit messages.
Signed-off-by: Joel A Fernandes joelag...@ti.com
---
classes/sdcard_image.bbclass |4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/classes/sdcard_image.bbclass b/classes/sdcard_image.bbclass
index ed9d779..c535ad2 100644
--- a/classes/sdcard_image.bbclass
+++ b/classes/sdcard_image.bbclass
@@ -86,8 +86,10 @@ IMAGE_CMD_sdimg () {
suffix=bin
fi
+ cp -v ${IMAGE_ROOTFS}/boot/{user.txt,uEnv.txt}
${WORKDIR}/tmp-mnt-boot || true
+
if [ -e ${IMAGE_ROOTFS}/boot/u-boot.$suffix ] ; then
- cp -v ${IMAGE_ROOTFS}/boot/{u-boot.$suffix,user.txt,uEnv.txt}
${WORKDIR}/tmp-mnt-boot || true
+ cp -v ${IMAGE_ROOTFS}/boot/{u-boot.$suffix}
${WORKDIR}/tmp-mnt-boot || true
Your patch is effectively a noop, I don't see the value in applying it.
There is quite a lot of value in applying it.
I suggest you try to build an image (cloud9 / ti-hw-bringup) and
notice that there is no uEnv.txt in the boot partition.
If you're fixing the bug that {1,2,3} will only pick 1, but forget 2,3 then
user.txt is still broken. If you're saying uboot.suffix is not in /boot, we
need to fix that. Either way, I'm not supposed to be guessing that, you should
explain that in the commit message or with comments in the code or both.
regards,
Koen
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] [PATCH v3 meta-ti] linux-ti33x-psp 3.1rc8: Add pin mux and init for beaglebone specific devices
Op 20 okt. 2011, om 08:54 heeft Joel A Fernandes het volgende geschreven: Updated the USER LED patch to include BeagleBone tester specific initialization/code. Build and run time tested. Signed-off-by: Joel A Fernandes joelag...@ti.com --- v3: * formatted patch with -B -C * Modified commit summary applied, thanks! ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] task-base(-extended) missing in systemd-image based images?
Op 20 okt. 2011, om 22:23 heeft Andreas Müller het volgende geschreven: On Thursday, October 20, 2011 07:32:33 AM Koen Kooi wrote: Task-basic is all the rage now :) This should fix it for you: There was something but I can't find it any more: What's wrong with task-base? It includes too much historical things (pxa27x-udc, wtf?) and I'd like to see if we can rewrite it into something more modern and smaller. ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Easy way to remove x11 from DISTRO_FEATURES?
Applied, thanks!
Op 19 okt. 2011, om 02:41 heeft Denys Dmytriyenko het volgende geschreven:
On Tue, Oct 18, 2011 at 04:15:38PM -0600, Gary Thomas wrote:
On 2011-10-18 16:08, Khem Raj wrote:
On (18/10/11 21:04), Daniel Lazzari wrote:
Hey everyone,
We are trying to build something of a custom distro on top of
Angstrom-core and need to remove x11 from the DISTRO_FEATURES as it
breaks dbus (since we aren't shipping x11). I can just comment it out in
angstrom.inc, but that requires editing files in meta-angstrom, which is
not our layer. Anyone know of a good way of removing this by only using
files in our own layer?
If you are using layer based angstrom(using oe-core and other layers) then
its easier where you can
specify your layer with highest layer priority and ahead of other layers
for
BBPATH then it will pick your layer first when it searches for recipes.
in conf/distro/include/angstrom.inc we have
DISTRO_FEATURES += x11
you could comment that out.
I think the point was to not have to modify the common/public layer.
n.b. I'm interested in the same thing for my own distro.
I use the following code a lot in Arago[1] for different list manipulations:
DISTRO_FEATURES := ${@oe_filter_out('x11', bb.data.getVar('DISTRO_FEATURES',
d, 1), d)}
Just be careful as oe_filter_out() seems to match the substring, unless you
specify it as regex, so all values beginning with x11* will be filtered out.
[1]
http://arago-project.org/git/?p=arago.git;a=blob;f=recipes/qt4/qt4-embedded-4.7.2/amend.inc;h=5c053a76dc1607646782d7604145b4120c93770b;hb=refs/heads/next
--
Denys
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Koen Kooi : update-rc.d 0.7: don't let update-rc. d start initscripts when systemd is present
Op 19 okt. 2011, om 09:54 heeft Steffen Sledz het volgende geschreven: On 18.10.2011 14:24, Angstrom Git Repos wrote: Module: meta-angstrom Branch: master Commit: 36a550b314ebb0c30d1c0e565ded197a8682c025 Author: Koen Kooi k...@dominion.thruhere.net Date: Tue Oct 18 13:47:58 2011 +0200 update-rc.d 0.7: don't let update-rc.d start initscripts when systemd is present This should cleanup the error messages shown at first boot a lot It is possible to install systemd package into an existing installation. Right? If yes you need to disable starting of all relevant initscripts within the systemd postinst too. Systemd itself already takes care of that since it's /sbin/init after installation :) ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] task-base(-extended) missing in systemd-image based images?
Op 20 okt. 2011, om 00:09 heeft Andreas Müller het volgende geschreven: just finished a build of xfce-nm-image.bb and was surprised of small size. I checked and found that all the recipes included in my machine conf by MACHINE_EXTRA_RRECOMMENDS = .. are missing in the image ( in my case kernel-modules! ). These are included by task-base.bb. Is it possible that this is missing in systemd-image based images? Task-basic is all the rage now :) This should fix it for you: http://cgit.openembedded.org/meta-openembedded/commit/?id=959d90a32409231e3e121277c64ff7839f1d815e regards, Koen ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] [PATCH meta-ti] sdcard_image: Copy user.txt/uEnv.txt if it exists in /boot
[added meta-ti list]
Op 20 okt. 2011, om 05:52 heeft Joel A Fernandes het volgende geschreven:
Pick up uEnv.txt/user.txt U-boot environment files installed in /boot
This doesn't match what the patch does :/
Signed-off-by: Joel A Fernandes joelag...@ti.com
---
classes/sdcard_image.bbclass |4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/classes/sdcard_image.bbclass b/classes/sdcard_image.bbclass
index ed9d779..c535ad2 100644
--- a/classes/sdcard_image.bbclass
+++ b/classes/sdcard_image.bbclass
@@ -86,8 +86,10 @@ IMAGE_CMD_sdimg () {
suffix=bin
fi
+ cp -v ${IMAGE_ROOTFS}/boot/{user.txt,uEnv.txt} ${WORKDIR}/tmp-mnt-boot
|| true
+
if [ -e ${IMAGE_ROOTFS}/boot/u-boot.$suffix ] ; then
- cp -v ${IMAGE_ROOTFS}/boot/{u-boot.$suffix,user.txt,uEnv.txt}
${WORKDIR}/tmp-mnt-boot || true
+ cp -v ${IMAGE_ROOTFS}/boot/{u-boot.$suffix}
${WORKDIR}/tmp-mnt-boot || true
Your patch is effectively a noop, I don't see the value in applying it.
regards,
Koen
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] [meta-ettus] console-gnuradio-image: angstrom systemd-image has moved to recipes-images/angstrom
It slipped below my radar because I was still using the old meta-ettus uri. No cookie for me :) Op 15 okt. 2011 om 18:25 heeft Philip Balister phi...@balister.org het volgende geschreven: Thanks, applied. Philip On 10/15/2011 10:23 AM, Andreas Müller wrote: Signed-off-by: Andreas Müller schnitzelt...@gmx.de --- recipes/images/console-gnuradio-image.bb |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/recipes/images/console-gnuradio-image.bb b/recipes/images/console-gnuradio-image.bb index 68ba57d..2c8a828 100644 --- a/recipes/images/console-gnuradio-image.bb +++ b/recipes/images/console-gnuradio-image.bb @@ -1,4 +1,4 @@ -require recipes-angstrom/images/systemd-image.bb +require recipes-images/angstrom/systemd-image.bb IMAGE_INSTALL += \ task-base-extended \ ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] [meta-ti] Pull request: beaglebone-tester add
Op 14 okt. 2011, om 01:56 heeft Fernandes, Joel A het volgende geschreven: Hi Koen, Could you pull the first 5 patches against meta-ti master branch from: git://github.com/joelagnel/meta-texasinstruments.git (branch for-koen) Joel A Fernandes (5): beaglebone-tester: A component-based test framework for BeagleBone This is missing dependencies on e.g. iputils. Also, kerner-module-foo must never be in RDEPENS, only in RRECOMMENDS. Style related: variables are set in recipes in the order they are used so packaging variables like RDEPENDS and FILES go below do_install ti-hw-bringup-image: Add iputils See above ti-hw-bringup-image: Add beaglebone-tester That should go into the cloud9 image, not the regular hardware bringup one ti-hw-bringup-image: Add kernel-modules package Applied, thanks linux-am335x-joel: Enable g_file_storage kernel module CONFIG_USB_FILE_STORAGE is deprecated, CONFIG_USB_MASS_STORAGE should be used instead and is already turned on in the defconfig. regards, Koen ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] [meta-ti] Pull request: beaglebone-tester add
Op 14 okt. 2011, om 10:51 heeft Joel A Fernandes het volgende geschreven: On Fri, Oct 14, 2011 at 2:35 AM, Koen Kooi k...@dominion.thruhere.net wrote: Op 14 okt. 2011, om 01:56 heeft Fernandes, Joel A het volgende geschreven: Hi Koen, Could you pull the first 5 patches against meta-ti master branch from: git://github.com/joelagnel/meta-texasinstruments.git (branch for-koen) Joel A Fernandes (5): beaglebone-tester: A component-based test framework for BeagleBone This is missing dependencies on e.g. iputils. Also, kerner-module-foo must never be in RDEPENS, only in RRECOMMENDS. Style related: variables are set in recipes in the order they are used so packaging variables like RDEPENDS and FILES go below do_install Will do, thanks. ti-hw-bringup-image: Add iputils See above ti-hw-bringup-image: Add beaglebone-tester That should go into the cloud9 image, not the regular hardware bringup one Ok, then I'll add iputils and kernel-modules to the cloud9 image as well unless they already are. No, you should add iputils only to the tester recipe ti-hw-bringup-image: Add kernel-modules package Applied, thanks linux-am335x-joel: Enable g_file_storage kernel module CONFIG_USB_FILE_STORAGE is deprecated, CONFIG_USB_MASS_STORAGE should be used instead and is already turned on in the defconfig. Can we please include this, I have seen kernel panics and other instabilities with mass_storage. Hmmm, we're going to ship with g_multi as default, which uses mass_storage, so we'll need to sort out those bugs real soon! ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] openssh vs dropbear
Op 10 okt. 2011, om 18:28 heeft Khem Raj het volgende geschreven: On Sat, Oct 8, 2011 at 8:13 PM, Cliff Brake cliff.br...@gmail.com wrote: What are the tradeoffs between using openssh and dropbear? I'm using Angstrom/systemd images, and would prefer dropbear as its likely smaller, but want to make sure I understand the other tradeoffs. biggest win dropbear has is memory footprint both static and runtime and it lacks sftp-server openssh-sftp can be installed in parallel at a very low cost. Graeme added that to angstrom years ago :) ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] image packing bug?
Op 9 okt. 2011, om 20:48 heeft matti kaasinen het volgende geschreven:
Hi!
I'm not quite sure if this is proper forum for my question, but as it
somewhat smells a bug, I try first here.
I was possibly faced with a bug related to image packing when
bitbaking with following configuration:
Build Configuration:
BB_VERSION= 1.12.0
METADATA_BRANCH = 2011.03-maintenance
METADATA_REVISION = f9c0bce
TARGET_ARCH = arm
TARGET_OS = linux-gnueabi
MACHINE = at91sam9260ek
DISTRO= angstrom
DISTRO_VERSION= 2011.03
TARGET_FPU= soft
One recipe - called recipe-aa_1.0.bb
was picked from it's dev packate (recipe-aa-dev_1.0-r0.6_at91sam9260ek.ipk).
It was tied in recipe-bb_1.0.bb with
RDEPENDS_${PN} = recipe-aa udev
Then recipe-bb_1.0.bb was included to image in
initramfs-image.bbappend with statement:
IMAGE_INSTALL_append = recipe-bb
Anyone followed? Anyhow, everything else goes all right, but recipe-aa
is always taken from wrong package (-dev).
Could the reason for this be RDEPENDS_${PN} = recipe-aa udev
statement as there is this 'udev'? Could bitbake use udev string to
relate recipe-aa with recipe-aa-dev package?
Is there any parameter I should use to force using recipe-aa(no -dev) version?
I bet aa.bb puts a .so in aa-dev. Have a look at
http://dominion.thruhere.net/koen/cms/the-testlab-strikes-again for a similar
situation.
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] [PATCH v2 meta-ti] u-boot: added version 2011.09-rc1
this one has been applied for a few days now Op 23 sep. 2011 om 18:26 heeft Joel A Fernandes joelag...@ti.com het volgende geschreven: From: Jason Kridner j...@ti.com There is a v2011.09 tag on the mainline, but I haven't seen a release notice go out. It didn't make sense to me to try to carry-forward those all patches since the release tag, so I simply picked the latest tag in the maineline. Patched and tested on BeagleBoard-xM revision C. USB Ethernet was tested with: setenv usbethaddr de:ad:be:ef:00:01 usb start dhcp^C setenv ipaddr 10.0.1.2 ping 10.0.1.1 USB Storage was tested with: above usb part fatls usb 0 led command was tested with: led all off led all on led 1 on led 1 off gpio command tested with: gpio input 4 hold USER button gpio input 4 release USER button Also performed boot test. Signed-off-by: Jason Kridner j...@ti.com Signed-off-by: Joel A Fernandes joelag...@ti.com --- v2 changes: * Dropped PV * Leave L2 cache enabled ...-beagleboard-config-disable-cache-for-USB.patch | 33 + ...02-beagleboard-config-enable-gpio-command.patch | 25 + ...d-some-timeout-durations-for-MMC-and-EHCI.patch | 39 recipes-bsp/u-boot/u-boot_2011.09.bb | 21 +++ 4 files changed, 118 insertions(+), 0 deletions(-) create mode 100644 recipes-bsp/u-boot/u-boot/2011.09/0001-HACK-beagleboard-config-disable-cache-for-USB.patch create mode 100644 recipes-bsp/u-boot/u-boot/2011.09/0002-beagleboard-config-enable-gpio-command.patch create mode 100644 recipes-bsp/u-boot/u-boot/2011.09/0003-Increased-some-timeout-durations-for-MMC-and-EHCI.patch create mode 100644 recipes-bsp/u-boot/u-boot_2011.09.bb diff --git a/recipes-bsp/u-boot/u-boot/2011.09/0001-HACK-beagleboard-config-disable-cache-for-USB.patch b/recipes-bsp/u-boot/u-boot/2011.09/0001-HACK-beagleboard-config-disable-cache-for-USB.patch new file mode 100644 index 000..a2776e9 --- /dev/null +++ b/recipes-bsp/u-boot/u-boot/2011.09/0001-HACK-beagleboard-config-disable-cache-for-USB.patch @@ -0,0 +1,33 @@ +From 03b9bca863257cb24d8f11bb773ad2b8dff820c6 Mon Sep 17 00:00:00 2001 +From: Jason Kridner j...@ti.com +Date: Sun, 18 Sep 2011 12:16:31 -0400 +Subject: [PATCH 1/3] HACK: beagleboard: config: disable cache for USB + +There is currently a bug in the USB code for the BeagleBoard that is +worked-around by disabling the cache. + +See http://comments.gmane.org/gmane.comp.boot-loaders.u-boot/108224 + +Signed-off-by: Jason Kridner j...@ti.com +--- + include/configs/omap3_beagle.h |5 + + 1 files changed, 5 insertions(+), 0 deletions(-) + +diff --git a/include/configs/omap3_beagle.h b/include/configs/omap3_beagle.h +index 1369c89..8a84d7a 100644 +--- a/include/configs/omap3_beagle.h b/include/configs/omap3_beagle.h +@@ -36,6 +36,10 @@ + #define CONFIG_OMAP34301/* which is in a 3430 */ + #define CONFIG_OMAP3_BEAGLE1/* working with BEAGLE */ + ++/* TODO: WORK-AROUND for bug in BeagleBoard-specific USB */ ++#define CONFIG_SYS_ICACHE_OFF ++#define CONFIG_SYS_DCACHE_OFF ++ + #define CONFIG_SDRC/* The chip has SDRC controller */ + + #include asm/arch/cpu.h/* get chip and board defs */ +-- +1.7.4.1 + diff --git a/recipes-bsp/u-boot/u-boot/2011.09/0002-beagleboard-config-enable-gpio-command.patch b/recipes-bsp/u-boot/u-boot/2011.09/0002-beagleboard-config-enable-gpio-command.patch new file mode 100644 index 000..096a1ce --- /dev/null +++ b/recipes-bsp/u-boot/u-boot/2011.09/0002-beagleboard-config-enable-gpio-command.patch @@ -0,0 +1,25 @@ +From 79e8280783d445f7630b8a9830f8db73f2e04828 Mon Sep 17 00:00:00 2001 +From: Jason Kridner j...@ti.com +Date: Tue, 6 Sep 2011 18:56:11 -0400 +Subject: [PATCH 2/3] beagleboard: config: enable gpio command + +Now that we are using the generic GPIO framework, enable the command. +--- + include/configs/omap3_beagle.h |1 + + 1 files changed, 1 insertions(+), 0 deletions(-) + +diff --git a/include/configs/omap3_beagle.h b/include/configs/omap3_beagle.h +index 8a84d7a..43dc94a 100644 +--- a/include/configs/omap3_beagle.h b/include/configs/omap3_beagle.h +@@ -169,6 +169,7 @@ + #define CONFIG_CMD_PING + #define CONFIG_CMD_DHCP + #define CONFIG_CMD_SETEXPR/* Evaluate expressions*/ ++#define CONFIG_CMD_GPIO + + #undef CONFIG_CMD_FLASH/* flinfo, erase, protect*/ + #undef CONFIG_CMD_FPGA/* FPGA configuration Support*/ +-- +1.7.4.1 + diff --git a/recipes-bsp/u-boot/u-boot/2011.09/0003-Increased-some-timeout-durations-for-MMC-and-EHCI.patch b/recipes-bsp/u-boot/u-boot/2011.09/0003-Increased-some-timeout-durations-for-MMC-and-EHCI.patch new file mode 100644 index 000..c3ebf1b --- /dev/null +++ b/recipes-bsp/u-boot/u-boot/2011.09/0003-Increased-some-timeout-durations-for-MMC-and-EHCI.patch @@ -0,0 +1,39 @@ +From
Re: [Angstrom-devel] [beagleboard] Re: [PATCH] beagleboard images: Initial recipes for BeagleBoard release images
If we put it in meta-angstrom I'd like to avoid using 'machine' names in image
titles.
Op 23 sep. 2011 om 19:10 heeft Jason Kridner jkrid...@beagleboard.org het
volgende geschreven:
On Fri, Sep 23, 2011 at 12:42 PM, Joel A Fernandes agnel.j...@gmail.com
wrote:
Hi,
Can this patch be applied please? If not, can a conclusion be made on
where this recipe should go?
Koen, please apply it where you see fit (if it is suitable) and we can
discuss in Dallas about if there should be multiple layers in the
meta-ti repo to separate BSP from integration/demo. I think this
stuff needs to go into a non-TI layer (perhaps a beagleboard layer),
but we can move it out of meta-ti when another repo exists and we
agree on its role. I think the TI bits should only be for the BSP or
the official TI SDK, but I know I need to learn a lot more about the
best ways to keep TI in alignment with non-TI developers.
I would vote for meta-angstrom (same as original patch). If everyone
is agreement, please apply this patch so that I could make a normal
BeagleBoard image release instead of a pre-release with a modified
layers.txt pointing to my tree.
Thanks,
Joel
On Wed, Sep 7, 2011 at 10:26 PM, Fernandes, Joel A joelag...@ti.com wrote:
These recipes are used to build release images for the BeagleBoard
community using the sdcard_image class in meta-ti
Signed-off-by: Joel A Fernandes joelag...@ti.com
---
recipes-angstrom/images/beagleboard-gnome-image.bb | 14
recipes-angstrom/images/beagleboard-image.bb | 34
2 files changed, 48 insertions(+), 0 deletions(-)
create mode 100644 recipes-angstrom/images/beagleboard-gnome-image.bb
create mode 100644 recipes-angstrom/images/beagleboard-image.bb
diff --git a/recipes-angstrom/images/beagleboard-gnome-image.bb
b/recipes-angstrom/images/beagleboard-gnome-image.bb
new file mode 100644
index 000..ff7d225
--- /dev/null
+++ b/recipes-angstrom/images/beagleboard-gnome-image.bb
@@ -0,0 +1,14 @@
+require beagleboard-image.bb
+
+PR = r2
+
+IMAGE_INSTALL += \
+ angstrom-task-gnome \
+ task-xserver \
+ vim \
+ alsa-tools \
+ alsa-utils \
+
+
+export IMAGE_BASENAME = beagleboard-gnome-image
+
diff --git a/recipes-angstrom/images/beagleboard-image.bb
b/recipes-angstrom/images/beagleboard-image.bb
new file mode 100644
index 000..319cf8b
--- /dev/null
+++ b/recipes-angstrom/images/beagleboard-image.bb
@@ -0,0 +1,34 @@
+LICENSE = MIT
+LIC_FILES_CHKSUM =
file://${COREBASE}/LICENSE;md5=3f40d7994397109285ec7b81fdeb3b58
+
+IMAGE_PREPROCESS_COMMAND = rootfs_update_timestamp
+
+IMAGE_INSTALL += \
+ angstrom-task-boot \
+ angstrom-zeroconf-audio \
+ rsyslog \
+ dropbear-systemd openssh-sftp \
+ e2fsprogs-e2fsck e2fsprogs-blkid \
+ avahi-daemon avahi-utils avahi-systemd \
+ ${CONMANPKGS} \
+ systemd-compat-units \
+ cpufrequtils \
+ beagleboard-test-scripts \
+ gstreamer-ti \
+ ti-dmai-apps \
+ u-boot \
+ x-load \
+htop \
+
+
+CONMANPKGS = connman connman-plugin-loopback connman-plugin-ethernet
connman-plugin-wifi connman-systemd
+CONMANPKGS_libc-uclibc =
+
+IMAGE_DEV_MANAGER = udev
+IMAGE_INITSCRIPTS =
+IMAGE_INIT_MANAGER = systemd
+IMAGE_LOGIN_MANAGER = tinylogin shadow
+
+export IMAGE_BASENAME = beagleboard-image
+
+inherit sdcard_image
--
1.7.0.4
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
--
You received this message because you are subscribed to the Google Groups
Beagle Board group.
To post to this group, send email to beaglebo...@googlegroups.com.
To unsubscribe from this group, send email to
beagleboard+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/beagleboard?hl=en.
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Poor write speed to USB-Stick on beagleboard
Op 21 sep. 2011, om 11:33 heeft Hauser, Wolfgang (external) het volgende geschreven: Hello, we imagined a poor speed while writing to USB-Sticks (USB 2.0) on BeagleboardxM (OMAP3570). Reading from the same Devices has the expected speed. We use the linux-omap-psp-2.6.32 Kernel with an Angstrom based Linux system from Openembedded 2011.03-maintenance. Have someone imagined this behavior too? Is there a solution ? How did you measure the speed? Mount options play a big part in perceived speed, but it could also be a generic omap ehci bug. ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] kernel config
Op 21 sep. 2011, om 12:03 heeft Andrew Holt het volgende geschreven: Hi, Thanks Gary that’s just what I was looking for. On a related note I notice that when I build Angstrom it downloads, patches and builds u-boot. I have a question that relates to other packages too. I want to modify the config for u-boot, enabling some commands exposing certain functions to loadable ‘stand alone’ modules. I may also want to adjust the applets that are included in busybox. Is there a workflow defined for performing changes like this ? what is the safest and most compatible (with the “Angstrom way”) method ? Have a look at http://www.angstrom-distribution.org/ especially the news item below the hx4700 picture ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] [meta-angstrom] angstrom-2010: prefer busybox 1.18.5
Op 9 sep. 2011, om 10:00 heeft Eric Bénard het volgende geschreven:
now that openembedded-core is updated
Signed-off-by: Eric Bénard e...@eukrea.com
---
.../include/angstrom-2010-preferred-versions.inc |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/conf/distro/include/angstrom-2010-preferred-versions.inc
b/conf/distro/include/angstrom-2010-preferred-versions.inc
index 05a1f4c..312233c 100644
--- a/conf/distro/include/angstrom-2010-preferred-versions.inc
+++ b/conf/distro/include/angstrom-2010-preferred-versions.inc
@@ -11,7 +11,7 @@ require
conf/distro/include/angstrom-codec-engine-${CE_VERSION}-preferred-versio
# Needs updating to the latest meta-oe
#require conf/distro/include/preferred-xorg-versions-live.inc
-PREFERRED_VERSION_busybox= 1.18.4
+PREFERRED_VERSION_busybox= 1.18.5
PREFERRED_VERSION_cairo = 1.10.2
PREFFERED_VERSION_connman = 0.76
PREFERRED_VERSION_dropbear = 0.52
This was solved by removing the busybox entries.
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] [PATCH v2 meta-angstrom] gnome: Add gedit to angstrom-task-gnome
I did this slightly different:
http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-angstrom/commit/?id=21316afa9bcfc7d49b8d39828373d126637cb0e5
Op 20 sep. 2011, om 05:03 heeft Joel A Fernandes het volgende geschreven:
Signed-off-by: Joel A Fernandes joelag...@ti.com
---
v2 changes: Bumped PR
recipes-angstrom/tasks/angstrom-task-gnome.bb |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/recipes-angstrom/tasks/angstrom-task-gnome.bb
b/recipes-angstrom/tasks/angstrom-task-gnome.bb
index a2f9fae..3fdde2e 100644
--- a/recipes-angstrom/tasks/angstrom-task-gnome.bb
+++ b/recipes-angstrom/tasks/angstrom-task-gnome.bb
@@ -2,7 +2,7 @@ DESCRIPTION = Task for a GNOME based image
LICENSE = MIT
LIC_FILES_CHKSUM =
file://${COREBASE}/LICENSE;md5=3f40d7994397109285ec7b81fdeb3b58
-PR = r9
+PR = r10
inherit task
@@ -41,6 +41,7 @@ RDEPENDS_task-gnome = \
gpe-scap \
bash \
tzdata \
+ gedit \
RRECOMMENDS_task-gnome = ofono
--
1.7.0.4
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] [PATCH v2 meta-ti] u-boot: added version 2011.09-rc1
Thanks, applied Op 20 sep. 2011, om 05:32 heeft Joel A Fernandes het volgende geschreven: From: Jason Kridner j...@ti.com There is a v2011.09 tag on the mainline, but I haven't seen a release notice go out. It didn't make sense to me to try to carry-forward those all patches since the release tag, so I simply picked the latest tag in the maineline. Patched and tested on BeagleBoard-xM revision C. USB Ethernet was tested with: setenv usbethaddr de:ad:be:ef:00:01 usb start dhcp^C setenv ipaddr 10.0.1.2 ping 10.0.1.1 USB Storage was tested with: above usb part fatls usb 0 led command was tested with: led all off led all on led 1 on led 1 off gpio command tested with: gpio input 4 hold USER button gpio input 4 release USER button Also performed boot test. Signed-off-by: Jason Kridner j...@ti.com Signed-off-by: Joel A Fernandes joelag...@ti.com --- v2 changes: * Dropped PV * Leave L2 cache enabled ...-beagleboard-config-disable-cache-for-USB.patch | 33 + ...02-beagleboard-config-enable-gpio-command.patch | 25 + ...d-some-timeout-durations-for-MMC-and-EHCI.patch | 39 recipes-bsp/u-boot/u-boot_2011.09.bb | 21 +++ 4 files changed, 118 insertions(+), 0 deletions(-) create mode 100644 recipes-bsp/u-boot/u-boot/2011.09/0001-HACK-beagleboard-config-disable-cache-for-USB.patch create mode 100644 recipes-bsp/u-boot/u-boot/2011.09/0002-beagleboard-config-enable-gpio-command.patch create mode 100644 recipes-bsp/u-boot/u-boot/2011.09/0003-Increased-some-timeout-durations-for-MMC-and-EHCI.patch create mode 100644 recipes-bsp/u-boot/u-boot_2011.09.bb diff --git a/recipes-bsp/u-boot/u-boot/2011.09/0001-HACK-beagleboard-config-disable-cache-for-USB.patch b/recipes-bsp/u-boot/u-boot/2011.09/0001-HACK-beagleboard-config-disable-cache-for-USB.patch new file mode 100644 index 000..a2776e9 --- /dev/null +++ b/recipes-bsp/u-boot/u-boot/2011.09/0001-HACK-beagleboard-config-disable-cache-for-USB.patch @@ -0,0 +1,33 @@ +From 03b9bca863257cb24d8f11bb773ad2b8dff820c6 Mon Sep 17 00:00:00 2001 +From: Jason Kridner j...@ti.com +Date: Sun, 18 Sep 2011 12:16:31 -0400 +Subject: [PATCH 1/3] HACK: beagleboard: config: disable cache for USB + +There is currently a bug in the USB code for the BeagleBoard that is +worked-around by disabling the cache. + +See http://comments.gmane.org/gmane.comp.boot-loaders.u-boot/108224 + +Signed-off-by: Jason Kridner j...@ti.com +--- + include/configs/omap3_beagle.h |5 + + 1 files changed, 5 insertions(+), 0 deletions(-) + +diff --git a/include/configs/omap3_beagle.h b/include/configs/omap3_beagle.h +index 1369c89..8a84d7a 100644 +--- a/include/configs/omap3_beagle.h b/include/configs/omap3_beagle.h +@@ -36,6 +36,10 @@ + #define CONFIG_OMAP3430 1 /* which is in a 3430 */ + #define CONFIG_OMAP3_BEAGLE 1 /* working with BEAGLE */ + ++/* TODO: WORK-AROUND for bug in BeagleBoard-specific USB */ ++#define CONFIG_SYS_ICACHE_OFF ++#define CONFIG_SYS_DCACHE_OFF ++ + #define CONFIG_SDRC /* The chip has SDRC controller */ + + #include asm/arch/cpu.h /* get chip and board defs */ +-- +1.7.4.1 + diff --git a/recipes-bsp/u-boot/u-boot/2011.09/0002-beagleboard-config-enable-gpio-command.patch b/recipes-bsp/u-boot/u-boot/2011.09/0002-beagleboard-config-enable-gpio-command.patch new file mode 100644 index 000..096a1ce --- /dev/null +++ b/recipes-bsp/u-boot/u-boot/2011.09/0002-beagleboard-config-enable-gpio-command.patch @@ -0,0 +1,25 @@ +From 79e8280783d445f7630b8a9830f8db73f2e04828 Mon Sep 17 00:00:00 2001 +From: Jason Kridner j...@ti.com +Date: Tue, 6 Sep 2011 18:56:11 -0400 +Subject: [PATCH 2/3] beagleboard: config: enable gpio command + +Now that we are using the generic GPIO framework, enable the command. +--- + include/configs/omap3_beagle.h |1 + + 1 files changed, 1 insertions(+), 0 deletions(-) + +diff --git a/include/configs/omap3_beagle.h b/include/configs/omap3_beagle.h +index 8a84d7a..43dc94a 100644 +--- a/include/configs/omap3_beagle.h b/include/configs/omap3_beagle.h +@@ -169,6 +169,7 @@ + #define CONFIG_CMD_PING + #define CONFIG_CMD_DHCP + #define CONFIG_CMD_SETEXPR /* Evaluate expressions */ ++#define CONFIG_CMD_GPIO + + #undef CONFIG_CMD_FLASH /* flinfo, erase, protect */ + #undef CONFIG_CMD_FPGA /* FPGA configuration Support */ +-- +1.7.4.1 + diff --git a/recipes-bsp/u-boot/u-boot/2011.09/0003-Increased-some-timeout-durations-for-MMC-and-EHCI.patch b/recipes-bsp/u-boot/u-boot/2011.09/0003-Increased-some-timeout-durations-for-MMC-and-EHCI.patch new file mode 100644 index 000..c3ebf1b --- /dev/null +++ b/recipes-bsp/u-boot/u-boot/2011.09/0003-Increased-some-timeout-durations-for-MMC-and-EHCI.patch @@ -0,0 +1,39 @@ +From
Re: [Angstrom-devel] [PATCH 1/2] .gitignore: unignore sources/layers.txt
Op 8 sep. 2011, om 12:58 heeft Dmitry Eremin-Solenikov het volgende geschreven: Explicitly unignore sources/layers.txt in .gitignre to let git know that we care about that file. E.g. this fixes problems when merging that file after a git commit or a git stash pop. Signed-off-by: Dmitry Eremin-Solenikov dbarysh...@gmail.com It took a while, but it's in now, thanks! ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] [beagleboard] [PATCH v2 meta-ti] linux-3.0: use die-id for BeagleBoard-xM eth mac
Op 16 sep. 2011, om 21:08 heeft Jason Kridner het volgende geschreven: The following changes since commit c6251231c603256eff6ccd0181c20bb182f9e03b: gstreamer-ti: use MEMARGS variable instead of hardcoding omap3 config (2011-09-16 16:04:42 +0200) are available in the git repository at: git://github.com/jadonk/meta-texasinstruments.git for-koen Jason Kridner (1): [meta-ti] linux-3.0: use die-id for BeagleBoard-xM eth mac ...e-add-support-for-beagleboard-xM-revision.patch |6 +- ...OMAP3-beagle-add-support-for-expansionboa.patch |6 +- ...0003-HACK-OMAP3-beagle-switch-to-GPTIMER1.patch |6 +- .../0004-OMAP3-beagle-HACK-add-in-1GHz-OPP.patch |6 +- ...5-omap3-Add-basic-support-for-720MHz-part.patch |6 +- ...Set-dto-to-max-value-of-14-to-avoid-SD-Ca.patch | 33 ...add-cpu-id-register-to-MAC-address-helper.patch | 89 ++ ...BeagleBoard-Fix-up-random-or-missing-MAC-.patch | 156 ++ ...3630-PRM-add-ABB-PRM-register-definitions.patch |4 +- ...P3-PM-VP-generalize-PRM-interrupt-helpers.patch |4 +- ...P3-PRM-add-tranxdone-IRQ-handlers-for-ABB.patch |4 +- ...P3-ABB-Adaptive-Body-Bias-structures-data.patch |4 +- ...-OMAP3-OPP-add-ABB-data-to-voltage-tables.patch |4 +- ...3-Voltage-add-ABB-data-to-voltage-domains.patch |4 +- ...3-ABB-initialization-transition-functions.patch |4 +- ...-OMAP3-Voltage-add-ABB-to-voltage-scaling.patch |4 +- ...01-Enabling-Hwmon-driver-for-twl4030-madc.patch |4 +- .../madc/0002-mfd-twl-core-enable-madc-clock.patch |4 +- ...nking-error-in-twl-common.c-for-OMAP2-3-4.patch |4 +- ...-introduce-function-to-free-cpufreq-table.patch |6 +- ...q-ensure-driver-initializes-after-cpufreq.patch |4 +- ...PUfreq-ensure-policy-is-fully-initialized.patch |4 +- .../0004-OMAP3-PM-CPUFreq-driver-for-OMAP3.patch |4 +- ...AP-PM-CPUFREQ-Fix-conditional-compilation.patch |4 +- ...-cpufreq-fixup-after-new-OPP-layer-merged.patch |4 +- ...q-Split-OMAP1-and-OMAP2PLUS-CPUfreq-drive.patch |4 +- ...cpufreq-Add-SMP-support-to-cater-OMAP4430.patch |4 +- ...pufreq-Fix-typo-when-attempting-to-set-mp.patch |4 +- ...P2-cpufreq-move-clk-name-decision-to-init.patch |4 +- ...-cpufreq-deny-initialization-if-no-mpudev.patch |4 +- ...012-OMAP2-cpufreq-dont-support-freq_table.patch |4 +- ...3-OMAP2-cpufreq-only-supports-OPP-library.patch |4 +- ...-OMAP2-cpufreq-put-clk-if-cpu_init-failed.patch |4 +- .../0015-OMAP2-cpufreq-fix-freq_table-leak.patch |4 +- ...eq-Remove-superfluous-check-in-target-for.patch |4 +- ...ufreq-notify-even-with-bad-boot-frequency.patch |4 +- ...req-Enable-all-CPUs-in-shared-policy-mask.patch |4 +- ...eq-update-lpj-with-reference-value-to-avo.patch |4 +- ...egulator-supply-definitions-in-mach-omap2.patch |4 +- ...style-supply.dev-assignments-common-in-hs.patch |4 +- ...parate-init_irq-functions-to-avoid-cpu_is.patch |6 +- ...parate-timer-init-functions-to-avoid-cpu_.patch |8 +- ...05-omap-Move-dmtimer-defines-to-dmtimer.h.patch |4 +- ...-subset-of-dmtimer-functions-into-inline-.patch |4 +- ...7-omap2-Use-dmtimer-macros-for-clockevent.patch |4 +- .../0008-omap2-Remove-gptimer_wakeup-for-now.patch |4 +- ...OMAP3-SR-make-notify-independent-of-class.patch |4 +- ...010-OMAP3-SR-disable-interrupt-by-default.patch |4 +- ...1-OMAP3-SR-enable-disable-SR-only-on-need.patch |4 +- .../0012-OMAP3-SR-fix-cosmetic-indentation.patch |4 +- ...ve-clocksource-and-timesource-and-initial.patch |4 +- ...-omap2-Use-dmtimer-macros-for-clocksource.patch |4 +- ...p2-Remove-omap2_gp_clockevent_set_gptimer.patch |4 +- ...e-timer-gp.c-into-timer.c-to-combine-time.patch |4 +- .../0017-omap-cleanup-NAND-platform-data.patch |4 +- ...omap-board-omap3evm-Fix-compilation-error.patch |4 +- .../0019-omap-mcbsp-Drop-SPI-mode-support.patch|4 +- ...map-mcbsp-Drop-in-driver-transfer-support.patch |4 +- .../voltdm/0021-omap2-fix-build-regression.patch |4 +- ...w-twl-common-for-common-TWL-configuration.patch |6 +- ...common-twl6030-configuration-to-twl-commo.patch |4 +- ...ve-common-twl-configuration-to-twl-common.patch |4 +- ...common-regulator-configuration-to-twl-com.patch |4 +- ...mcbsp-Remove-rx_-tx_word_length-variables.patch |4 +- .../0027-omap-mcbsp-Remove-port-number-enums.patch |4 +- .../0028-OMAP-dmtimer-add-missing-include.patch|4 +- ...P2-hwmod-Fix-smart-standby-wakeup-support.patch |4 +- ...4-hwmod-data-Add-MSTANDBY_SMART_WKUP-flag.patch |4 +- ...-Enable-module-in-shutdown-to-access-sysc.patch |4 +- ...-Do-not-write-the-enawakeup-bit-if-SYSC_H.patch |4 +- ...wmod-Remove-_populate_mpu_rt_base-warning.patch |4 +- ...4-OMAP2-hwmod-Fix-the-HW-reset-management.patch |4 +- ...-OMAP-hwmod-Add-warnings-if-enable-failed.patch |4 +-
Re: [Angstrom-devel] Koen Kooi : layers: add meta-handheld to fetchable layers
patches welcome Op 6 sep. 2011, om 16:43 heeft Andrea Adami het volgende geschreven: thanks, please note today the layer was finally pushed in OE. Repository: http://cgit.openembedded.org/cgit.cgi/meta-handheld/ Please update, TIA Andrea ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Narcissus and device nodes
Op 29 aug. 2011, om 15:36 heeft Joel A Fernandes het volgende geschreven: Doesn't Narcissus suffer from mknod errors as the following is run as non-root? http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/narcissus/tree/scripts/assemble-image.sh#n147 If so, what are the effects of not being able to create device nodes in an image and, does udev auto create them during startup? The kernel creates them for you: root@beagleboard:~# zcat /proc/config.gz | grep DEVTMP CONFIG_DEVTMPFS=y CONFIG_DEVTMPFS_MOUNT=y Is it ok to skip the tar stage and directly copy what's in TARGET_DIR into the fs loopback mount? It seems that, since tar -x is run as non-root anyway, then tarring and untarring is as good as copying in files directly. This would save a stage if a tar is not a desired output (for ex. just an sdcard image is desired) It serves as a sanity test for the tar code ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
[Angstrom-devel] Suggestions for narcissus rewrite
Hi, There are plans to make a rewrite of narcissus (echo) to move more of the processing to javascript (less php and shell). So before starting that, what changes would you like to see? And more importantly, do you want to help out making those changes? regards, Koen ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Suggestions for narcissus rewrite
I'm responding to this specific point now, will address the others later in a seperate mail. Op 30 aug. 2011, om 09:55 heeft Paul Eggleton het volgende geschreven: * Have a closer link to the actual package building on the backend (BitBake), so anyone can see when the last set of packages were built or if there is a build currently in progress. The problem is that narcissus knows nothing about bitbake, it's just a fancy way of 'opkg update ; opkg install foo'. If we continue with that model, we have the following to work with: 1) /etc/angstrom-version: root@beagleboard:~# cat /etc/angstrom-version Angstrom v2011.08-core (Core edition) Built from branch: master Revision: 4816116d9c08c82e38dc5d95a170e2904bfe3786 [1] Target system: arm-angstrom-linux-gnueabi 2) Opkg metadata: koen@dominion:/OE/angstrom-v2011/build/tmp-angstrom-v2011/deploy/eglibc$ dpkg-deb -I ipk/armv7a/libav_0.6.2+r0.2+gitr0+c6c2dfcf15c1d93b2189adff6f71c5c4b6b05338-r0.2.9_armv7a.ipk | grep -e OE -e Build OE: libav Build: org.openembedded.dev/d5e59ef So after building the image we can extract the buildrevs and recipe name for each package[2] and when the last image build was done for said machine. That is pretty much there already: http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/narcissus/tree/scripts/assemble-image.sh#n291 Now, suppose we break with the 'opkg update ; opkg install foo' model and start leveraging sstate we can have a 'toplevel' thing that manages both narcissus options (read: package checkboxes) and autobuilder config (read: list of recipes to build): 1) have an autobuilder build the machine x packages set daily and store info (success, revisions, etc) into a shared db 2) make narcissus pull info from that db when presenting the options. As more hardware becomes available we could even have narcissus add the build to a workqueue for the autobuilder directly. This needs to be considered carefully, since the plain 'opkg install' method is already eating a big chunk of IO. The Oregon instance of narcissus is already using an SSD for the workdir since a spinning disk was too slow for the workload. Have a look at the last 30 days: http://narcissus.angstrom-distribution.org/graph.php?timeframe=30 or the past year for beagleboard: http://narcissus.angstrom-distribution.org/graph.php?timeframe=365machine=beagleboard The images aren't small either: 20110830 06:07:51 akita95M 20110830 07:12:51 beagleboard 30M 20110830 07:40:10 beagleboard 692M 20110830 07:41:26 beagleboard 8.6M 20110830 07:44:43 dm355-leopard31M 20110830 07:49:13 beagleboard 35M 20110830 07:52:26 beagleboard 30M 20110830 07:58:57 beagleboard 322M 20110830 07:59:54 omap3evm 456M 20110830 08:15:41 at91sam9263ek32M 20110830 08:32:13 h220093M 20110830 08:51:20 beagleboard 13M 20110830 08:56:02 beagleboard 258M 20110830 09:02:20 beagleboard 48M With all this info being known and the fact that narcissus will run parallel to echo for the time being, what design should we choose? regards, Koen [1] That rev doesn't exist upstream, the autobuilder has extra patches applied to oe-core (e.g. gst-plugin renaming). This is a seperate problem that needs addressing. [2] in .dev builds, OE-core doesn't have that yet: commit 6ae45bbf2b5ca9e4fd7e8b04e461f0bf120dd44d Author: Koen Kooi koen.k...@gmail.com Date: Tue Dec 21 18:06:06 2010 + package ipk bbclass: store build branch and revision in ipkg metadata The ipkg metadata will look like this now: koen@dominion:/OE/angstrom-dev/deploy/glibc$ dpkg-deb -I ipk/am3517-evm/matrix-gui_1.3-r19.0.6_am3517-evm.ipk new debian package, version 2.0. size 24112 bytes: control archive= 540 bytes. 629 bytes,13 lines control Package: matrix-gui Version: 1.3-r19.0.6 Description: Matrix GUI for Qt X11 Section: multimedia Priority: optional Maintainer: Angstrom Developers angstrom-distro-devel@linuxtogo.org License: BSD Architecture: am3517-evm OE: matrix-gui Homepage: https://gforge.ti.com/gf/project/matrix_gui/ Build: org.openembedded.dev/f35ab2d Depends: matrix-gui-common, libpng12-0, libfreetype6, libz1, libgthread-2.0-0, libqtwebkit4, libphonon4, libqtdbus4, libqtxml4, libqtgui4, libqtnetwork4, libqtcore4, libglib-2.0-0, libc6, libstdc++6, libgcc1 Source: svn://gforge.ti.com/svn/matrix_gui/;module=trunk;proto=https;user=anonymous;pswd='' koen@dominion:/OE/angstrom-dev/deploy/glibc$ Signed-off-by: Koen Kooi k...@openembedded.org Acked-by: Martin Jansa martin.ja...@gmail.com Acked-by: Chase Maupin chase.mau...@ti.com ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Suggestions for narcissus rewrite
Op 30 aug. 2011, om 11:39 heeft Paul Eggleton het volgende geschreven:
Koen Kooi wrote:
Op 30 aug. 2011, om 09:55 heeft Paul Eggleton het volgende geschreven:
* Have a closer link to the actual package building on the backend
(BitBake), so anyone can see when the last set of packages were built or
if there is a build currently in progress.
The problem is that narcissus knows nothing about bitbake, it's just a
fancy way of 'opkg update ; opkg install foo'.
Yes, and I'm not necessarily suggesting a deviation from that. I figured
assuming that continues to be the model, it might still be nice to get
some more visibility into the actual build process, but no control over it
from the web interface.
If we continue with that
model, we have the following to work with:
1) /etc/angstrom-version:
root@beagleboard:~# cat /etc/angstrom-version
Angstrom v2011.08-core (Core edition)
Built from branch: master
Revision: 4816116d9c08c82e38dc5d95a170e2904bfe3786 [1]
Target system: arm-angstrom-linux-gnueabi
BTW will this revision information be expanded for the OE-core model of
multiple metadata repos? Might be ugly but it seems to me the single
revision isn't as useful as it was previously.
The angstrom-version recipe does this:
do_install() {
install -d ${D}${sysconfdir}
echo Angstrom ${DISTRO_VERSION} (Core edition)
${D}${sysconfdir}/angstrom-version
echo Built from branch: ${METADATA_BRANCH}
${D}${sysconfdir}/angstrom-version
echo Revision: ${METADATA_REVISION} ${D}${sysconfdir}/angstrom-version
echo Target system: ${TARGET_SYS} ${D}${sysconfdir}/angstrom-version
echo NAME=Angstrom ${D}${sysconfdir}/os-release
echo ID=angstrom ${D}${sysconfdir}/os-release
echo PRETTY_NAME=The Ångström Distribution ${D}${sysconfdir}/os-release
echo ANSI_COLOR=1;35 ${D}${sysconfdir}/os-release
install -d ${D}${bindir}
install -m 0755 ${WORKDIR}/lsb_release ${D}${bindir}/
}
So if METADATA_* becomes more usefull, angstrom-version becomes more usefull :)
Slightly off-topic: maybe we should try to standardize /etc/distro-release in
the OE-core universe, like systemd is standardizing /etc/os-release.
Now, suppose we break with the 'opkg update ; opkg install foo' model and
start leveraging sstate we can have a 'toplevel' thing that manages both
narcissus options (read: package checkboxes) and autobuilder config (read:
list of recipes to build):
1) have an autobuilder build the machine x packages set daily and store
info (success, revisions, etc) into a shared db
2) make narcissus pull info from that db when presenting the options.
As more hardware becomes available we could even have narcissus add the
build to a workqueue for the autobuilder directly. This needs to be
considered carefully, since the plain 'opkg install' method is already
eating a big chunk of IO. The Oregon instance of narcissus is already
using an SSD for the workdir since a spinning disk was too slow for the
workload. Have a look at the last 30 days:
http://narcissus.angstrom-distribution.org/graph.php?timeframe=30
or the past year for beagleboard:
http://narcissus.angstrom-distribution.org/graph.php?timeframe=365machine=beagleboard
The images aren't small either:
20110830 06:07:51 akita95M
20110830 07:12:51 beagleboard 30M
20110830 07:40:10 beagleboard 692M
20110830 07:41:26 beagleboard 8.6M
20110830 07:44:43 dm355-leopard31M
20110830 07:49:13 beagleboard 35M
20110830 07:52:26 beagleboard 30M
20110830 07:58:57 beagleboard 322M
20110830 07:59:54 omap3evm 456M
20110830 08:15:41 at91sam9263ek32M
20110830 08:32:13 h220093M
20110830 08:51:20 beagleboard 13M
20110830 08:56:02 beagleboard 258M
20110830 09:02:20 beagleboard 48M
With all this info being known and the fact that narcissus will run
parallel to echo for the time being, what design should we choose?
Well, one thing to consider as well is that it's very likely at some point
in the near future that we will be writing a BitBake web-UI within the
Yocto Project, and although it has not been designed yet I would expect
that to be along similar lines to the hob GTK2+-based UI, at least in
terms of the options it allows the user to change. The question is though,
in a distro like Angstrom where you've specified quite a lot of policy
(preferred versions, features, etc.) that you wouldn't necessarily want to
allow the user to configure, does a UI at the BitBake level make sense?
From what I've seem 'hob' hides pretty much everything as well so a web
version of it would be suitable as a narcissus replacement. I will postulate
that people using 'hob' or narcissus aren't distro developers and just want to
get a rootfs with their set of features. The feedback I get about narcisuss'
simple mode is that it has too many choices already :)
regards,
Koen
___
Angstrom-distro
Re: [Angstrom-devel] [PATCH] angstrom-2010: bump glibmm version to 2.28.2
All 3 patches are in (the setupscripts one got squashed due Mail.app and git disagreeing about seperators), thanks! Op 15 aug. 2011, om 17:57 heeft Dmitry Eremin-Solenikov het volgende geschreven: glibmm 2.24.0 isn't provided anymore, which results in the following messages: NOTE: preferred version 2.24.0 of glibmm not available (for item glibmm) NOTE: versions of glibmm available: 2.28.2 NOTE: preferred version 2.24.0 of glibmm not available (for item glibmm-dev) NOTE: versions of glibmm available: 2.28.2 NOTE: preferred version 2.24.0 of glibmm not available (for item glibmm) NOTE: versions of glibmm available: 2.28.2 Signed-off-by: Dmitry Eremin-Solenikov dbarysh...@gmail.com --- .../include/angstrom-2010-preferred-versions.inc |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/conf/distro/include/angstrom-2010-preferred-versions.inc b/conf/distro/include/angstrom-2010-preferred-versions.inc index 5847732..05a1f4c 100644 --- a/conf/distro/include/angstrom-2010-preferred-versions.inc +++ b/conf/distro/include/angstrom-2010-preferred-versions.inc @@ -18,7 +18,7 @@ PREFERRED_VERSION_dropbear = 0.52 PREFERRED_VERSION_fontconfig = 2.8.0 PREFERRED_VERSION_glib-2.0= 2.28.8 PREFERRED_VERSION_glib-2.0-native = 2.28.8 -PREFERRED_VERSION_glibmm = 2.24.0 +PREFERRED_VERSION_glibmm = 2.28.2 PREFERRED_VERSION_gobject-introspection-native = 0.9.10 PREFERRED_VERSION_gst-pulse = 0.9.7 PREFERRED_VERSION_gtkmm = 2.20.0 -- 1.7.2.5 ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Simple recipe
Op 12 aug. 2011, om 10:25 heeft Andrew Holt het volgende geschreven: Hi, I new to Openembeded Angstrom so this may be a straightforward question. I am building an image for a Beagleboard (rev C4). I want the simplest, smallest viable image I can get, as a starting pint for further additions. No gnome, no X just a simple tty login to the serial port, with busy box, networking, opkg. Does a bitbake recipe for this already exist ? if so what is it called ? If its not in the standard distribution can somebody mail it to me please ? 'console-image' is basically that. ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Toolchain roadmap for Angstrom-core
Op 9 aug. 2011, om 17:29 heeft Khem Raj het volgende geschreven: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/09/2011 01:38 AM, Koen Kooi wrote: Hi, For angstrom-core we currently have the following configs: 2011.x: gcc: 4.5.x binutils: 2.20.x eglibc: 2.12 bleeding: gcc: 4.6.x binutils: 2.21.x eglibc: 2.13 With the october release of OE-core coming up it makes a lot of sense to start thinking of the toolchain roadmap. Do we want to keep the current one and move the bleeding into the master config after the release or do we want to update e.g. eglibc to 2.13 before the release. And better ideas for release names and numbers are appreciated as well. I think. We can use eglibc 2.13 release. Since 2.13 has been tested quite a bit and does not have any radical features it should be relatively safe. I would propose bintutils 2.21.x as well if there is no dependency on 2.20.x anymore but its medium risk 2.21.x breaks with 'old' kernels on armv7a, so I'd like to have the october release work with those and introduce the breakage after that. ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Prolific pl 2303 driver not enabled
Op 28 jul. 2011, om 09:38 heeft Anton Komarov het volgende geschreven: Hi, guys. Got my beagleboard xm and found out that angstrom kernel 2.6.32 misses pl 2303 usb to serial driver support. Have you tried opkg installing it? ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] gstreamer-ti package
Op 27 jul. 2011, om 16:29 heeft Joel A Fernandes het volgende geschreven: On Wed, Jul 27, 2011 at 12:36 AM, Koen Kooi k...@dominion.thruhere.net wrote: Op 26 jul. 2011, om 23:09 heeft Joel A Fernandes het volgende geschreven: Hi, The gstreamer-ti plugin in Narcissus built images appears to have not been rebuilt when we updated the ti-dmai package. As a result gstreamer-ti in these images cannot render to display as it doesn't have the new display fixes. Does the auto-builder not rebuild dependent packages on such updates? for the tl;dr crowd: bump PR if you want a rebuild, longer version below. It only rebuild when versions change, which normally works well enough for shared libs, but for static linking you will need to bump PR manually. You need to do that anyway since a package manager can't sense that the 1.0.2-r2 in the feeds has become different from the 1.0.2-r2 already installed. To further protect from such mismatches the upload script will refuse to upload a .ipk if one with the same name/version/arch is already there. Thanks! I will send a patch to update gstreamer-ti SRCREV to OE then. Is this something we need to do for OE-core too? Why do you need a newer SRCREV? ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] gstreamer-ti package
Op 27 jul. 2011, om 16:38 heeft Joel A Fernandes het volgende geschreven: On Wed, Jul 27, 2011 at 9:30 AM, Koen Kooi k...@dominion.thruhere.net wrote: Op 27 jul. 2011, om 16:29 heeft Joel A Fernandes het volgende geschreven: On Wed, Jul 27, 2011 at 12:36 AM, Koen Kooi k...@dominion.thruhere.net wrote: Op 26 jul. 2011, om 23:09 heeft Joel A Fernandes het volgende geschreven: Hi, The gstreamer-ti plugin in Narcissus built images appears to have not been rebuilt when we updated the ti-dmai package. As a result gstreamer-ti in these images cannot render to display as it doesn't have the new display fixes. Does the auto-builder not rebuild dependent packages on such updates? for the tl;dr crowd: bump PR if you want a rebuild, longer version below. It only rebuild when versions change, which normally works well enough for shared libs, but for static linking you will need to bump PR manually. You need to do that anyway since a package manager can't sense that the 1.0.2-r2 in the feeds has become different from the 1.0.2-r2 already installed. To further protect from such mismatches the upload script will refuse to upload a .ipk if one with the same name/version/arch is already there. Thanks! I will send a patch to update gstreamer-ti SRCREV to OE then. Is this something we need to do for OE-core too? Why do you need a newer SRCREV? Sorry, I meant the PR variable. Like was done yesterday: http://cgit.openembedded.org/cgit.cgi/openembedded/commit/?id=0a6de7caea8a163928297d0562a728f62d1a6fcd ? ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Making angstrom-core the default in the setup scripts
Op 27 jul. 2011, om 19:24 heeft Philip Balister het volgende geschreven: On 07/26/2011 12:35 PM, Paul Eggleton wrote: Paul Menzel wrote: I am still having some concerns I raised in reply to Khem?s message [2] but I am pasting them here again. Will reply to your original message on OE-dev. If someone can point me at a coherent set of instructions for building Angstrom with OE core, I can start to put in some spare cycles. As mentioned before: http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-angstrom/tree/README ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] AM1808
Op 26 jul. 2011, om 12:59 heeft Michael Schnell het volgende geschreven: On 07/19/2011 12:16 PM, Koen Kooi wrote: I tried to update the Distribution via the opkg package manager. Lots of files were downloaded, but when opkg tried to install them I get an error message like too small memory. The board has 32 MB RAM Does it really only have 32M or is that artificially limited by uboot setting mem=32M? I found that mem=32M is given in the Kernel command line. Can this easily be changed (I'm quite new to u-boot) ? Yes, look back a few emails in the thread :) ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] AM1808
Op 21 jul. 2011, om 14:02 heeft Michael Schnell het volgende geschreven: We want to use an LCD display (mainly for development and maintenance). The kit features a socket for the chip's LCD/Video pins. We are going to get an LCD panel to connect to the board or to find a converter that allows connecting some standard monitor. (Question 5) How to configure, use and test the LCD and/or Video output ? No idea on that, sorry. I think that's a question for logicPD. I know that the stock LCD is supported by angstrom out of the box. Just to let you know: The framebuffer driver seems to be in the Kernel as well: cat /proc/fp 0 D8Axx FB Drv Now I need to find some Display to attach to the boards socket. Note that framebuffer and display are 2 completely seperate things. The framebuffer is just a portion of RAM linux will draw into, getting that out onto a display is something else. ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] OE-core based setup instructions page
Op 26 jul. 2011, om 16:24 heeft Paul Eggleton het volgende geschreven: Hi all, It would be nice if we had a setup instructions page for the new OE-core based Angstrom. We have the old page [1] but it makes no reference to OE-core; there's Khem's blog post [2] which would be a good start if Khem is amenable to us copying it. I'm happy to put this together so long as we decide what we want and where we want it. Thoughts? There's a README in the git tree: http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/README is that a start? Cheers, Paul [1] http://www.angstrom-distribution.org/building-angstrom [2] http://sakrah.homelinux.org/blog/2011/03/using-openembedded-core-to-build-angstrom-for-qemu/ - Paul Eggleton Intel Open Source Technology Centre ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] OE-core based setup instructions page
Op 26 jul. 2011, om 17:16 heeft Paul Eggleton het volgende geschreven: Koen Kooi wrote: There's a README in the git tree: http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/README is that a start? Sure, if we could integrate that into the page on the Angstrom website - is now the appropriate time to do that? I kinda tried to start that discussion over here: http://lists.linuxtogo.org/pipermail/angstrom-distro-devel/2011-July/004761.html ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] gstreamer-ti package
Op 26 jul. 2011, om 23:09 heeft Joel A Fernandes het volgende geschreven: Hi, The gstreamer-ti plugin in Narcissus built images appears to have not been rebuilt when we updated the ti-dmai package. As a result gstreamer-ti in these images cannot render to display as it doesn't have the new display fixes. Does the auto-builder not rebuild dependent packages on such updates? for the tl;dr crowd: bump PR if you want a rebuild, longer version below. It only rebuild when versions change, which normally works well enough for shared libs, but for static linking you will need to bump PR manually. You need to do that anyway since a package manager can't sense that the 1.0.2-r2 in the feeds has become different from the 1.0.2-r2 already installed. To further protect from such mismatches the upload script will refuse to upload a .ipk if one with the same name/version/arch is already there. ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] start X server
Op 25 jul. 2011, om 16:47 heeft Paul Menzel het volgende geschreven: Am Montag, den 25.07.2011, 16:34 +0200 schrieb Michael Schnell: Thanks to the help from this forum I finally got the X11 server running. I can start Enlightenment on same and view it with x11vnc. the remote mouse and keyboard works fine even though I did not install any hardware mouse or keyboard driver. It is great to hear that you were successful. Seemingly Xorg -configure does not work, though. I need to manually write /etc/X11/xorg.config. This should be `/etc/X11/xorg.conf`, should not be it? Could you attach the file for others interested in it in the future. And xorg.conf isn't needed anymore, udev autoplugging is doing a nice job nowadays for most platforms ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] start X server
Op 22 jul. 2011, om 11:38 heeft Michael Schnell het volgende geschreven: Hi experts, I found that the OMAP L138 development board by Logic PD I have is equipped with a Kernel that includes a graphics driver for the LCD interface the chip features. I do see: root@da850-omapl138-evm:/dev# ls -l f* lrwxrwxrwx1 root root3 Jan 1 2000 fb - fb0 crw-rw1 root video 29, 0 May 15 14:46 fb0 crw-rw-rw-1 root root 1, 7 May 15 14:46 full Unfortunately right now I don't have an LCD panel yet, so I can't see if the display shows anything. (When X is installed I'll try to use X11vnc to access the FB.) Now I installed the packages xserver-xorg and xserver-kdrive-fbdev You'll need: xserver-xorg xf86-video-fbdev xf86-input-evdev ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] [PATCH] narcissus: Set max LEB count to 4097 to avoid mkfs.ubifs segmentation fault
Op 20 jul 2011, om 23:37 heeft Joel A Fernandes het volgende geschreven: Signed-off-by: Joel A Fernandes agnel.j...@gmail.com --- conf/beagleboard/machine-config |4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/conf/beagleboard/machine-config b/conf/beagleboard/machine-config index 6d44260..f9caa45 100644 --- a/conf/beagleboard/machine-config +++ b/conf/beagleboard/machine-config @@ -1,8 +1,8 @@ EXTRA_IMAGECMD_jffs2=-lnp # UBI: smallest flash I/O unit:2048 # UBI: logical eraseblock size:129024 bytes -# UBI device number 0, total 1996 LEBs -MKUBIFS_ARGS=-m 2048 -e 129024 -c 1996 +# UBI device number 0, total 4097 LEBs +MKUBIFS_ARGS=-m 2048 -e 129024 -c 4097 And how does that work for C4 and earlier? ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] [PATCH] narcissus: Set max LEB count to 4097 to avoid mkfs.ubifs segmentation fault
Op 21 jul. 2011, om 09:23 heeft Joel A Fernandes het volgende geschreven: On Thu, Jul 21, 2011 at 1:14 AM, Koen Kooi k...@dominion.thruhere.net wrote: Op 20 jul 2011, om 23:37 heeft Joel A Fernandes het volgende geschreven: Signed-off-by: Joel A Fernandes agnel.j...@gmail.com --- conf/beagleboard/machine-config |4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/conf/beagleboard/machine-config b/conf/beagleboard/machine-config index 6d44260..f9caa45 100644 --- a/conf/beagleboard/machine-config +++ b/conf/beagleboard/machine-config @@ -1,8 +1,8 @@ EXTRA_IMAGECMD_jffs2=-lnp # UBI: smallest flash I/O unit:2048 # UBI: logical eraseblock size:129024 bytes -# UBI device number 0, total 1996 LEBs -MKUBIFS_ARGS=-m 2048 -e 129024 -c 1996 +# UBI device number 0, total 4097 LEBs +MKUBIFS_ARGS=-m 2048 -e 129024 -c 4097 And how does that work for C4 and earlier? From what I understand, -c specifies the maximum LEB count, so if you meant devices with a smaller NAND, should it matter? I'm pretty sure it matters, have you tested it on e.g. a C4? ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] [oe] [PATCH v2] linux-omap-psp, linux-omap: Added patch to fix MMC timeout errors
Op 21 jul. 2011, om 19:34 heeft Jason Kridner het volgende geschreven: On Thu, Jul 21, 2011 at 12:24 PM, Joel A Fernandes agnel.j...@gmail.com wrote: On Thu, Jul 21, 2011 at 1:29 AM, Koen Kooi k...@dominion.thruhere.net wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Op 21-07-11 00:02, Joel A Fernandes schreef: This fixes MMC errors due to timeouts on certain SD Cards following suggestions to set dto to 14 by Jason Kridner and Steven Kipisz Details of the issue: http://talk.maemo.org/showthread.php?p=1000707#post1000707 --- Changes since v1: * Made patch to apply to org.openembedded.dev branch * Bumped PR of respective recipes ...mc-Adjust-dto-to-eliminate-timeout-errors.patch | 27 ++ ...mc-Adjust-dto-to-eliminate-timeout-errors.patch | 39 +++- recipes/linux/linux-omap-psp_2.6.32.bb | 2 +- recipes/linux/linux-omap_2.6.39.bb |3 +- Could you please split that in 2? And for the .39 kernel, the master recipe is in meta-ti, not in .dev: http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/recipes-kernel/linux/linux-omap_2.6.39.bb?id=7018fe0a81fa33c6d73d6296d25517b5d427d0a7 Did you move it recently? If you don't mind, can you point me to some information on why this has changed? Are we not keeping both up-to-date for the time being? It's about the direction the merges happen, it goes into meta-ti first, then it gets synced to .dev and optionally to maintenance. ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] AM1808
Op 19 jul 2011, om 11:31 heeft Michael Schnell het volgende geschreven: Hi experts. I am new to this list, so please pardon me, if I violate any rules or this is off-topic here. We are starting to design a controller based on an AM1808 (or maybe an upcoming AM 335x) chip. Right now, we just have a Development kit (by Logic PD) that features an OMAP 138 Chip (that is pin-compatible with the AM1808 but additionally has a DSP) We started playing with this kit and now, I have several questions that you might be able to answer. The board came with an Angstrom Linux distribution. (Question 1) Can you give us a hint, whether it's a good idea to use Angstrom for an embedded controller or do you suggest to use another distributions (binary and/or cross compilable-source-code) ? Over here at angstrom we suggest angstrom :) I tried to update the Distribution via the opkg package manager. Lots of files were downloaded, but when opkg tried to install them I get an error message like too small memory. The board has 32 MB RAM Does it really only have 32M or is that artificially limited by uboot setting mem=32M? and the file system is close to empty. (At home I have another ARM hardware (a SLUG) with (IIRC) only 32 MB RAM and here updating via apt works just fine.) The board we are going to design will have 256 MB RAM, so I suppose this problem will not be seen there. Moreover I tried to install an additional package via opkg: same error. The board distributor and/or vendor installed angstrom on their own, so I don't know which version is on there and if there were some improvements made by the vendor. I'd suggest going to http://narcissus.angstrom-distribution.org/ And building a new image for the 'da850-omapl138-evm' machine (which matches your evm). (Question 2) How to use opkg on this device or upgrading the distribution (including the Kernel)l and installing additional packages (like audio and X)? Normally it's a matter of 'opkg update ; opkg install foo', you can see which packages are available at: http://www.angstrom-distribution.org/repo/ Note that not all angstrom releases have the same packages available, but we do try. I found that lsmod shows no loaded modules. But as busybox is configured to feature the module specific commands I suppose the distribution does support modules (Question 3) Can this system be enhanced with Kernel modules ? Why are no modules loaded after starting ? Yes, and for the second question, I don't know about the improvements that were made on top of a standard angstrom. We want to use I²S audio output. The kit does feature an I²S to analog converter. (Question 4) How to configure, use and test the audio output ? No idea on that, sorry. I think that's a question for logicPD. We want to use an LCD display (mainly for development and maintenance). The kit features a socket for the chip's LCD/Video pins. We are going to get an LCD panel to connect to the board or to find a converter that allows connecting some standard monitor. (Question 5) How to configure, use and test the LCD and/or Video output ? No idea on that, sorry. I think that's a question for logicPD. I know that the stock LCD is supported by angstrom out of the box. We want to be able to run software that has a GUI. (Question 6) How to install a system that allows for running GUI software (X11, QT or GTK or ???, ...) See my answers to question 1 and 2 :) We want to be able to run the system without a monitor connected. (Question 7) How to install and use VNC (or whatever) to remote-control the GUI of a running program ? For X11 you can install x11vnc and qt has a vnc plugin you can use, configuring those is a bit out of scope for angstrom, but let us know if you run into any troubles. regards, Koen ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] AM1808
Op 19 jul 2011, om 13:14 heeft Michael Schnell het volgende geschreven: On 07/19/2011 12:16 PM, Koen Kooi wrote: Over here at angstrom we suggest angstrom :) Yep. As I am new to angstrom. I) wanted to make sure that it's suitable for embedded controllers with AM1808 or AM 335x Does it really only have 32M or is that artificially limited by uboot setting mem=32M? The hardware is: http://www.logicpd.com/products/system-modules/texas-instruments-omap-l138-som-m1#tabs-som-2 Here they say it's either 64 or 128 MB but on the command line I get root@da850-omapl138-evm:~# cat /proc/meminfo MemTotal: 28120 kB [..] So maybe it in fact memory artificially limited. What to do about this ? (I'm new to uboot, too.) If you attach a serial console and go into uboot you can do the following (hawkboard has a AM1808 as well): U-Boot 2009.01-dirty (Nov 18 2009 - 23:30:48) DRAM: 128 MB NAND: NAND device: Manufacturer ID: 0x2c, Chip ID: 0xa1 (Micron NAND 128MiB 1,8V 8-bit) [..] hawkboard.org print bootargs bootargs=console=ttyS2,115200n8 root=/dev/mmcblk0p1 rw rootwait mem=64M And here we see that while 128MB is installed (the DRAM: line) linux only gets to see 64M (the mem= part), to fix that, do: hawkboard.org setenv bootargs 'bootargs=console=ttyS2,115200n8 root=/dev/mmcblk0p1 rw rootwait mem=128M' hawkboard.org saveenv Saving Environment to NAND... Erasing Nand... Erasing at 0x0 -- 100% complete. Writing to Nand... done hawkboard.org In your case you might see 'DRAM: 64MB' and need to pass in mem=64M, but you get the general idea. The board distributor and/or vendor installed angstrom on their own, so I don't know which version is on there and if there were some improvements made by the vendor. I'd suggest going to http://narcissus.angstrom-distribution.org/ And building a new image for the 'da850-omapl138-evm' machine (which matches your evm). I'll try to do this. But I suppose this will not take care of any uboot issues. Moreover I suppose I need to persuade uboot to install the new Kernel. Right now I don't know how to do this. (Question 2) How to use opkg on this device or upgrading the distribution (including the Kernel)l and installing additional packages (like audio and X)? Normally it's a matter of 'opkg update ; opkg install foo', I did try both and got the said error message: root@da850-omapl138-evm:~# opkg install ppp Upgrading ppp on root from 2.4.3-r9.5 to 2.4.3-r9.6... The r9.5 - r9.6 shows that it tries to upgrade for a pretty old angstrom to a more recent one: koen@dominion:/OE/angstrom-2008/sources/openembedded$ git blame conf/distro/angstrom-2008.1.conf | grep DISTRO_PR 56a7be99 (Koen Kooi 2010-09-07 15:03:44 +0200 18) DISTRO_PR = .6 So that's almost a year ago. Trying to update thru opkg would upgrade everything, so I'd advice generating a brand new image or ask logicPD if they have something more recent Downloading http://www.angstrom-distribution.org/feeds/unstable/ipk/glibc/armv5te/base/ppp_2.4.3-r9.6_armv5te.ipk. Collected errors: * gz_open: fork: Cannot allocate memory. * opkg_install_pkg: Failed to unpack control files from /tmp/opkg-GhmigW/ppp_2.4.3-r9.6_armv5te.ipk. * opkg_install_cmd: Cannot install package ppp. That version of angstrom lacks the opkg low-mem fixes, so it failing on 32M is expected. you can see which packages are available at: http://www.angstrom-distribution.org/repo/ I did check this and found an impressive number :) . Note that not all angstrom releases have the same packages available, but we do try. Obviously :) . That is why I at first tried to upgrade to the current version. I found that lsmod shows no loaded modules. But as busybox is configured to feature the module specific commands I suppose the distribution does support modules (Question 3) Can this system be enhanced with Kernel modules ? Why are no modules loaded after starting ? Yes, and for the second question, I don't know about the improvements that were made on top of a standard angstrom. I see. We want to use I²S audio output. The kit does feature an I²S to analog converter. (Question 4) How to configure, use and test the audio output ? No idea on that, sorry. I think that's a question for logicPD. Not exclusively. Of course a driver for the Chips I²S hardware is necessary. But as same is not specific to the PCB, but just to the TI-chip, I did hope it's included in one of the standard packages. AFAIK, the I²S to analog hardware in the board does not need any software support. But on top of the driver, I understand that I need to install the ALSA sub-system. And additionally, I need some user program that can output a sound just for testing. I hoped that these are standard issues that are covered by the distribution. A distribution generally just integrates what is already out there. Angstrom is a bit of a special case since a lot
Re: [Angstrom-devel] Bitbake build failure of Angstrom
Op 18 jul 2011, om 07:16 heeft Joel A Fernandes het volgende geschreven: Hi, I am attempting to manually rebuild the BeagleBoard validation image using bitbake. For this, I used the revision found in /etc/angstrom-version of an image I built with Narcissus. The OE revision I used referring to the above version file is: a1f31c757d2514e946737d60789c6f9f05ce38eb (Which happens to be my fix for GPIO) Now, when I run a bitbake beagleboard-validation-gnome-image -k Why are you using -k ? ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] [PATCH 1/2] assemble_image: Copy U-boot environment files for flashing NAND (controlled by user button)
Op 18 jul 2011, om 17:50 heeft Joel A Fernandes het volgende geschreven:
* Copy a user.txt and uEnv.txt if they exist in /boot in the root fs to the
boot partition,
When the user button is pressed, U-boot chooses between these 2 files,
user.txt is used
for flashing while uEnv.txt is for a regular boot
Signed-off-by: Joel A Fernandes agnel.j...@gmail.com
---
scripts/assemble-image.sh |8
1 files changed, 8 insertions(+), 0 deletions(-)
diff --git a/scripts/assemble-image.sh b/scripts/assemble-image.sh
index 6043bde..d34b1c8 100755
--- a/scripts/assemble-image.sh
+++ b/scripts/assemble-image.sh
@@ -126,6 +126,14 @@ if [ -e ${WORKDIR}/conf/${MACHINE}/sd ] ; then
echo Using uImage from narcissus, no uImage found in
rootfs
fi
+ if [ -e ${TARGET_DIR}/boot/user.txt ]; then
needs space between ] and ;
+ cp -v ${TARGET_DIR}/boot/user.txt
/mnt/narcissus/sd_image1/
+ fi
+
+ if [ -e ${TARGET_DIR}/boot/uEnv.txt ]; then
needs space between ] and ;
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] [PATCH 2/2] assemble_image: Copy a UBIFS image to the filesystem for SD Card image builds
Op 18 jul 2011, om 17:51 heeft Joel A Fernandes het volgende geschreven:
* For SD Card image builds, also make a ubi image and copy it to /boot in the
root filesystem
This is used by the flashing script to ubiformat the NAND
Signed-off-by: Joel A Fernandes agnel.j...@gmail.com
---
scripts/assemble-image.sh |6 +-
1 files changed, 5 insertions(+), 1 deletions(-)
diff --git a/scripts/assemble-image.sh b/scripts/assemble-image.sh
index d34b1c8..d0760b9 100755
--- a/scripts/assemble-image.sh
+++ b/scripts/assemble-image.sh
@@ -145,8 +145,11 @@ if [ -e ${WORKDIR}/conf/${MACHINE}/sd ] ; then
echo Copying file system:
echo tar xzf ${TARGET_DIR}/../${IMAGENAME}-${MACHINE}.tar.gz
-C /mnt/narcissus/sd_image2
tar xzf ${TARGET_DIR}/../${IMAGENAME}-${MACHINE}.tar.gz -C
/mnt/narcissus/sd_image2
- touch /mnt/narcissus/sd_image2/narcissus-was-here
+ echo Copying UBIFS image to file system:
+ mv ${TARGET_DIR}/../${IMAGENAME}-${MACHINE}.ubi
/mnt/narcissus/sd_image2/boot/fs.ubi
+
+ touch /mnt/narcissus/sd_image2/narcissus-was-here
echo Remounting ${LOOP_DEV_FS}
umount ${LOOP_DEV_FS}
mount ${LOOP_DEV_FS}
@@ -426,6 +429,7 @@ case ${IMAGETYPE} in
do_ext2;;
sdimg)
do_tar
+ do_ubifs
do_sdimg;;
The ubifs addition needs to be opt-in, not forcefully enabled for all builds
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] [PATCH v3 2/2] assemble_image: Copy a UBIFS image to the filesystem for SD Card image builds
Op 18 jul 2011, om 19:54 heeft Joel A Fernandes het volgende geschreven:
* For SD Card image builds, also make a ubi image and copy it to /boot in the
root filesystem
This is used by the flashing script to ubiformat the NAND
Signed-off-by: Joel A Fernandes agnel.j...@gmail.com
---
Changes since v2:
- Fixed spacing in if condition
scripts/assemble-image.sh | 11 ++-
1 files changed, 10 insertions(+), 1 deletions(-)
diff --git a/scripts/assemble-image.sh b/scripts/assemble-image.sh
index f2a595a..2940d9a 100755
--- a/scripts/assemble-image.sh
+++ b/scripts/assemble-image.sh
@@ -145,8 +145,13 @@ if [ -e ${WORKDIR}/conf/${MACHINE}/sd ] ; then
echo Copying file system:
echo tar xzf ${TARGET_DIR}/../${IMAGENAME}-${MACHINE}.tar.gz
-C /mnt/narcissus/sd_image2
tar xzf ${TARGET_DIR}/../${IMAGENAME}-${MACHINE}.tar.gz -C
/mnt/narcissus/sd_image2
- touch /mnt/narcissus/sd_image2/narcissus-was-here
+ if [ -e ${TARGET_DIR}/../${IMAGENAME}-${MACHINE}.ubi ] ; then
+ echo Copying UBIFS image to file system:
+ mv ${TARGET_DIR}/../${IMAGENAME}-${MACHINE}.ubi
/mnt/narcissus/sd_image2/boot/fs.ubi
+ fi
+
+ touch /mnt/narcissus/sd_image2/narcissus-was-here
echo Remounting ${LOOP_DEV_FS}
umount ${LOOP_DEV_FS}
mount ${LOOP_DEV_FS}
@@ -427,6 +432,10 @@ case ${IMAGETYPE} in
sdimg)
do_tar
do_sdimg;;
+ sdimg-ubi)
+ do_tar
+ do_ubifs
+ do_sdimg;;
How does sdimg-ubi get called?
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] [PATCH v3 2/2] assemble_image: Copy a UBIFS image to the filesystem for SD Card image builds
Op 18 jul 2011, om 21:18 heeft Joel A Fernandes het volgende geschreven:
On Mon, Jul 18, 2011 at 1:35 PM, Koen Kooi k...@dominion.thruhere.net wrote:
Op 18 jul 2011, om 19:54 heeft Joel A Fernandes het volgende geschreven:
* For SD Card image builds, also make a ubi image and copy it to /boot in
the root filesystem
This is used by the flashing script to ubiformat the NAND
Signed-off-by: Joel A Fernandes agnel.j...@gmail.com
---
Changes since v2:
- Fixed spacing in if condition
scripts/assemble-image.sh | 11 ++-
1 files changed, 10 insertions(+), 1 deletions(-)
diff --git a/scripts/assemble-image.sh b/scripts/assemble-image.sh
index f2a595a..2940d9a 100755
--- a/scripts/assemble-image.sh
+++ b/scripts/assemble-image.sh
@@ -145,8 +145,13 @@ if [ -e ${WORKDIR}/conf/${MACHINE}/sd ] ; then
echo Copying file system:
echo tar xzf ${TARGET_DIR}/../${IMAGENAME}-${MACHINE}.tar.gz
-C /mnt/narcissus/sd_image2
tar xzf ${TARGET_DIR}/../${IMAGENAME}-${MACHINE}.tar.gz -C
/mnt/narcissus/sd_image2
- touch /mnt/narcissus/sd_image2/narcissus-was-here
+ if [ -e ${TARGET_DIR}/../${IMAGENAME}-${MACHINE}.ubi ] ; then
+ echo Copying UBIFS image to file system:
+ mv ${TARGET_DIR}/../${IMAGENAME}-${MACHINE}.ubi
/mnt/narcissus/sd_image2/boot/fs.ubi
+ fi
+
+ touch /mnt/narcissus/sd_image2/narcissus-was-here
echo Remounting ${LOOP_DEV_FS}
umount ${LOOP_DEV_FS}
mount ${LOOP_DEV_FS}
@@ -427,6 +432,10 @@ case ${IMAGETYPE} in
sdimg)
do_tar
do_sdimg;;
+ sdimg-ubi)
+ do_tar
+ do_ubifs
+ do_sdimg;;
How does sdimg-ubi get called?
Jason's patch passes it in the radio button element imagetype.
Can you please send all the related patches as a series please? I've lost track
which version those what and which extra patches are needed.
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
[Angstrom-devel] Making angstrom-core the default in the setup scripts
Hi, What do you think of making the oe-core branch[1] the default in the setup scripts? The basic needs are there and I'm using it for for all the new work I'm doing. It is missing a lot of recipes, but if people can name the ones that are missing we can port them over to meta-oe and/or meta-angstrom. regards, Koen [1] http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/setup-scripts/log/?h=oe-core ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Problem building oe-core based Ångström on openSUSE 11.4 (64bit)
Op 27 jun 2011, om 17:43 heeft Steffen Sledz het volgende geschreven: I tried to make an Ångström build using the oebb.sh from the oe-core branch following the instructions in [1] (hope they are valid for this branch too). MACHINE=beagleboard ./oebb.sh config beagleboard MACHINE=beagleboard ./oebb.sh update made no problems, but MACHINE=beagleboard ./oebb.sh bitbake virtual/kernel resulted in this error --snip--- Executing: MACHINE=beagleboard bitbake virtual/kernel Pseudo is not present but is required, building this first before the main build ERROR: Execution of event handler 'check_sanity_eventhandler' failed ERROR: Poky's config sanity checker detected a potential misconfiguration. Either fix the cause of this error or at your own risk disable the checker (see sanity.conf). Following is the list of potential problems / advisories: You have a 32-bit libc, but no 32-bit headers. You must install the 32-bit libc headers. --snip--- I suppose that the library structure openSUSE is using (/usr/lib for 32bit stuff, /usr/lib64 for 64bit stuff) is the cause. Right? And how can this be fixed? As the message says: You must install the 32-bit libc headers. ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Build toolchain on SAM9G45 sdcard.
Op 25 jun 2011, om 15:12 heeft M T het volgende geschreven: Hi, I'm a newbie, and I would ask You about toolchain build on sd card. I have a sam9g45 board, and I would build the toolchain so that it can be put/copy in the SD card (no use the flash ram). I try with buildroot toolchain, but I have some problem in the compile process. Please, can You suggest me the one toolchain sources and the entire process to compile the Angstrom/toolchain source code in the SDcard ? Go to http://www.angstrom-distribution.org/ and read the first news article called Some usefull workflow blogs and the one called Simplified development setup and then click the Developers tab and read the instructions there. ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Problem efl-nodm-image with angstrom and oe-core branch
Op 14 jun 2011, om 17:12 heeft Nicolas Aguirre het volgende geschreven: 2011/6/14 Koen Kooi k...@dominion.thruhere.net: Op 14 jun 2011, om 14:58 heeft Nicolas Aguirre het volgende geschreven: Hi, i'm trying to build the efl-nodm-image of the oe-core branch, but i'm facing some problems. E17 won't start and fails with error : *** glibc detected *** /usr/bin/enlightenment: munmap_chunk(): invali pointer: 0x00d5f740 *** This image uses EFL 1.0 and related SVN revision of e17 and modules. I tried to change and use the angstrom's svn version of EFL and e17 , but the problem is the same. I made another test by changing the SVN revision number to a recent version (i used 60100 as revision number) but error is still here. This revision is working pretty well for me on x86 ubuntu desktop. For me it starts up, but gives me the I segfaulted screen after the first run wizard. Next step is to execute enlightenment with gdb to find where the problem is. But i have not idea how to integrate it on my image. I built it successfully on my build machine and add it in IMAGE_INSTALL var of my efl-no-dm image. But there is maybe a better solution ? Add gdb and ewm-dbg to IMAGE_INSTALL to get the symbols as well I tryed to opkg install gdb on the target, but it's not found in repositories. I would like to have your advices on this :) I'll try uploading gdb and friends to the feeds later today. gdb is in now. ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] USB trouble with Beagleboard C4 and 2Gb 2010.3 image
the ehci is USB 2.0 only, so for keyboards you'll need a hub Op 15 jun. 2011 om 20:31 heeft Darren Hart dvh...@linux.intel.com het volgende geschreven: I'm trying to verify if my Beagleboard C4 may have a hardware problem. I haven't been able to get the EHCI USB hub to recognize any devices on a linux-omap 2.6.37 based kernel. I thought I should see if things worked with Angstrom. Using the image from: http://www.angstrom-distribution.org/demo/beagleboard/sd-images/2gb/Angstrom-Beagleboard-demo-image-glibc-ipk-2010.3-beagleboard.sd-image-2GiB.img.bz2 I see the following after inserting a USB RF tranceiver for a wireless keyboard/mouse. I see the same with a simple wired USB optical mouse. root@beagleboard:~# lsusb [ 408.834106] hub 1-0:1.0: Cannot enable port 2. Maybe the USB cable is bad? [ 411.912139] hub 1-0:1.0: Cannot enable port 2. Maybe the USB cable is bad? [ 414.990509] hub 1-0:1.0: Cannot enable port 2. Maybe the USB cable is bad? [ 418.068481] hub 1-0:1.0: Cannot enable port 2. Maybe the USB cable is bad? [ 418.075531] hub 1-0:1.0: unable to enumerate USB device on port 2 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub I was able to insert a USB key and see the partitions appear in /proc/partitions, which is more than I got with my 2.6.37 kernel. However, the keyboard is not recognized and the warnings above concern me. This device works fine in an xM. I wasn't able to test with Angstrom on the xM as this same image fails to boot there - perhaps there is a newer one available somewhere? Given the above, should I pursue the possibility of faulty hardware on my C4? I am powering the board with a 5v 2.5A AC/DC adapter. The same behavior results powering over musb with a wall plug source. -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] narcissus image with toolchain
Op 14 jun 2011, om 11:20 heeft Nuno Cardoso het volgende geschreven: Hi, Basically what I need is a rootfs for development and make some performance tests with Valgrind. But, to run Valgrind I need a non-stripped glibc library. Valgring needs to use glibc table of symbols to make the system performance tests... When I use a standard image from Narcissus, glibc is compiled with strip command, that remove the table of symbols. Can you tell me if it is possible I compile an angstrom image with narcissus without removing the table of symbols from glibc. 'opkg update ; opkg install glibc-dbg' to install the symbol table. regards, Koen Narcissus provides any option to intall Valgrind... or I need to compile it? Thanks, Huck. 2011/6/14 Koen Kooi k...@dominion.thruhere.net Op 14 jun 2011, om 10:24 heeft Nuno Cardoso het volgende geschreven: Hi list, When I create Narcissus image for beagleboard with this options: - Select the machine you want to build your rootfs image for: beagleboard - Choose the complexity of the options below: Advanced - Base System: regular - SDK type: simple toolchain - *User environment selection: console only* *- **Additional packages selection: *Development packages: toolchain The unpack rootfs image have this file structure: /home/ncardoso/devkit8000/usr/local/angstrom/arm/ + dirs I need to copy all the directory path to SD Card or the path after dirs? Is this a target file system or a directory that I need on the host machine for cross-compile? You get 2 tarballs: 1) the filesystem for your target 2) the sdk that runs on your to to crosscompile for your target. http://www.angstrom-distribution.org/toolchains/ shows how you could use the SDK. If you want a toolchain to run *on* your target, select Native (on-target) SDK from the development packages section. regards, Koen ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Problem efl-nodm-image with angstrom and oe-core branch
Op 14 jun 2011, om 14:58 heeft Nicolas Aguirre het volgende geschreven: Hi, i'm trying to build the efl-nodm-image of the oe-core branch, but i'm facing some problems. E17 won't start and fails with error : *** glibc detected *** /usr/bin/enlightenment: munmap_chunk(): invali pointer: 0x00d5f740 *** This image uses EFL 1.0 and related SVN revision of e17 and modules. I tried to change and use the angstrom's svn version of EFL and e17 , but the problem is the same. I made another test by changing the SVN revision number to a recent version (i used 60100 as revision number) but error is still here. This revision is working pretty well for me on x86 ubuntu desktop. For me it starts up, but gives me the I segfaulted screen after the first run wizard. Next step is to execute enlightenment with gdb to find where the problem is. But i have not idea how to integrate it on my image. I built it successfully on my build machine and add it in IMAGE_INSTALL var of my efl-no-dm image. But there is maybe a better solution ? Add gdb and ewm-dbg to IMAGE_INSTALL to get the symbols as well I tryed to opkg install gdb on the target, but it's not found in repositories. I would like to have your advices on this :) I'll try uploading gdb and friends to the feeds later today. regards, Koen ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Online builder source code
Op 11 jun 2011, om 15:35 heeft David Lambert het volgende geschreven: The link on the nacissus online builder for the souce code appears to be broken. It leads to: http://dominion.thruhere.net/git/cgit.cgi/?q=angstrom This link states: No repositories found Where can I find this? When I go to http://narcissus.angstrom-distribution.org/ and scroll down to the bottom the link points to http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/narcissus/ . Where did you get the link to dominion? ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Narcissus installation
Op 11 jun 2011, om 22:03 heeft David Lambert het volgende geschreven: From the narcissus README: * put pseudo and libpseudo in bin/ - Where are these to be found? Dave. You;ll have to build it from https://github.com/wrpseudo/pseudo/tree/PSEUDO_1_1_1, I'll update the narcissus readme next week with the build instruction since they are nonobvious for mixed 32/64 bit hosts. ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] QA error in dspgw-utils_3.3.1.bb.
Op 8 jun 2011, om 09:54 heeft Joaquim Duran het volgende geschreven: Hello, A QA error has been detected in dspgw-utils_3.3.1.bb. Build Configuration: BB_VERSION= 1.12.0 METADATA_BRANCH = 2011.03-maintenance METADATA_REVISION = dd8ac3a TARGET_ARCH = arm TARGET_OS = linux-gnueabi MACHINE = beagleboard DISTRO= angstrom DISTRO_VERSION= 2011.03 TARGET_FPU= hard NOTE: package dspgw-utils-3.3.1-r1: task do_package: Started ERROR: QA Issue with dspgw-utils: No GNU_HASH in the elf binary: '/home/jduran/projectes/gem_heard_two/tao-3530/openembedded/angstrom-setup-scripts/build/tmp-angstrom_2008_1/work/armv7a-angstrom-linux-gnueabi/dspgw-utils-3.3.1-r1/packages-split/dspgw-utils/usr/sbin/dsp_dld' ERROR: QA run found fatal errors. Please consider fixing them. NOTE: package dspgw-utils-3.3.1-r1: task do_package_qa: Failed ERROR: Function 'do_package_qa' failed ERROR: Task 14 (/home/jduran/projectes/gem_heard_two/tao-3530/openembedded/angstrom-setup-scripts/sources/openembedded/recipes/dspgw-utils/dspgw-utils_3.3.1.bb, do_package) failed with exit code '1' Why are you building an omap1 interface for omap3? Did you port the dspgw driver to the beagle kernel? ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] QA error in dspgw-utils_3.3.1.bb.
Op 8 jun 2011, om 12:11 heeft Joaquim Duran het volgende geschreven: 2011/6/8 Koen Kooi k...@dominion.thruhere.net: Op 8 jun 2011, om 09:54 heeft Joaquim Duran het volgende geschreven: Hello, A QA error has been detected in dspgw-utils_3.3.1.bb. Build Configuration: BB_VERSION= 1.12.0 METADATA_BRANCH = 2011.03-maintenance METADATA_REVISION = dd8ac3a TARGET_ARCH = arm TARGET_OS = linux-gnueabi MACHINE = beagleboard DISTRO= angstrom DISTRO_VERSION= 2011.03 TARGET_FPU= hard NOTE: package dspgw-utils-3.3.1-r1: task do_package: Started ERROR: QA Issue with dspgw-utils: No GNU_HASH in the elf binary: '/home/jduran/projectes/gem_heard_two/tao-3530/openembedded/angstrom-setup-scripts/build/tmp-angstrom_2008_1/work/armv7a-angstrom-linux-gnueabi/dspgw-utils-3.3.1-r1/packages-split/dspgw-utils/usr/sbin/dsp_dld' ERROR: QA run found fatal errors. Please consider fixing them. NOTE: package dspgw-utils-3.3.1-r1: task do_package_qa: Failed ERROR: Function 'do_package_qa' failed ERROR: Task 14 (/home/jduran/projectes/gem_heard_two/tao-3530/openembedded/angstrom-setup-scripts/sources/openembedded/recipes/dspgw-utils/dspgw-utils_3.3.1.bb, do_package) failed with exit code '1' Why are you building an omap1 interface for omap3? Did you port the dspgw driver to the beagle kernel? I was thinking that that packages was the tools/libraries to communicate with the DSP so I decided to create the project to test it. I'm interested to write my own applications for the DSP. Based on the documentation of the project (http://dspgateway.sourceforge.net/pub/3.3.1/DSP_Gateway331_spec_a.pdf), it also includes OMAP2. More over, there is instructions to use the DSP with beagleboard and similars boards: http://elinux.org/BeagleBoard/DSP_Howto http://omappedia.org/wiki/DSPBridge_Project For beagleboard only dsplink is supported and maybe syslink at a later point. ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Failed to generate the 4.6.3 qt4e with gles activated
Op 7 jun 2011, om 12:32 heeft Joaquim Duran het volgende geschreven: Dear all, I've detected an error when generating qt4-embedded-gles-4.6.3 receipe. did you clean the non-gles recipe first? Build Configuration: BB_VERSION= 1.12.0 METADATA_BRANCH = 2011.03-maintenance METADATA_REVISION = dd8ac3a TARGET_ARCH = arm TARGET_OS = linux-gnueabi MACHINE = beagleboard DISTRO= angstrom DISTRO_VERSION= 2011.03 TARGET_FPU= hard | make[1]: Entering directory `/home/jduran/projectes/gem_heard_two/tao-3530/openembedded/angstrom-setup-scripts/build/tmp-angstrom_2008_1/work/armv7a-angstrom-linux-gnueabi/qt4-embedded-gles-4.6.3-r29.8/qt-everywhere-opensource-src-4.6.3/src/opengl' | rm -f libQtOpenGLE.so.4.6.3 libQtOpenGLE.so libQtOpenGLE.so.4 libQtOpenGLE.so.4.6 | arm-angstrom-linux-gnueabi-g++ -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp -mthumb-interwork -mno-thumb --sysroot=/home/jduran/projectes/gem_heard_two/tao-3530/openembedded/angstrom-setup-scripts/build/tmp-angstrom_2008_1/sysroots/armv7a-angstrom-linux-gnueabi -Wl,-rpath-link,/home/jduran/projectes/gem_heard_two/tao-3530/openembedded/angstrom-setup-scripts/build/tmp-angstrom_2008_1/sysroots/armv7a-angstrom-linux-gnueabi/usr/lib -Wl,-O1 -Wl,--hash-style=gnu -Wl,--no-undefined -shared -Wl,-Bsymbolic-functions -Wl,-soname,libQtOpenGLE.so.4 -o libQtOpenGLE.so.4.6.3 .obj/release-shared-emb-arm/qgl.o .obj/release-shared-emb-arm/qglcolormap.o .obj/release-shared-emb-arm/qglpixelbuffer.o .obj/release-shared-emb-arm/qglframebufferobject.o .obj/release-shared-emb-arm/qglextensions.o .obj/release-shared-emb-arm/qglpaintdevice.o .obj/release-shared-emb-arm/qglshaderprogram.o .obj/release-shared-emb-arm/qglpixmapfilter.o .obj/release-shared-emb-arm/qgraphicsshadereffect.o .obj/release-shared-emb-arm/qgraphicssystem_gl.o .obj/release-shared-emb-arm/qwindowsurface_gl.o .obj/release-shared-emb-arm/qpixmapdata_gl.o .obj/release-shared-emb-arm/qglgradientcache.o .obj/release-shared-emb-arm/qglengineshadermanager.o .obj/release-shared-emb-arm/qgl2pexvertexarray.o .obj/release-shared-emb-arm/qpaintengineex_opengl2.o .obj/release-shared-emb-arm/qglcustomshaderstage.o .obj/release-shared-emb-arm/qtriangulatingstroker.o .obj/release-shared-emb-arm/qtextureglyphcache_gl.o .obj/release-shared-emb-arm/qgl_qws.o .obj/release-shared-emb-arm/qglpixelbuffer_egl.o .obj/release-shared-emb-arm/qglscreen_qws.o .obj/release-shared-emb-arm/qglwindowsurface_qws.o .obj/release-shared-emb-arm/qgl_egl.o .obj/release-shared-emb-arm/moc_qgl.o .obj/release-shared-emb-arm/moc_qgl_p.o .obj/release-shared-emb-arm/moc_qglshaderprogram.o .obj/release-shared-emb-arm/moc_qgraphicsshadereffect_p.o .obj/release-shared-emb-arm/moc_qwindowsurface_gl_p.o .obj/release-shared-emb-arm/moc_qglengineshadermanager_p.o .obj/release-shared-emb-arm/moc_qtextureglyphcache_gl_p.o -L/home/jduran/projectes/gem_heard_two/tao-3530/openembedded/angstrom-setup-scripts/build/tmp-angstrom_2008_1/sysroots/armv7a-angstrom-linux-gnueabi/usr/lib -L/home/jduran/projectes/gem_heard_two/tao-3530/openembedded/angstrom-setup-scripts/build/tmp-angstrom_2008_1/work/armv7a-angstrom-linux-gnueabi/qt4-embedded-gles-4.6.3-r29.8/qt-everywhere-opensource-src-4.6.3/lib -L -Wl,-rpath-link,/home/jduran/projectes/gem_heard_two/tao-3530/openembedded/angstrom-setup-scripts/build/tmp-angstrom_2008_1/work/armv7a-angstrom-linux-gnueabi/qt4-embedded-gles-4.6.3-r29.8/qt-everywhere-opensource-src-4.6.3/lib -lQtGuiE -lQtNetworkE -lQtCoreE -lglib-2.0 -lpthread -lEGL -lIMGegl -lsrv_um -lEGL -lGLESv2 -lGLES_CM -lIMGegl -lsrv_um | .obj/release-shared-emb-arm/qgl_qws.o: In function `qt_egl_add_platform_config(QEglProperties, QPaintDevice*)': | /home/jduran/projectes/gem_heard_two/tao-3530/openembedded/angstrom-setup-scripts/build/tmp-angstrom_2008_1/work/armv7a-angstrom-linux-gnueabi/qt4-embedded-gles-4.6.3-r29.8/qt-everywhere-opensource-src-4.6.3/src/opengl/qgl_qws.cpp:134: undefined reference to `QEglProperties::setPixelFormat(QImage::Format)' | /home/jduran/projectes/gem_heard_two/tao-3530/openembedded/angstrom-setup-scripts/build/tmp-angstrom_2008_1/work/armv7a-angstrom-linux-gnueabi/qt4-embedded-gles-4.6.3-r29.8/qt-everywhere-opensource-src-4.6.3/src/opengl/qgl_qws.cpp:132: undefined reference to `QEglProperties::setPixelFormat(QImage::Format)' | .obj/release-shared-emb-arm/qgl_qws.o: In function `QGLContext::chooseContext(QGLContext const*)': | /home/jduran/projectes/gem_heard_two/tao-3530/openembedded/angstrom-setup-scripts/build/tmp-angstrom_2008_1/work/armv7a-angstrom-linux-gnueabi/qt4-embedded-gles-4.6.3-r29.8/qt-everywhere-opensource-src-4.6.3/src/opengl/qgl_qws.cpp:199: undefined reference to `QEglContext::QEglContext()' |
Re: [Angstrom-devel] meta-toolchain-qte problems
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 31-05-11 19:23, Trevor Hickey wrote: Hello all, I am trying to bitbake the meta-toolchain-qte file for the mini2440 to be able to compile Qt apps for the mini2440. However, I am running into some problems while trying to bitbake this package. It gives me an error when it tried to bitbake the qt4-tools-sdk_4.6.3.bb recipe. NOTE: Running task 1594 of 2622 (ID: 741, /home/balute/oe/openembedded/recipes/qt4/qt4-tools-sdk_4.6.3.bb, do_compile) ERROR: function do_compile failed ERROR: see log in /home/balute/oe/build/work/i686-armv4t-sdk-angstrom-linux-gnueabi/qt4-tools-sdk-4.6.3-r0/temp/log.do_compile.2720 NOTE: Task failed: /home/balute/oe/build/work/i686-armv4t-sdk-angstrom-linux-gnueabi/qt4-tools-sdk-4.6.3-r0/temp/log.do_compile.2720 ERROR: TaskFailed event exception, aborting ERROR: Build of /home/balute/oe/openembedded/recipes/qt4/ qt4-tools-sdk_4.6.3.bb do_compile failed ERROR: Task 741 (/home/balute/oe/openembedded/recipes/qt4/ qt4-tools-sdk_4.6.3.bb, do_compile) failed NOTE: Waiting for 1 active tasks to finish NOTE: 1: /home/balute/oe/openembedded/recipes/qt4/qt4-tools-native_4.4.3.bb, do_setscene (2678) Configuring staging-qt4-tools-native-i686-linux sh: rm: command not found NOTE: Staging package found, using it for /home/balute/oe/openembedded/recipes/qt4/qt4-tools-native_4.4.3.bb. Installing staging-qt4-tools-native-i686-linux (4.4.3-r3) to root... Configuring staging-qt4-tools-native-i686-linux sh: rm: command not found NOTE: Tasks Summary: Attempted 1592 tasks of which 1587 didn't need to be rerun and 1 failed. ERROR: '/home/balute/oe/openembedded/recipes/qt4/qt4-tools-sdk_4.6.3.bb' failed and in the log file the last 3 lines are collect2: ld returned 1 exit status make: *** [../../../bin/uic3] Error 1 FATAL: oe_runmake failed I have been trying to fix this for a couple days now with no luck and I cannot find any helpful resources. Help please? I took a b54 debian machine and installed the buildsys according to http://www.angstrom-distribution.org/building-angstrom and I get: NOTE: package meta-toolchain-qte-1.0-r5: task do_build: Succeeded Since qt is memory hungry thing to build, does you buildmachine have enough ram and swap? regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFN5d3cMkyGM64RGpERAqSjAKCNRESJiOM1957A0Wo5hjPUh8qG1gCeLe1p RU2xIzutujMWhON0wn/+v50= =HzwR -END PGP SIGNATURE- ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Working with Angstrom as an upstream distro (layers and meta-angstrom related)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 31-05-11 15:31, John Willis wrote: Hi, This is something that came up in a conversation with Koen and I thought it might be prudent to open the debate on the list to get some feedback about the best way to approach this workflow without generating any ill feeling or unintentional marginalisation. The scenario is quite simple... I have started to clean up and refactor the old OpenPandora recipes into something that aligns a lot more closely with OE-Core/Meta-OE and Meta-Angstrom going forward. This is purely a personal project (that I welcome help with) and is not necessarily tied to the main OpenPandora 'entity'. It is mostly for my own benefit as I have a few other projects/machines that I would like to apply the same working pattern. The forking and keeping bits in various trees with no very clear distinction has always been a problem in the past and I want to minimise this going forward making best use of layers. I also want to ensure some ground rules are set before I start committing or working on this in earnest (it's a 'free time pet project' for me so I don't want to waste my time creating a rod for my own back, I can do that on a myriad of other projects ;)). At the moment I have https://github.com/openpandora/meta-openpandora, this is the old OpenPandora overlay refactored into something more akin to the new layer layout. At the moment this layer has both machine level BSP type stuff in it and the general 'not for mainline' OpenPandora overlay stuff that makes up the stock image (some custom libs, a logo and some image/task files etc.). My plan is to move meta-openpandora into a true hardware BSP layer so that you can just add this to give you full hardware support for the OpenPandora to any existing combination of OE layers (e.g. kernel, bootloader, netbase, formfactor, basefiles etc.). As part of this the rest of the 'not for mainline/cruft' stuff would need to find its way into a companion layer (say meta-openpandora-vendor or some such). Is this a good idea? I think that's a very good idea. Let me know when you want to have the openpandora BSP added to the angstrom bblayers.conf by default. regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFN5PO2MkyGM64RGpERAtjNAJ0dKMXhaucKJi0lscVki9Vd0zn83wCguIFk elmWgWXeeaWl8CyiG3nVP0o= =0MTX -END PGP SIGNATURE- ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] BeagleBoard (C3) won't boot
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 30-05-11 21:18, Gary Thomas wrote: On 05/29/2011 08:27 AM, Koen Kooi wrote: Op 29 mei 2011, om 14:18 heeft Gary Thomas het volgende geschreven: On 05/29/2011 05:46 AM, Koen Kooi wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 29-05-11 13:34, Gary Thomas wrote: On 05/28/2011 07:00 AM, Gary Thomas wrote: On 05/28/2011 05:45 AM, Koen Kooi wrote: (Adding beagle group to CC:) Op 28 mei 2011, om 12:46 heeft Gary Thomas het volgende geschreven: On 05/28/2011 04:35 AM, Koen Kooi wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 28-05-11 12:07, Gary Thomas wrote: I just built Angstrom via oe-core for the BeagleBoard, rev C3 (not xM) Here were my steps: $ git clone git://git.angstrom-distribution.org/setup-scripts angstrom-bb $ cd angstrom-bb $ git checkout -b local-oe origin/oe-core $ MACHINE=beagleboard ./oebb.sh config beagleboard $ MACHINE=beagleboard ./oebb.sh bitbake console-image It doesn't boot at all. I built a bootable SD from the deploy/images, including MLO and U-Boot. Here's the boot sequence (I broke in to set the console): Texas Instruments X-Loader 1.4.4ss (Jan 29 2011 - 10:54:03) That should say 1.5.0, but wouldn't cause boot problems. For reference, this is what I get on my C3: It seems like every major component (MLO, U-Boot, Linux kernel) differs between my build and yours. So what did you do differently? Why is my build so different (and not work)? I used the stock conf/local.conf - did you make any changes to it? You're right, my FAT partition was a mess, I recreated the card using OE-core built stuff, log is further below. The one change I have is this one: http://patches.openembedded.org/patch/4677/ which might explain the problems Gary is seeing, but not the problems I'm encountering. I'm trying this now with that patch applied. So far, I can already see signs of change (fewer strange warnings while parsing recipes, etc). I'm doing a complete build from scratch, so I won't know the results for a few hours. Sadly, I'm still getting the same results even with this patch. I'm still curious why my components are different (MLO=1.4.4 vs 1.5 for you, etc)? It's probably loading from nand, do a 'nand erase.chip' from inside uboot I pressed the user button to force it to read from MMC and see the correct date. Here are the package versions that were built: u-boot-v2011.03+git1+b29fbb347698286935bfc401c08499a6f63479de-r3 x-load-1.42+r13+git1+6f3a26101303051e0f91b6213735b68ce804e94e-r13 linux-omap-2.6.39-r0 I am confused by this though. For example, that version of x-load is coming from sources/openembedded-core/meta/recipes-bsp/x-load/x-load_git.bb not (as I think yours is) sources/meta-texasinstruments/recipes-bsp/x-load/x-load_git.bb It would seem to me that the build should come from the meta-texasinstruments layer which has priority=10? The list of all packages built by the process I've described (above) is attached. How does it line up with what you've built and why the difference(s)? You might have an old copy of the setup-scripts, which revision are you using? I check on my 3 buildhosts and they all build the correct MLO, but I can imagine that using an old bblayers.conf would seriously mess that up. As up to date as I can get I think: $ git pull gitorious.org[0: 2a02:c0:1014::1]: errno=Connection refused We moved off gitorious as hosting for setup-scripts a long time ago, which is why http://www.angstrom-distribution.org/building-angstrom tells you to pull from git.angstrom-distribution.org :) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFN4++JMkyGM64RGpERAmYXAJ9frkAL8Gfli1yWd7KIm0F/3uMQFQCghyRz DllDGy2Zv/VU1pbx4dsoabA= =NC9n -END PGP SIGNATURE- ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] BeagleBoard (C3) won't boot
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 30-05-11 21:18, Gary Thomas wrote: On 05/29/2011 08:27 AM, Koen Kooi wrote: Op 29 mei 2011, om 14:18 heeft Gary Thomas het volgende geschreven: On 05/29/2011 05:46 AM, Koen Kooi wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 29-05-11 13:34, Gary Thomas wrote: On 05/28/2011 07:00 AM, Gary Thomas wrote: On 05/28/2011 05:45 AM, Koen Kooi wrote: (Adding beagle group to CC:) Op 28 mei 2011, om 12:46 heeft Gary Thomas het volgende geschreven: On 05/28/2011 04:35 AM, Koen Kooi wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 28-05-11 12:07, Gary Thomas wrote: I just built Angstrom via oe-core for the BeagleBoard, rev C3 (not xM) Here were my steps: $ git clone git://git.angstrom-distribution.org/setup-scripts angstrom-bb $ cd angstrom-bb $ git checkout -b local-oe origin/oe-core $ MACHINE=beagleboard ./oebb.sh config beagleboard $ MACHINE=beagleboard ./oebb.sh bitbake console-image It doesn't boot at all. I built a bootable SD from the deploy/images, including MLO and U-Boot. Here's the boot sequence (I broke in to set the console): Texas Instruments X-Loader 1.4.4ss (Jan 29 2011 - 10:54:03) That should say 1.5.0, but wouldn't cause boot problems. For reference, this is what I get on my C3: It seems like every major component (MLO, U-Boot, Linux kernel) differs between my build and yours. So what did you do differently? Why is my build so different (and not work)? I used the stock conf/local.conf - did you make any changes to it? You're right, my FAT partition was a mess, I recreated the card using OE-core built stuff, log is further below. The one change I have is this one: http://patches.openembedded.org/patch/4677/ which might explain the problems Gary is seeing, but not the problems I'm encountering. I'm trying this now with that patch applied. So far, I can already see signs of change (fewer strange warnings while parsing recipes, etc). I'm doing a complete build from scratch, so I won't know the results for a few hours. Sadly, I'm still getting the same results even with this patch. I'm still curious why my components are different (MLO=1.4.4 vs 1.5 for you, etc)? It's probably loading from nand, do a 'nand erase.chip' from inside uboot I pressed the user button to force it to read from MMC and see the correct date. Here are the package versions that were built: u-boot-v2011.03+git1+b29fbb347698286935bfc401c08499a6f63479de-r3 x-load-1.42+r13+git1+6f3a26101303051e0f91b6213735b68ce804e94e-r13 linux-omap-2.6.39-r0 I am confused by this though. For example, that version of x-load is coming from sources/openembedded-core/meta/recipes-bsp/x-load/x-load_git.bb not (as I think yours is) sources/meta-texasinstruments/recipes-bsp/x-load/x-load_git.bb It would seem to me that the build should come from the meta-texasinstruments layer which has priority=10? The list of all packages built by the process I've described (above) is attached. How does it line up with what you've built and why the difference(s)? You might have an old copy of the setup-scripts, which revision are you using? I check on my 3 buildhosts and they all build the correct MLO, but I can imagine that using an old bblayers.conf would seriously mess that up. As up to date as I can get I think: $ git pull gitorious.org[0: 2a02:c0:1014::1]: errno=Connection refused We moved off gitorious as hosting for setup-scripts a long time ago, which is why http://www.angstrom-distribution.org/building-angstrom tells you to pull from git.angstrom-distribution.org :) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFN4++vMkyGM64RGpERApwKAJ9vVIO8U8PD/hqjz95qA7Mf8u57WACeOsJt zMFxxSIhVoxMtNn1WMS3FC4= =/mu+ -END PGP SIGNATURE- ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] BeagleBoard (C3) won't boot
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 29-05-11 13:34, Gary Thomas wrote: On 05/28/2011 07:00 AM, Gary Thomas wrote: On 05/28/2011 05:45 AM, Koen Kooi wrote: (Adding beagle group to CC:) Op 28 mei 2011, om 12:46 heeft Gary Thomas het volgende geschreven: On 05/28/2011 04:35 AM, Koen Kooi wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 28-05-11 12:07, Gary Thomas wrote: I just built Angstrom via oe-core for the BeagleBoard, rev C3 (not xM) Here were my steps: $ git clone git://git.angstrom-distribution.org/setup-scripts angstrom-bb $ cd angstrom-bb $ git checkout -b local-oe origin/oe-core $ MACHINE=beagleboard ./oebb.sh config beagleboard $ MACHINE=beagleboard ./oebb.sh bitbake console-image It doesn't boot at all. I built a bootable SD from the deploy/images, including MLO and U-Boot. Here's the boot sequence (I broke in to set the console): Texas Instruments X-Loader 1.4.4ss (Jan 29 2011 - 10:54:03) That should say 1.5.0, but wouldn't cause boot problems. For reference, this is what I get on my C3: It seems like every major component (MLO, U-Boot, Linux kernel) differs between my build and yours. So what did you do differently? Why is my build so different (and not work)? I used the stock conf/local.conf - did you make any changes to it? You're right, my FAT partition was a mess, I recreated the card using OE-core built stuff, log is further below. The one change I have is this one: http://patches.openembedded.org/patch/4677/ which might explain the problems Gary is seeing, but not the problems I'm encountering. I'm trying this now with that patch applied. So far, I can already see signs of change (fewer strange warnings while parsing recipes, etc). I'm doing a complete build from scratch, so I won't know the results for a few hours. Sadly, I'm still getting the same results even with this patch. I'm still curious why my components are different (MLO=1.4.4 vs 1.5 for you, etc)? It's probably loading from nand, do a 'nand erase.chip' from inside uboot -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFN4jIRMkyGM64RGpERAmyUAJ4tg+vri57Z1hCe7ZtgK7veD7J5bQCfcloe Cv62Ru5i1L02GbiCF1m+dWo= =aVgl -END PGP SIGNATURE- ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] BeagleBoard (C3) won't boot
Op 29 mei 2011, om 14:18 heeft Gary Thomas het volgende geschreven: On 05/29/2011 05:46 AM, Koen Kooi wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 29-05-11 13:34, Gary Thomas wrote: On 05/28/2011 07:00 AM, Gary Thomas wrote: On 05/28/2011 05:45 AM, Koen Kooi wrote: (Adding beagle group to CC:) Op 28 mei 2011, om 12:46 heeft Gary Thomas het volgende geschreven: On 05/28/2011 04:35 AM, Koen Kooi wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 28-05-11 12:07, Gary Thomas wrote: I just built Angstrom via oe-core for the BeagleBoard, rev C3 (not xM) Here were my steps: $ git clone git://git.angstrom-distribution.org/setup-scripts angstrom-bb $ cd angstrom-bb $ git checkout -b local-oe origin/oe-core $ MACHINE=beagleboard ./oebb.sh config beagleboard $ MACHINE=beagleboard ./oebb.sh bitbake console-image It doesn't boot at all. I built a bootable SD from the deploy/images, including MLO and U-Boot. Here's the boot sequence (I broke in to set the console): Texas Instruments X-Loader 1.4.4ss (Jan 29 2011 - 10:54:03) That should say 1.5.0, but wouldn't cause boot problems. For reference, this is what I get on my C3: It seems like every major component (MLO, U-Boot, Linux kernel) differs between my build and yours. So what did you do differently? Why is my build so different (and not work)? I used the stock conf/local.conf - did you make any changes to it? You're right, my FAT partition was a mess, I recreated the card using OE-core built stuff, log is further below. The one change I have is this one: http://patches.openembedded.org/patch/4677/ which might explain the problems Gary is seeing, but not the problems I'm encountering. I'm trying this now with that patch applied. So far, I can already see signs of change (fewer strange warnings while parsing recipes, etc). I'm doing a complete build from scratch, so I won't know the results for a few hours. Sadly, I'm still getting the same results even with this patch. I'm still curious why my components are different (MLO=1.4.4 vs 1.5 for you, etc)? It's probably loading from nand, do a 'nand erase.chip' from inside uboot I pressed the user button to force it to read from MMC and see the correct date. Here are the package versions that were built: u-boot-v2011.03+git1+b29fbb347698286935bfc401c08499a6f63479de-r3 x-load-1.42+r13+git1+6f3a26101303051e0f91b6213735b68ce804e94e-r13 linux-omap-2.6.39-r0 I am confused by this though. For example, that version of x-load is coming from sources/openembedded-core/meta/recipes-bsp/x-load/x-load_git.bb not (as I think yours is) sources/meta-texasinstruments/recipes-bsp/x-load/x-load_git.bb It would seem to me that the build should come from the meta-texasinstruments layer which has priority=10? The list of all packages built by the process I've described (above) is attached. How does it line up with what you've built and why the difference(s)? You might have an old copy of the setup-scripts, which revision are you using? I check on my 3 buildhosts and they all build the correct MLO, but I can imagine that using an old bblayers.conf would seriously mess that up. regards, Koen regards, Koen ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] BeagleBoard (C3) won't boot
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 28-05-11 12:07, Gary Thomas wrote: I just built Angstrom via oe-core for the BeagleBoard, rev C3 (not xM) Here were my steps: $ git clone git://git.angstrom-distribution.org/setup-scripts angstrom-bb $ cd angstrom-bb $ git checkout -b local-oe origin/oe-core $ MACHINE=beagleboard ./oebb.sh config beagleboard $ MACHINE=beagleboard ./oebb.sh bitbake console-image It doesn't boot at all. I built a bootable SD from the deploy/images, including MLO and U-Boot. Here's the boot sequence (I broke in to set the console): Texas Instruments X-Loader 1.4.4ss (Jan 29 2011 - 10:54:03) That should say 1.5.0, but wouldn't cause boot problems. For reference, this is what I get on my C3: Texas Instruments X-Loader 1.5.0 (May 23 2011 - 13:53:21) Beagle Rev C1/C2/C3 Reading boot sector Loading u-boot.bin from mmc U-Boot 2011.03-rc1-0-g5ace684-dirty (May 15 2011 - 18:50:56) OMAP3530-GP ES3.0, CPU-OPP2, L3-165MHz, Max CPU Clock 600 mHz OMAP3 Beagle board + LPDDR/NAND I2C: ready DRAM: 256 MiB NAND: 256 MiB MMC: OMAP SD/MMC: 0 *** Warning - bad CRC, using default environment In:serial Out: serial Err: serial Beagle Rev C1/C2/C3 Recognized Tincantools Zippy board (rev 1 ) Die ID #40880003040323090d01c015 Hit any key to stop autoboot: 3 2 1 0 The user button is currently NOT pressed. SD/MMC found on device 0 reading uEnv.txt MMC: block number 0x1906 exceeds max(0x3af000) ** Unable to read uEnv.txt from mmc 0:1 ** Loading file /boot/uImage from mmc device 0:2 (xxa2) 3329956 bytes read Booting from mmc ... ## Booting kernel from Legacy Image at 8020 ... Image Name: Angstrom/2.6.39/beagleboard Image Type: ARM Linux Kernel Image (uncompressed) Data Size:3329892 Bytes = 3.2 MiB Load Address: 80008000 Entry Point: 80008000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... Uncompressing Linux... done, booting the kernel. [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 2.6.39+ (koen@dominion) (gcc version 4.5.3 (GCC) ) #2 Thu May 26 17:18:00 CEST 2011 [0.00] CPU: ARMv7 Processor [411fc083] revision 3 (ARMv7), cr=10c53c7f [0.00] CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache [0.00] Machine: OMAP3 Beagle Board [0.00] Beagle expansionboard: zippy [0.00] Reserving 12582912 bytes SDRAM for VRAM [0.00] Memory policy: ECC disabled, Data cache writeback [0.00] OMAP3430/3530 ES3.0 (l2cache iva sgx neon isp ) [0.00] SRAM: Mapped pa 0x4020 to va 0xfe40 size: 0x1 [0.00] Clocking rate (Crystal/Core/MPU): 26.0/332/500 MHz [0.00] Reprogramming SDRC clock to 33200 Hz [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 61952 [0.00] Kernel command line: console=ttyO2,115200n8 mpurate=auto buddy=zippy camera=lbcm3m1 vram=12M omapfb.mode=dvi:640x480MR-16@60 omapdss.def_disp=dvi root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait [0.00] PID hash table entries: 1024 (order: 0, 4096 bytes) [0.00] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) [0.00] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) [0.00] allocated 1048576 bytes of page_cgroup [0.00] please try 'cgroup_disable=memory' option if you don't want memory cgroups [0.00] Memory: 244MB = 244MB total [0.00] Memory: 239680k/239680k available, 22464k reserved, 0K highmem [0.00] Virtual kernel memory layout: [0.00] vector : 0x - 0x1000 ( 4 kB) [0.00] fixmap : 0xfff0 - 0xfffe ( 896 kB) [0.00] DMA : 0xffc0 - 0xffe0 ( 2 MB) [0.00] vmalloc : 0xd080 - 0xf800 ( 632 MB) [0.00] lowmem : 0xc000 - 0xd000 ( 256 MB) [0.00] modules : 0xbf00 - 0xc000 ( 16 MB) [0.00] .init : 0xc0008000 - 0xc003d000 ( 212 kB) [0.00] .text : 0xc003d000 - 0xc062c7ec (6078 kB) [0.00] .data : 0xc062e000 - 0xc0679900 ( 303 kB) [0.00] NR_IRQS:410 [0.00] IRQ: Found an INTC at 0xfa20 (revision 4.0) with 96 interrupts [0.00] Total of 96 interrupts on 1 active controller [0.00] omap_hwmod: gpt12_fck: missing clockdomain for gpt12_fck. [0.00] OMAP clockevent source: GPTIMER12 at 32768 Hz [0.00] sched_clock: 32 bits at 32kHz, resolution 30517ns, wraps every 131071999ms [0.00] Console: colour dummy device 80x30 [0.000244] Calibrating delay loop... 475.76 BogoMIPS (lpj=1855488) [0.044799] pid_max: default: 32768 minimum: 301 [0.045043] Mount-cache hash table entries: 512 [0.045532] Initializing cgroup subsys ns [0.045532] ns_cgroup deprecated: consider using the 'clone_children'
Re: [Angstrom-devel] Angstrom 2008 setup scripts
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 28-05-11 12:54, Maksym Parkachov wrote: Hi Developers, now, with the changes going for oe-core/oe-meta and some new version of angstrom, I wanted to ask if there is a stable branch of Angstrom setup scripts pointing to openembedded 2011.03 stable branch. Yes, that's the 'master' branch :) The general idea behind the setup-scripts is that the default gives you something that builds and works by default and make it easy to switch to more dangerous stuff. To use .dev: go into sources/openembedded and do 'git master' and change the DISTRO setting in build/conf/local.conf To use oe-core: checkout the 'oe-core' branch of the setup-scripts. regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFN4N2AMkyGM64RGpERAhmPAJ9owX03G0Q6YqO+l04Qs+aWx6VN3wCfX8CJ EAXLMEN7fuNiOIzApd4WJkI= =5UA/ -END PGP SIGNATURE- ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] BeagleBoard (C3) won't boot
(Adding beagle group to CC:) Op 28 mei 2011, om 12:46 heeft Gary Thomas het volgende geschreven: On 05/28/2011 04:35 AM, Koen Kooi wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 28-05-11 12:07, Gary Thomas wrote: I just built Angstrom via oe-core for the BeagleBoard, rev C3 (not xM) Here were my steps: $ git clone git://git.angstrom-distribution.org/setup-scripts angstrom-bb $ cd angstrom-bb $ git checkout -b local-oe origin/oe-core $ MACHINE=beagleboard ./oebb.sh config beagleboard $ MACHINE=beagleboard ./oebb.sh bitbake console-image It doesn't boot at all. I built a bootable SD from the deploy/images, including MLO and U-Boot. Here's the boot sequence (I broke in to set the console): Texas Instruments X-Loader 1.4.4ss (Jan 29 2011 - 10:54:03) That should say 1.5.0, but wouldn't cause boot problems. For reference, this is what I get on my C3: It seems like every major component (MLO, U-Boot, Linux kernel) differs between my build and yours. So what did you do differently? Why is my build so different (and not work)? I used the stock conf/local.conf - did you make any changes to it? You're right, my FAT partition was a mess, I recreated the card using OE-core built stuff, log is further below. The one change I have is this one: http://patches.openembedded.org/patch/4677/ which might explain the problems Gary is seeing, but not the problems I'm encountering. I did some more experiments with some of the boards on my desk: B6 + zippy: uboot fails with mmc, know problem. kernel 2.6.32 works kernel 2.6.37 works kernel 2.6.39 halts booting near the end (around the SR init and mmc messages) C3 (labeled 'very bad beagle' by gerald due to ehci capacitors) + zippy: uboot works kernel 2.6.32 works kernel 2.6.37 works kernel 2.6.39 works (log below) C4: uboot works kernel 2.6.32 works kernel 2.6.37 works kernel 2.6.39 halts booting near the end (around the SR init and mmc messages) C5 (preproduction sample): uboot misdetects ram as 128MiB kernel 2.6.32 works kernel 2.6.37 works kernel 2.6.39 halts booting near the end (around the SR init and mmc messages) xM-C: uboot works kernel 2.6.32 works kernel 2.6.37 works kernel 2.6.39 works So something in .39 is broken, my knee-jerk reaction is to blame the regulator setup, but I really don't know why it fails completely for Gary, not even producing output on serial. Maybe it's the overrides problem described above. Joel, can you borrow a C5 from Steve K and play around with that? Jason, can you try .39 on your C5 as well? Chase, which models are going to be tested for the sdk? In any case, it seems that my original test samples (C3 + xM-C) were an unlucky pick, since the other revisions are broken :( For rev B we can revert the mmc commit that gives the huge speedup, for C5 we'll probably need to hack x-loader to get the right amount of RAM setup. As for the kernel, I'll try to build one without all the fancy PM stuff applied. regards, Koen Texas Instruments X-Loader 1.5.0 (May 28 2011 - 09:55:17) Beagle Rev C1/C2/C3 Reading boot sector Loading u-boot.bin from mmc U-Boot 2011.03-rc1-00128-gc797785-dirty (May 28 2011 - 09:55:17) OMAP3530-GP ES3.0, CPU-OPP2, L3-165MHz, Max CPU Clock 600 mHz OMAP3 Beagle board + LPDDR/NAND I2C: ready DRAM: 256 MiB NAND: 256 MiB MMC: OMAP SD/MMC: 0 *** Warning - bad CRC, using default environment In:serial Out: serial Err: serial Beagle Rev C1/C2/C3 Recognized Tincantools Zippy board (rev 1 ) Die ID #40880003040323090d01c015 Hit any key to stop autoboot: 3 2 1 0 The user button is currently NOT pressed. SD/MMC found on device 0 reading uEnv.txt ** Unable to read uEnv.txt from mmc 0:1 ** Loading file /boot/uImage from mmc device 0:2 (xxa2) ** File not found /boot/uImage Booting from nand ... NAND read: device 0 offset 0x28, size 0x40 4194304 bytes read: OK Wrong Image Format for bootm command ERROR: can't get kernel image! OMAP3 beagleboard.org # run loaduimagefat reading uImage 3329956 bytes read OMAP3 beagleboard.org # run mmcargs OMAP3 beagleboard.org # bootm ## Booting kernel from Legacy Image at 8020 ... Image Name: Angstrom/2.6.39/beagleboard Image Type: ARM Linux Kernel Image (uncompressed) Data Size:3329892 Bytes = 3.2 MiB Load Address: 80008000 Entry Point: 80008000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... Uncompressing Linux... done, booting the kernel. [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 2.6.39+ (koen@dominion) (gcc version 4.5.3 (GCC) ) #2 Thu May 26 17:18:00 CEST 2011 [0.00] CPU: ARMv7 Processor [411fc083] revision 3 (ARMv7), cr=10c53c7f [0.00] CPU: VIPT
[Angstrom-devel] Angstrom-core machine overview
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, As of today you can configure for the following machines when using the setup-scripts for angstrom-core: am37x-evm beagleboard beagleboard crownbay crownbay-noemgd efikamx emenlow fishriver hawkboard htcdream i586 i686 jasperforest n450 nokia900 nslu2be nslu2le omap3evm omap3-touchbook omap4430-panda om-gta01 om-gta02 palmpre palmpre2 qemuarm qemumips qemuppc qemux86 qemux86-64 spartan6-lx9mb spitz sugarbay usrp-e1xx virtex4 virtex5 x86_64 If you encounter a problem with one of those machines, please check the README in the respective layer and contact the maintainer. regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFN32K0MkyGM64RGpERAuBjAKCjjQVPKwNqzmT9yCgTTGzSIRVqDACgoXN0 hlcupMmGozy0NvAGTyHeCUE= =k86K -END PGP SIGNATURE- ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Koen Kooi : narcissus: add core-eglibc config for beagleboard
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 27-05-11 16:23, Jason Kridner wrote: Does this mean we can use Narcissus with OE-core soon? The change was already applied locally, this is just the commit to roll it out to all the mirrors :) You can now build an OE-core based image on all narcissus mirrors. On May 27, 2011, at 8:49 AM, ang-...@xora.vm.bytemark.co.uk (Angstrom Git Repos) wrote: Module: narcissus Branch: master Commit: 436fce7ec6b210a9b895c5e8c192c5321907f80b Author: Koen Kooi k...@dominion.thruhere.net Date: Fri May 27 15:48:54 2011 +0200 narcissus: add core-eglibc config for beagleboard Signed-off-by: Koen Kooi k...@dominion.thruhere.net --- .../angstrom-feed-configs_1.0-r15_beagleboard.ipk | Bin 0 - 1186 bytes 1 files changed, 0 insertions(+), 0 deletions(-) diff --git a/conf/beagleboard/configs/core-eglibc/angstrom-feed-configs_1.0-r15_beagleboard.ipk b/conf/beagleboard/configs/core-eglibc/angstrom-feed-configs_1.0-r15_beagleboard.ipk new file mode 100755 index 000..16eba8c Binary files /dev/null and b/conf/beagleboard/configs/core-eglibc/angstrom-feed-configs_1.0-r15_beagleboard.ipk differ ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFN37YsMkyGM64RGpERAq+mAJ4zUmojkw+qLhpVysPWh/nbUtITPQCgpkRC vZgAgGrzhcGuZkYaggXWFp8= =uQha -END PGP SIGNATURE- ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
[Angstrom-devel] Native angstrom support in systemd!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, For people wanting to try sysvinit replacements, systemd now has native angstrom support upstream: http://cgit.freedesktop.org/systemd/commit/?id=1bd8b8184ee3bc7fc023d6d6dfb2ca99fb6612f3 One step closer to world domination :) regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFNyOKaMkyGM64RGpERAjtyAKCtfHhxGkoVV9gpT1xylVzAnl3cewCfbJKh q8Pxo4rAvqbov08s1NKLRtU= =4uUY -END PGP SIGNATURE- ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
[Angstrom-devel] Angstrom weekly changelog for meta-angstrom, 2011-04-25 to 2011-05-02
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Khem Raj (6):
angstrom-2010.x.conf: Prefer gconf to provide gconf-dbus
angstrom-core-tweaks.inc: Fix SDK build failures since SDK_NAME is
angstrom-2010.x.conf: Defined PREFERRED_VERSION for gcc-runtime-
angstrom-2010.x.conf: Set preferred version 2.6.37.2 for linux-
distro/include/uclibc.inc: Define missing PREFERRED_PROVIDERs for
angstrom-2010-preferred-versions.inc: Fix some of non existing
Koen Kooi (4):
angstrom: switch to .MM in distro version
angstrom-version: bump PE for distro version going backwards
include ${DISTRO_VERSION} in sdk tarball name
angstrom: catch up with perl version bump
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFNwWVYMkyGM64RGpERAmGsAJ9AX2EfjaN3Til53nIFxO/TcDW72wCeMDYV
NskQXaH8cX0bnpH1s48f5Io=
=GLLC
-END PGP SIGNATURE-
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
[Angstrom-devel] Angstrom weekly changelog for meta-angstrom, 2011-04-18 to 2011-04-25
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Khem Raj (2): angstrom-2010.x.conf: Lock more gcc and binutils based recipe versions conf, build-feeds, build-releases: Replace ANGSTROMLIBC with TCLIBC Koen Kooi (4): meta-angstrom: catch up with POKYBASE - COREBASE renaming e-wm-config-angstrom: add license checksum efl-nodm-image: initial add console-image-image: add dropbear -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFNuVGrMkyGM64RGpERAjENAJwJv1zm+A0W69UOJmDqEXUU5sosjgCeN1gu AaGS6VDXYJjUXgIh9EbDgns= =AQiP -END PGP SIGNATURE- ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Khem Raj : conf, build-feeds, build-releases: Replace ANGSTROMLIBC with TCLIBC
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 22-04-11 15:55, Paul Menzel wrote: Dear Khem, Am Freitag, den 22.04.2011, 08:33 +0100 schrieb Angstrom Git Repos: Module: meta-angstrom Branch: master Commit: a6d05ec5b23b2122e38771b4273d895adc0e9d8a Author: Khem Raj raj.k...@gmail.com Date: Thu Apr 21 14:15:09 2011 -0700 conf, build-feeds, build-releases: Replace ANGSTROMLIBC with TCLIBC why was this change made? What does `TCLIBC` stand for? This was done to standardize c library selection in the oe-core universe. The OE TSC discussed it yesterday, here's a transcript of the relevant bits: 22:33 +khem with current setup with angstrom we still get the problem if we convert to use LIBC instead of ANGSTROMLIBC 22:34 +koen bitbake should unexport it, no? 22:34 +khem koen: it does not it seems [..] 22:54 +khem RP__: if I remove LIBC from EXTRA_WHITELIST then I am unable to control libc selection 22:54 +khem RP__: right now I do LIBC=uclibc bitbake x 22:54 +khem or LIBC=eglibc bitbake x 22:55 +RP__ khem: I think we should go for TCLIBC for this and various other reasons 22:55 +RP__ and unexport it just to be sure The end goal is to prefix _T_ool_C_hain variables with TC to avoid conflicts with existing software (e.g. LIBC is used in perl and pcmcia-utils) and make clear that it's toolchain related. If you have any further questions and concerns, please raise them on the openembedded-core mailinglist since this topic is broader than angstrom alone. We[1] have the opportunity to fix long standing bugs like using LIBC in OE-core, but we need input from all you people to prevent us from replacing one problem with another. To summarize: 1) we want to standardize on variables 2) we want distros based on oe-core to use the standardized set 3) we would like your input on the above I hope that answers your questions. regards, Koen [1] 'We' as in 'oe-core', not 'we' as in 'angstrom' -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFNsZTnMkyGM64RGpERAlFmAKCPyiF8f9n9srh4F41JBZ7z3UtivACgqTiP o9MpWOrzzVMBOFSKWY85Fik= =gXfC -END PGP SIGNATURE- ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Broken ncurses mirrors or something else?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 13-04-11 18:13, Graeme Gregory wrote: On Wed, Apr 13, 2011 at 09:01:37AM -0700, Philip Balister wrote: On 04/13/2011 12:09 AM, Graeme Gregory wrote: Hmm, permisions on disk look ok, Ill have to bug koen when he is back from travelling to look at the apache setup. I'll kick him in person. That all sounds a bit violent for me :-( The ncurses problem should be fixed in both .dev and maintainance branch now -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFNqXeYMkyGM64RGpERAkAyAKCbKbLybPueR69RMATJBTI5B4Gu7QCgqFOO zhLVtWAJWbN95hJefCs7+Eg= =YP+S -END PGP SIGNATURE- ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Getting started with the BeagleBoard-xM problem with Boot process :-/
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 31-03-11 16:06, Gil Cohen wrote: *Hi Guys ,* * * *Two days ago I got my BeagleBoard-xM RevB, * *At first I plugged my mini usb cable to my computer for the voltage and connected the serial-to-USB converter.* *The leds blinked and turn on.* *but couldn't see any boot load, so after a day I bought a 5v power source as suggested on the manual. * *I connected again the serial-to-USB to the serial port on the BeagleBoard and powered on using 5v (Leds turned on including the red one indicating the power source).* That red LED is sadly not a PSU indicator, but the overvoltage indicator. This usually can mean 2 things: 1) your board is broken and need an RMA 2) your 5V supply delivers more than 5.4V Case 2) should be easy to work around, case 1) is slightly more involved. regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFNlKcdMkyGM64RGpERAm3VAKCR/t8rpi7Xx6VtxarAbkwXunaqewCfaEAT iDt//0cubb98VRHaekI13Us= =K2PC -END PGP SIGNATURE- ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] networking
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 30-03-11 14:30, Gary Thomas wrote: On 03/30/2011 11:07 AM, Michael Burghart wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 30.03.2011 13:04, schrieb Gary Thomas: You didn't answer the most important questions, so this doesn't help find your problems. We'd really need to know: What version (repository branch revision) of OE did you build from? What's your target hardware? Ok. Sorry. How do I find out with git? Am used to SVN and thats different. There might be simpler ways (git is an enigma) 'cat /etc/angstrom-version' is even easier and can be done on the buildhost as well. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD4DBQFNkyRYMkyGM64RGpERAiYhAJYtxZlG0tN4B0Fqy0YstDH4CsBJAKCClzi5 gXuzLbubKVIWiPrmbGG1PA== =MaCO -END PGP SIGNATURE- ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Question About Compile lighttpd
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 30-03-11 14:39, Nuno Cardoso wrote: Hi list, Is it possible you send me the steps needed o compile lighttpd and lighttpd modules for angstrom distro running on BeagleBoard XM? They are already compiled and available in the feeds, but if you insist on building your own: http://www.angstrom-distribution.org/building-angstrom I'm using angstrom toolchain to compile it (http://www.angstrom-distribution.org/toolchains/). I use the angstrom-2011.03-i686-linux-armv7a-linux-gnueabi-toolchain.tar.bz2 toolchain. Is this right for BeagleBoard XM? Thanks, Nuno Cardoso. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFNkyrUMkyGM64RGpERAnAlAJ0TS6wrgqW2CCDHf1fcHHaKbZVcRgCfRupL 1VvKnGQEPHP6oIaUojl5KhA= =KwtK -END PGP SIGNATURE- ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Error building beagleboard-demo-image
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 17-03-11 21:27, ARTURO LOPEZ wrote: I am new using Linux. I have already copied the beagleboard_demo_image from http://www.angstrom-distribution.org/demo/beagleboard and works well in Beagle c4. I followed instructions from http://www.angstrom-distribution.org/building-angstrom and I have generated the X11 image; however, when I try to generate the beagleboard_demo_image like this: MACHINE=beagleboard ./oebb.sh bitbake beagleboard-demo-image I find this error: NOTE: package networkmanager-0.8.1-r2: task do_compile: Failed did I missed something? That is a known problem and we are testing a fix. For people who want the fix right now, pull the commits from http://dominion.thruhere.net/git/cgit.cgi/openembedded/log/?h=2011.03-maintenance Those should get merged into the main maintenance branch early next week. regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFNiyVKMkyGM64RGpERAuAKAJ0d6znAkIKxk1YFtnnXoBhWteh8bgCfa2G1 Y7fL6zqF/YHoyRaI2YIbv8U= =8yHG -END PGP SIGNATURE- ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
