-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11-03-11 03:34, Brian Hutchinson wrote:
Hi,
I have a TI c6a816x-evm board. These things come with Arago.
Just install angstrom. Arago lacks NEON and VFP support and uses
outdated C libraries.
Apparently Arago doesn't have many -dev
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02-03-11 13:28, Koen Kooi wrote:
Hi,
With the 2011.3 release of OE we are taking the opportunity to retire
angstrom 2008.1 into a maintenance branch, which is going to created
soon, and move ahead with 2010.x in openembedded-core
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
People can now access the angstrom feeds using:
feeds.angstrom-distribution.org
with mirrors at
us.feeds.angstrom-distribution.org
eu.feeds.angstrom-distribution.org
In the near future feeds.angstrom-distribution.org will start rotating
org.openembedded.dev before the
end of this month.
Your friendly Angstrom maintainers,
Graeme 'Xora' Gregory
Koen Kooi
Philip 'Crofton' Balister
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFNbjgGMkyGM64RGpERAuFpAKCWLxDSNxKL8QBk6kFGXb9Crwk+LgCfXNO/
ceHJGwJ2itYh2Vubew6xlj8
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 28-02-11 02:46, Bob Feretich wrote:
Is base-image still a supported Angstrom image for the BeagleBoard?
I have just migrated from a two year old version of OE/Angstrom and was
able to build nano, but building base-image (the image I previously
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19-02-11 20:28, Jonathan Wilson wrote:
Bitbake bombs out with:-
ERROR: Build
of
/home/wilsonjonathan/oebeagle/angstrom-setup-scripts/sources/openembedded/recipes/gnome/pyorbit_2.24.0.bb
do_configure failed
ERROR: Task 8977
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 20-02-11 17:05, Jonathan Wilson wrote:
On Sun, 2011-02-20 at 09:14 +0100, Koen Kooi wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19-02-11 20:28, Jonathan Wilson wrote:
Bitbake bombs out with:-
ERROR: Build
of
/home
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12-02-11 15:57, Gary Thomas wrote:
the Angstrom web pages (most links on that page are broken BTW).
Which ones are broken? The ones I used a few hours ago were working.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Darwin)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12-02-11 15:57, Gary Thomas wrote:
I know that Koen is working on building Angstrom using the
Yocto/Poky framework. I don't see any mention of this on
the Angstrom web pages (most links on that page are broken BTW).
Is this work something
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12-02-11 16:47, Koen Kooi wrote:
On 12-02-11 15:57, Gary Thomas wrote:
I know that Koen is working on building Angstrom using the
Yocto/Poky framework. I don't see any mention of this on
the Angstrom web pages (most links on that page
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 30-01-11 19:04, Robert M. Kenney wrote:
I've tried several times to get the build system to generate jffs2
images for my IPAQ H5455, but without any success.
Select machine: h5000
Complexity of options: advanced (so you can select jffs2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 30-01-11 21:24, Caglar Akyuz wrote:
On Friday 28 January 2011 10:09:15 am Koen Kooi wrote:
On 28-01-11 08:25, Caglar Akyuz wrote:
Hi all,
I'm compiling Angstrom 2010.x against commit:
commit d10ef750c59ee954c11a8edd0e278f99dbf2816a
Author
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 28-01-11 08:25, Caglar Akyuz wrote:
Hi all,
I'm compiling Angstrom 2010.x against commit:
commit d10ef750c59ee954c11a8edd0e278f99dbf2816a
Author: Khem Raj raj.k...@gmail.com
Date: Mon Jan 24 01:06:08 2011 -0800
Machine is custom
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
The meta-angstrom layer for yocto was split out into its own repository,
so for people using that, they need to update their setup scripts and
bblayer.conf
The conf/bblayer.conf is quite simple:
- -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 17-01-11 20:10, Maksym Parkachov wrote:
Hi,
I'm trying to compile gstreamer-ti for the angstrom-2010.x distro
and beagleboard machine on yesterday's checkout from openembeded.
The compile step is returning an error
You've found out why
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 13-12-10 22:22, Darren wrote:
Hi,
I'm new to open embedded and Angstrom. I recently purchased an Overo Fire
and
have been struggling for about a week trying to get an Angstrom image with
OpenGL to work. Still not there, but hopefully
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07-12-10 15:37, Philip Balister wrote:
I'm looking for a way to point people at a relatively sane checkout of
the OE dev for people using a product based on Angstrom 2010.
short version:
cat /etc/angstrom-version
-BEGIN PGP SIGNATURE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07-12-10 16:39, Gary Thomas wrote:
On 12/07/2010 08:32 AM, Koen Kooi wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07-12-10 15:37, Philip Balister wrote:
I'm looking for a way to point people at a relatively sane checkout of
the OE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07-12-10 17:15, Philip Balister wrote:
On 12/07/2010 11:12 AM, Koen Kooi wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07-12-10 16:39, Gary Thomas wrote:
On 12/07/2010 08:32 AM, Koen Kooi wrote:
-BEGIN PGP SIGNED MESSAGE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Please follow the instructions on the angstrom website instead of doing
random things.
On 15-11-10 09:21, Sriram Chadalavada wrote:
Hi everyone,
Here is what I am trying to do:
@ubuntu:~/Projects/Mediabox_DRM/angstrom-setup-scripts$
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I suspect /home/mobilgenie/Mediabox_DRM/ is a symlink to somewhere.
Change that to a bind mount and you should be fine
On 09-11-10 08:09, Sriram Chadalavada wrote:
Hi everyone,
I earlier tried bitbake -b option but that gave autoreconf --exclude
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 22-10-10 10:29, Petr Štetiar wrote:
Thibault Jochem thibault.joc...@amundis.fr [2010-10-22 10:07:08]:
We broke the 1TB per month barrier and now the ISP is throttling us to
10Mbit/s. The admins are working on solving this, but it might be a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 22-10-10 19:26, Petr Štetiar wrote:
Koen Kooi k.k...@student.utwente.nl [2010-10-22 12:18:37]:
The limitting got fixed, but ltg is hosting some big android download
that is suffering from the slashdot effect :(
Well, I don't know
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 21-10-10 16:50, Thibault Jochem wrote:
With the simpified setup, i'm issuing this message twice when trying to build
some packages (tried with machine configured as beagleboard or as igep0020) :
ERROR: no recipe files to build, check your
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 20-10-10 01:14, Ash Charles wrote:
Hi,
I've built an Angstrom 'console-image' using a recent git pull from
openembedded master for a PXA255 board booting off a compact flash
card. The kernel boots but init gets stuck after spewing these
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
We broke the 1TB per month barrier and now the ISP is throttling us to
10Mbit/s. The admins are working on solving this, but it might be a case
of wait for the month to end.
Stay tuned...
regards,
Koen
-BEGIN PGP SIGNATURE-
Version:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 16-09-10 17:55, toma...@volny.cz wrote:
Look in contrib/angstrom for the personal feed
script, that works loads
better.
Where is it? I can't find it.
http://gitorious.org/angstrom/openembedded/trees/org.openembedded.dev/contrib/angstrom
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 16-09-10 15:06, Caglar Akyuz wrote:
On Thursday 16 September 2010 03:24:16 pm Tomáš Franke wrote:
Hi
It is possible to make the private mirror of Angstrom repository?
Do you mean the package repository? If yes, all you need to do is to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
If you're building a Qt app I would strongly advise using qmake. If
you're not building a Qt apps I would strongly advise dropping cmake,
it's horrible. CMake wasn't designed to support crosscompiling and that
shows :(
Since you seem to have a OE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02-09-10 00:36, gd...@xmlink.net wrote:
git clone git://gitorious.org/angstrom/angstrom-setup-scripts.git
cd angstrom-setup-scripts
sh oebb.sh config beagleboard
sh oebb.sh update
source ~/.oe/environment
MACHINE=beagleboard bitbake
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 23-07-10 20:27, Robin Cao wrote:
Hi,
I'm trying to build Angstrom image for Beagle board using simplified
development setup
(http://www.angstrom-distribution.org/simplified-development-setup).
The following is my steps:
1) git clone
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 21-07-10 20:30, David Peters wrote:
This may be a simple question, but I've searched everywhere I can think of to
find an answer.
I can see the package angstrom-task-gnome_1.0-r13.5_all.ipk in the Angstrom
feed browser. I assume this package
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Please don't top post.
On 12-07-10 00:21, Yann Vernier wrote:
A patch? The bugfix release upstream has fixed the problem.
All that needs to be done is update Ångström to the new upstream - the
bugfix release 1.13.4 if you don't want any new
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Care to make a patch and test it?
On 11-07-10 18:21, Yann Vernier wrote:
Found by u42p in #openpandora (Pandora is a Linux handheld which runs
Ångström): Ctrl+C causes sh, when running a simple script (below), to
fork uncontrollably.
The
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I already have this change locally :) I need to test some more before I
push it. And for the kaelios change, Marco with copy our changes without
attribution in a week or so.
regards,
Koen
On 09-07-10 21:47, Stanislav Brabec wrote:
Proposal to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
The good people from BUGlabs and Tarent have a patch for gcc that will
give is more atomic builtins for ARM, which is awesome, but it does
require rebuilding large parts of userspace, so DISTRO_PR will be
increased soon after the patch lands.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 25-06-10 01:09, Gregoire Gentil wrote:
Out of the 40 commits done on 6/24, there are a few recipes/patches that
would deserve to be pushed upstream,
Please send patches for those to here and/or openembedded-devel.
regards,
Koen
-BEGIN PGP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10-06-10 07:01, Maxim Podbereznyy wrote:
Hi All!
I've built the OE (Angstrom) and did not enabled rm_work feature in
local.conf. Now I have all necessary binaries but the whole OE directory
takes 15G of HDD space.
Is it possible to clean
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Both build fine for me
On 09-06-10 18:07, Robert P. J. Day wrote:
sounding like a broken record but it's been literally weeks since
either of firefox or abiword actually built when i'm trying for a
beagleboard/angstrom image.
i'm about to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02-06-10 12:48, Robert P. J. Day wrote:
On Wed, 2 Jun 2010, Martin Jansa wrote:
On Wed, Jun 02, 2010 at 06:08:22AM -0400, Robert P. J. Day wrote:
since this is the first time i actually built an image with any of
the downloadable TI stuff,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02-06-10 15:45, Robert P. J. Day wrote:
Make it clear in that include file that the user must manually create
the MD5 checksum file.
NAK. As I said before, those go into the README
Signed-off-by: Robert P. J. Day rpj...@crashcourse.ca
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You can 'fix' this problem by doing 'bitbake glibc', that will make
packaged-staging overwrite the bogus header. I'm looking into a proper
fix for this.
regards,
Koen
On 20-05-10 17:27, Sergey Lapin wrote:
Hi, all!
bash fails to build from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 20-05-10 03:29, Gary Thomas wrote:
Can't build 'beagleboard-demo-image' in today's tree :-(
MACHINE=beagleboard
DISTRO=angstrom-2008.1
OE Branch = org.openembedded.dev
commit 81a3db27c33d87401b33362c58f26ad69e2d7b4e
ERROR: QA Issue with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12-05-10 20:17, Francesco Lamonica wrote:
Hi all,
i think ther emight be a bug in the aforementioned recipe file
sinec it basically tries to apply non-existent patch files (6,8 and 10)
while the old 0006 patch can still be applid if ported from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10-05-10 16:15, Maxim Podbereznyy wrote:
Hi All!
I'm working with OE stable branch and want to add support for a new board.
I've always created local patches for OE but now wish to enable my board at
the public repository. I have changes for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 29-04-10 13:37, Maxim Podbereznyy wrote:
Hi All!
I have successfully built Angstrom-stable for one board. Now I have such
files tree:
m...@maxx-desktop:~/OE$ pwd
/home/maxx/OE
m...@maxx-desktop:~/OE$ ls
angstrom-dev build downloads
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 22-04-10 09:26, Koen Kooi wrote:
Hi,
The angstrom standalone toolchains have been updated:
http://www.angstrom-distribution.org/toolchains/
The new ones are for x86_64 hosts, but support for i686 hosts will
follow later (my 32bit machine
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Since a few weeks the code for various angstrom infrastructure (e.g.
setup scripts, narcissus, feedbrowser) is hosted on gitorious at
http://gitorious.org/angstrom/
If you want to contribute to those, drop us a line (e.g. send a mail to
the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 20-04-10 18:00, Martyn Welch wrote:
Koen Kooi wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19-04-10 10:21, Piyush Verma wrote:
Hello Friends
After lots of efford finaly I compile x11-gpe-image.
Everything goes well.
While
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 20-04-10 21:56, Lee, Charles (VWoA-ERL) wrote:
Hello,
I'm trying to compile a driver for Angstrom/Beagleboard. It comes with a
standard Makefile, but the catch is that it needs configured kernel
sources. From my driver's documentation
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19-04-10 10:21, Piyush Verma wrote:
Hello Friends
After lots of efford finaly I compile x11-gpe-image.
Everything goes well.
While booting it display Linux Logo on screen.
But after this message Starting GPE display manager: gpe-dm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19-04-10 12:00, Bernhard Guillon wrote:
Koen Kooi wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Some devices don't function properly when using a recent udev on an old
kernel, so udev will now try to fall back to an older version
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 17-04-10 22:38, Håkon wrote:
Hi,
I hope this is the right place to report this;
The package browser at http://www.angstrom-distribution.org/repo/ is
not working correctly for me in Opera.
This seems to be caused by malformed HTML. Some
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
No comments - applied
On 15-04-10 15:03, Koen Kooi wrote:
The angstrom mailserver seems to be dropping a lot of mails, so let's
see if try 7 gets thru:
-Original Message-
From: Maupin, Chase
Sent: Wednesday, April 14, 2010 9:02 AM
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 15-04-10 14:14, Andrea Adami wrote:
Hello,
I recently built for armv4 EABI (collie) and this pulled in gcc_4.4.2
(and binutils_2.20).
I see these are the defaults in sane-toolchain.inc, however e.g.
Angstrom-2008.1 doesn't include that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08-04-10 23:51, Paul Menzel wrote:
It would be great, if you added Enna, so that it is easy for people to test.
I hope, that the dependencies will be pulled in automatically.
It's in the unstable feeds now for armv7a, armv5te and armv6 will
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09-04-10 23:02, Paul Menzel wrote:
Thank you for giving me a chance to understand how all the tools work
together. I hope this patch is what you had in mind.
Thanks! Applied:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08-04-10 08:54, fat03...@newmail.ru wrote:
Dear Angstrom community,
I am trying to write small kernel module for Angstrtom on Beagleboard.But
found that my version of Angstrom doesn't have insmod utility.Could you
please give advise how to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07-04-10 00:22, viktor vraniak wrote:
That shouldn't be a problem. For which architecture do you want it?
i have this device http://www.handhelds.org/moin/moin.cgi/HpIpaq214
and i am using this repository
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06-04-10 18:13, Viktor Vraniak wrote:
hi all
first i want to thanks for your work on this distro.
my question is, if is possible to add package for owfs (1-wire
filesystem - http://owfs.org )
That shouldn't be a problem. For which
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04-04-10 23:33, Paul Eggleton wrote:
(oops, sent to angstrom-distro-users first by mistake...)
Hi all,
I've been looking into why the record button doesn't work in Opie on the
hx4700 (and probably h4000). Opie expects F24 to be the record
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 24-03-10 17:29, Matt Soffen (Angstrom) wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Internally at TI we have various scripts to make setting up an angstrom
buildtree easier and I adapted the shell one (I don't do perl, sorry
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 20-03-10 15:40, Daniel Poirot wrote:
On Sat, Mar 20, 2010 at 9:22 AM, isaac smith hunterne...@gmail.com wrote:
It looks more like a platypus trying to look like Tux to me... ;) I
guess I should've done more searching before I posted. I guess my
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08-03-10 05:09, Aruna Dissanayaka wrote:
Hello all,
Can any of you tell me why I get the following message on Serial console
while loading graphical utilities on x11-image? In additon it takes so much
time to load. Please help me to solve this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06-03-10 21:31, Jon wrote:
Please disregard my last email.
regarding
http://www.angstrom-distribution.org/feeds/2008/ipk/glibc/armv7a/base/libgcc1_4.3.3-r1.1_armv7a.ipk
Im new to linux, so Im still trying to learn, as well as test out packages
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19-02-10 04:33, shiyou yu wrote:
The new angstrom use Xorg as Xserver, not the old kdrive, so you can't
calibrate it using tslib, you must use a Xserver calibrate way like
xinput-calibrater. The newest angstrom haven't update it, so you must
do
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 18-02-10 09:52, Tejas wrote:
Hi All,
I want to use Ti's Plugins in gstreamer. For that I need cmem
option available and memory available for dsp. Any one has root file system
and UImage for the same.
opkg install
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 18-02-10 05:58, Tejas wrote:
Hello All,
I am not able to access unstable source directory on
http://www.angstrom-distribution.org/unstable/sources/
I am trying to do bitbake of gstreamer-ti and getting
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Now that packaged-staging seems to be working again, I think it's time
we come up with some infrastructure to leverage it properly for angstrom.
I was thinking about a workflow like this:
Autobuilders:
* build console-image for your favourite
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10-02-10 10:52, Martin Jansa wrote:
On Tue, Feb 09, 2010 at 04:05:14PM +0100, Koen Kooi wrote:
Hi,
Hi,
I've started working on cleaning up the udev recipe as well as making it
build the 'udev-extra' required for modern applications
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10-02-10 12:18, Maxim Podbereznyi wrote:
Hi guys!
I have own board based on AT91SAM9263-EK design and connect 7 LCD with
touchscreen. The LCD resolution is 800x480px. When Angstrom starts it asks
me to calibrate the TS, I do it. Then I can't
accel, why do you keep
complaining it's slow?
-Tejas.
-Original Message-
From: angstrom-distro-devel-boun...@linuxtogo.org
[mailto:angstrom-distro-devel-boun...@linuxtogo.org] On Behalf Of Koen Kooi
Sent: Monday, February 08, 2010 4:05 PM
To: angstrom-distro-devel@linuxtogo.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ping
On 07-02-10 11:42, Koen Kooi wrote:
Hi,
I've started working on cleaning up the udev recipe as well as making it
build the 'udev-extra' required for modern applications.
You can track the work at gitorious:
http://gitorious.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09-02-10 16:23, John Willis wrote:
As an aside, is a platform being on Narcissus now the 'official' mark of a
platform being supported? That would narrow down the core somewhat.
It would be nice if that was the case, but it isn't. I don't think
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09-02-10 21:27, Paul Eggleton wrote:
On Sun, 07 Feb 2010, Koen Kooi wrote:
* Really doesn't work with CONFIG_SYSFS_DEPRICATED
* Needs at least kernel 2.6.27 for proper signalfd usage
Not sure about the first one, but the second will be quite
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08-02-10 06:29, Tejas wrote:
Hi All,
I have enabled totem media player while building angstrom
image from narcissus. With that image I can open totem media player on
beagle board. But when I try to play video 0f 320 X 240 , it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08-02-10 09:51, Tejas wrote:
Hi Koen,
Totem is using playbin plugin to load file and automatically it is
finding parser and decoder etc. After using --gst-debug=GST_ELEMENT_*:3 I
can say it is using following pipeline.
Decodebin !
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07-02-10 20:04, Andrea Fazzi wrote:
Hi all,
I've got issues with SGX drivers. I built an unstable task-base-extended
image for a beagleboard machine using narcissus builder checking the
PowerVR SGX drivers for OMAP3 box. However, it seems it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01-02-10 10:45, balakrishnan wrote:
Hi,
I am building stable/2009 angstrom-distro branch in open embedded.
What is my problem is I am not able to enable 'touch screen'. I have
added touchscreen value in MACHINE_FEATURES variable also.
My
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01-02-10 13:40, balakrishnan wrote:
Hi Koen, thanks for ur reply,
I have added 'xf86-input-tslib' in XSERVER variable and build the
angstrom again. Still I am not getting touch screen input.
My doubt is,
1.touch screen support is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Luca pulled most of the wiki into http://gitorious.org/angstrom-manual
so it would be nice if everyone chips in to fix all the outdated info in
the manual, since the data in the wiki was already quite stale.
It would be neat to have a .pdf or
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Either do:
'opkg update ; opkg install totem'
or use narcissus and check the Totem media player box
regards,
Koen
On 16-01-10 12:09, Tejas wrote:
Hello All,
I would like to run totem player on beagle board. I am using
On 11-12-09 22:15, Frans Meulenbroeks wrote:
http://www.angstrom-distribution.org/ contains a section Ångström 2008
glibc ipk feed updates
If I press on more I go to
http://www.angstrom-distribution.org/aggregator/sources/6 which says:
Home › News aggregator › Sources
Ångström 2008 glibc ipk
On 04-12-09 23:04, Paxton Smith wrote:
I am using the origin/stable/2009 branch and I'd like to pull my kernel
from
git://git.infradead.org/users/dedekind/ubifs-v2.6.27.git. I manually
cloned this repo then tar/bz2'd it and I have been using it as such in
my builds. However, I'd like to do it
Hi,
I'd like to build some 2.6.32 kernels with kexecboot for various
devices, is that possible already? Is ubifs support already there?
regards,
Koen
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
On 02-12-09 16:32, Séverin MARCOMBES wrote:
Hello,
I cannot find the qt4-embedded-demos on my OpenEmbedded environment.
An other idea?
Yes, stop top-posting. qt4-embedded-demos is generated by building
qt4-embedded.
--
Séverin MARCOMBES
http://severin-marcombes.fr
On Wed, Dec
On 14-11-09 10:27, Koen Kooi wrote:
Hi,
Due to debian.bbclass being broken for the past few weeks the feeds are
a bit messed up. Combined with all the staging changes in OE .dev I'd
like to propose to bump DISTRO_PR to 5 around the 23rd of november.
This would be a nice time to get rid of oabi
On 15-11-09 16:12, Koen Kooi wrote:
Hi,
Currently we are building opkg(-nogpg) against curl and curl depends on
lots of stuff (crypto-auth for one). This is creating a too big runtime
dependency chain for opkg(-nogpg). I would like to get your opinion on
the following options:
1) keep curl
On 20-11-09 10:21, Graeme Gregory wrote:
On Thu, 19 Nov 2009 09:09:51 +0100
Koen Kooik.k...@student.utwente.nl wrote:
So how are things looking?
Stuff is now building but I see there are still a number of core
changes happening so I would like to hold off another week for
stuff to settle.
On 14-11-09 12:06, Graeme Gregory wrote:
On Sat, Nov 14, 2009 at 10:27:29AM +0100, Koen Kooi wrote:
Hi,
Due to debian.bbclass being broken for the past few weeks the feeds
are a bit messed up. Combined with all the staging changes in OE
.dev I'd like to propose to bump DISTRO_PR to 5 around
On 15-11-09 16:12, Koen Kooi wrote:
Hi,
Currently we are building opkg(-nogpg) against curl and curl depends on
lots of stuff (crypto-auth for one). This is creating a too big runtime
dependency chain for opkg(-nogpg). I would like to get your opinion on
the following options:
1) keep curl
On 14-11-09 12:06, Graeme Gregory wrote:
On Sat, Nov 14, 2009 at 10:27:29AM +0100, Koen Kooi wrote:
Hi,
Due to debian.bbclass being broken for the past few weeks the feeds
are a bit messed up. Combined with all the staging changes in OE
.dev I'd like to propose to bump DISTRO_PR to 5 around
On 04-11-09 13:10, Pankaj Chawla wrote:
I followed instructions on
http://www.angstrom-distribution.org/building-angstrom
http://www.angstrom-distribution.org/building-angstromSo I guess its 2009
stable. The MACHINE is mini2440 and am doing bitbake
base-image
Are you sure? That branch doesn't
On 30-10-09 21:45, Thomas Kunze wrote:
With gcc 4.4.2 armv4 can use arm-eabi. Now we can drop the support
of the obsolete abi. This patch sets gcc 4.4.2 as preferred for armv4
devices. It was tested for collie and glibc.
What do you think?
Looks good, do we need to pass --fix-v4bx for ld and
On 26-10-09 09:41, Graeme Gregory wrote:
On Mon, Oct 26, 2009 at 09:37:20AM +0100, Koen Kooi wrote:
Hi,
To fix the fallout for the static-libs-stripping bug and to get rid
of spurious gconf-dbus deps there will be a DISTRO_PR bump soon.
When bitbake informs you of said occasion, remove TMPDIR
On 27-10-09 12:05, Robert P. J. Day wrote:
is it worth posting them, or does the OE group do a regular build
and resolve these automatically? i don't want to waste this mailing
list's time if these things are handled on a regular basis.
The rule of thumb is:
Nonfatal QA errors: don't
Hi,
To fix the fallout for the static-libs-stripping bug and to get rid of
spurious gconf-dbus deps there will be a DISTRO_PR bump soon.
When bitbake informs you of said occasion, remove TMPDIR and rebuild.
regards,
Koen
___
Angstrom-distro-devel
On 26-10-09 10:36, Robert P. J. Day wrote:
On Mon, 26 Oct 2009, Frans Meulenbroeks wrote:
2009/10/26 Koen Kooik.k...@student.utwente.nl:
Hi,
To fix the fallout for the static-libs-stripping bug and to get
rid of spurious gconf-dbus deps there will be a DISTRO_PR bump
soon. When bitbake
On 26-10-09 18:46, Thomas Kunze wrote:
Koen Kooi wrote:
Hi,
To fix the fallout for the static-libs-stripping bug and to get rid of
spurious gconf-dbus deps there will be a DISTRO_PR bump soon.
When bitbake informs you of said occasion, remove TMPDIR and rebuild.
I'd like to bump gcc
On 26-10-09 19:06, Thomas Kunze wrote:
Koen Kooi wrote:
On 26-10-09 18:46, Thomas Kunze wrote:
Koen Kooi wrote:
Hi,
To fix the fallout for the static-libs-stripping bug and to get rid of
spurious gconf-dbus deps there will be a DISTRO_PR bump soon.
When bitbake informs you of said occasion
301 - 400 of 756 matches
Mail list logo
