-
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
On 17.09.2012 07:22, David H. wrote:
On 09/17/2012 12:48 AM, Paul Eggleton wrote:
Booting Linux image
Uncompressing Linux... done, booting the kernel.
this looks like the kernel has booted normally, maybe you have no or
just some broken rootfs?
The thing is since it is passing console=ttyS0
-
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
%
(distro,pkgnm, blacklist))
+
+}
+
What's wrong with blacklist.bbclass in OE-Core?
Cheers,
Paul
-
Paul Eggleton
Intel Open Source Technology Centre
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org
or indeed the Yocto Project autobuilders).
Cheers,
Paul
-
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
/htcuniversal/Kernel/
Otherwise I may have a tarball of the source somewhere, if I can find it I
would be more than willing to send it to you.
Cheers,
Paul
-
Paul Eggleton
Intel Open Source Technology Centre
___
Angstrom-distro-devel mailing list
Angstrom
with Javascript and builting websites, but I'd
certainly like to.
Cheers,
Paul
-
Paul Eggleton
Intel Open Source Technology Centre
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman
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
as we
decide what we want and where we want it.
Thoughts?
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
-
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
Koen Kooi wrote:
Op 26 jul. 2011, om 17:16 heeft Paul Eggleton het volgende geschreven:
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
On Mon, 05 Apr 2010, Koen Kooi wrote:
compiled, but untested kernel at:
http://dominion.thruhere.net/koen/OE/hx4700/
Doesn't seem to get very far - the last normal message I see is Waiting 10sec
before mounting root device... and then the cursor just sits there blinking.
After a minute or
(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 button for this
device, however the keycode received when the record button is pressed is 89
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 a problem for Zaurus
devices currently requiring the 2.6.26 kernel, not to mention iPAQs
On Mon, 14 Sep 2009, Michał Skuza wrote:
Has anyone succeeded running Angstrom on Asus A730? I'we build the
opie-image-asus730.tar, following the guide on
http://www.angstrom-distribution.org/building-angstrom. It is
booting with help of hret and displays screen tap the screen to
continue.
Zimler Attila Tamás wrote:
Finally I was able to try this because hackndev's git repository was
downloadable. I patched my preferred-opie-versions-1.2.4.inc file
(because I switched to it in my conf). I noticed from these patch
snippets that there is newer than 1.2.3. (Also tried the 1.2.3
Zimler Attila Tamás wrote:
I masked out all bluez4 recipe and it turned out that
DISTRO_BLUETOOTH_MANAGER is the source for the problem. When I changed
it from bluez4 to bluez-utils, opie-image compiles correctly. But this
change is in opposite direction as Koen changed it on 2009. march 31.
On Mon, 04 May 2009, frank A. Schneider wrote:
After an upgrade of udev a couple of days ago I had this same problem
(on the akita)
I copied /etc/init.d/udev from a backup and the system boots.
Indeed. After I reverted OE commit 5677ff24dfa105e2aaee777c1652fb1a66c1e7a5
(udev 124: add cache
On Tue, 28 Apr 2009, Koen Kooi wrote:
http://cgit.openembedded.net/cgit.cgi?url=openembedded/commit/id=4c992cda6
fe8a9c421d55efe80362a45be5b917e
If people can give that a spin we can move it to stable/2009.
OK, I can now confirm this works well on my spitz.
Cheers,
Paul
On Tue, 28 Apr 2009, Koen Kooi wrote:
http://cgit.openembedded.net/cgit.cgi?url=openembedded/commit/id=4c992cda6
fe8a9c421d55efe80362a45be5b917e
If people can give that a spin we can move it to stable/2009.
I was in the midst of producing a similar patch myself. However, I have been
held up
On Sat, 25 Apr 2009, Graeme Gregory wrote:
We gave up trying to squeeze in the kernel and now everyone pretty much
uses kexecboot to boot the zaurus machines. So OE generates kernels
which are now too big.
OK, thanks everyone - the kexecboot kernel worked perfectly on my spitz. So I
guess
Hi all,
In a recently built Angstrom image on my spitz I noticed that tskeys was
taking up 70% CPU. Upon closer examination I found that tskeys was reporting
that it could not use the touchscreen input device, which is configured to be
/dev/input/event1 in /etc/zaurusd/mach-config-vars. I
Hi all,
Just a reminder since development of the h3600 kernel seems to have been
revived (yay :) - I have two h3800 series devices (one h3870 with bt, one
h3850 without) and an h3600 with broken battery, free to anyone who is
interested in working on the kernel. They come with UK power
On Thursday 02 October 2008, I wrote:
I'd like to raise some interest in finishing off the 2.6 kernel support for
the iPAQ h3600 arch (AKA sa, including h3600, h3700 and h3800 series
devices), based upon what's already in the handhelds 2.6 tree. I'm prepared
to offer at least one free device
On Sunday 21 September 2008, Koen Kooi wrote:
What would be a good time to bump to r19 and upload them for testing? I
guess the opie dudes get to pick the date since they are doing most of
the work for 2007.12 nowadays :)
Could we do an r19 at least for c7x0? The Opie startup bug on that
Hi all,
I'd like to raise some interest in finishing off the 2.6 kernel support for
the iPAQ h3600 arch (AKA sa, including h3600, h3700 and h3800 series
devices), based upon what's already in the handhelds 2.6 tree. I'm prepared
to offer at least one free device to a keen kernel hacker who'd
Junqian Gordon Xu wrote:
The added packages (mostly user requested) are documented here [1]. More
opie applications will be added during the week.
FYI everything marked with [2] in the page linked below is ready to be
added to the stable autobuilder (and therefore the feed) as far as I'm
Junqian Gordon Xu wrote:
On 09/21/2008 03:37 PM, Koen Kooi wrote:
What would be a good time to bump to r19 and upload them for testing? I
guess the opie dudes get to pick the date since they are doing most of
the work for 2007.12 nowadays :)
blueligthing and I think Sep/29 (before the opie
On Sunday 21 September 2008, you wrote:
Thinking outside the box for a moment: you could use qvfb[1] inside an
X11 session to run opie or opie apps.
Actually that's a great idea, perhaps someone could test it?
Cheers,
Paul
___
Angstrom-distro-devel
On Sunday 21 September 2008, Koen Kooi wrote:
Actually, autobuilders are the gatekeepers for the feeds. If you add
something to the build-feeds.sh script the autobuilder will build and
upload it. A cronjob at the server runs the sorting script every 4 hours.
You can of course instruct
On Sunday 21 September 2008, Koen Kooi wrote:
It lists the feeds in which the package is present, so I don't see a
reason not to include the feeds. Especially considering people are
actively using 2008.x images.
Ah right, I wasn't aware of that.
Cheers,
Paul
On Saturday 20 September 2008, Koen Kooi wrote:
The split is quite easy: documentation that has been checked to be true
is on the website, the wiki is only there for documentation to mature
and get moved to the website.
Documentation in the wiki is *temporary*.
I'm not sure I agree with this
Bernhard Guillon wrote:
There was one time a huge amount of opensource software available for
opie. Lets search it and put everything on the Angstrom feeds :).
Agreed :) I have already tested a few packages in .dev and fixed some
issues. Of course things have to go into the feeds through the
Hi all,
What is the feed update policy and procedure exactly? It would be nice to
have this written out somewhere (ie, on the wiki).
Thanks,
Paul
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
On Tuesday 16 September 2008, Koen Kooi wrote:
Not really an answer to your question, but look in contrib/angstrom,
that has all the scripts the autobuilder and feed server use.
Well mostly I found that it's covered by the AngstromBackports page, and I was
aware of the scripts - the only thing
On Sunday 07 September 2008, Paul Eggleton wrote:
Well, should I move the images across then? Or do we want to wait for more
testing?
If noone objects, tomorrow evening I will move the images across for the
remaining machines, and we can finally declare Opie as supported.
Cheers,
Paul
On Friday 05 September 2008, I wrote:
Having just had a response from Paul S. it would seem that all of his
machines are no longer mentored either due to lack of time, unless
someone else steps up. So your plan gets +1 from me, although some testing
would be very helpful if there are people
On Wednesday 03 September 2008, Koen Kooi wrote:
I think going back to the good-old dumping untested stuff in releases
would actually be an improvement over the current mentor apathy.
Having just had a response from Paul S. it would seem that all of his machines
are no longer mentored either
Hi there,
Are there mentors for these machines? If so could their names be added to the
machine mentors page [1] ? If there is a lack of such a person, who decides
about the suitability of images to be made stable for those machines?
Cheers,
Paul
[1]
On Saturday 30 August 2008, Koen Kooi wrote:
Koen?
Don't look at me, machine mentors are supposed to move supported
images they have tested to the release dir.
OK, fair enough. Aren't you the h2200 hx4700 machine mentor though?
Cheers,
Paul
___
Hi Michal,
On Friday 08 August 2008, Michal Poplawski wrote:
I've tested -r18 image on h3970 and kernel panics before mounting root on
device 0,255. Will try with -r17 and see what's going on with it.
Any news on this?
Cheers,
Paul
___
On Tuesday 05 August 2008, Koen Kooi wrote:
New images, including opie-images have been uploaded. If people report
back their experiences to this list (or the user list if that's less
scary) we can move them to the release area.
Tested spitz, most stuff is working OK. There are a number of
On Tuesday 05 August 2008, Koen Kooi wrote:
New images, including opie-images have been uploaded. If people report
back their experiences to this list (or the user list if that's less
scary) we can move them to the release area.
Thanks. I tested the h2200 opie image and everything seems to be
On Tuesday 22 July 2008, Junqian Gordon Xu wrote:
I can think of testing many peripheral packages, such as zbedic,
zroadmap, qpegps ... after Opie 1.2.3 is declared supported. Great...
Agreed, those would be very nice to have in a fully working state.
Btw, how's the talk about
On Wednesday 23 July 2008, Bernhard Guillon wrote:
One thing I was not able to debug is that the close button is not
visible and at the lower left there is a clickable keyboard icon but I
cannot see it (see this screenshot [1]) .
Hmm, there's something odd going on there. I'm not sure whether
Hi all,
I'd like to request that Opie 1.2.3 be declared supported in Angstrom stable.
Most of the showstopper bugs previously identified have been fixed, and I'd
like the chance to move onto and finish 1.2.4 for eventual inclusion. In
addition I stand ready to provide the necessary support for
Hi Ian,
On Friday 23 May 2008, Ian Bonham wrote:
1 Sync, Is there a recommended way of using Opie with a Desktop to sync
Contacts, Email, Notes, and so on? I've decided to try Opie as I like the
PIM apps, and GPE was always a nightmare to try to get working, so is there
a simple way to sync
On Sat, 12 Jan 2008, Koen Kooi wrote:
Wsn't the whole point of this that opie would be uspported :)
That's the goal yes :)
It follows the same pattern as all images:
* autobuilder uploads to unstable/autobuild
* machine mentors tests images
* machine mentors move working images to
On Sat, 12 Jan 2008, Ian Bonham wrote:
Opie testing image installed and running fine on SL-C3000.
Will tinker about, but wanted to advise the autobuild worked fine for this
machine
Great :)
One question - when you rotate the screen, do the cursor keys work properly,
i.e. are they rotated to
On Sun, 13 Jan 2008, Ian Bonham wrote:
I've just rebooted it from cold (battery reset switch), and immediantly
opened a shell before doing anything else. It's open in landscape, as a
clam shell unit, with the keyboard available. I typed in '123456' as a junk
line and hit enter to put something
On Sun, 13 Jan 2008, Bernhard Guillon wrote:
I tested the new Opie image from autobuilder on SIMpad.
Qpe does not start because qcop is not working.
See also Bug # 3681 .
OK, thanks for the report. It could be that someone more familiar with the
Simpad has to look at fixing this one. Any
On Sat, 12 Jan 2008, Koen Kooi wrote:
This first batch of opie images is being uploaded by the 2007 autobuilder.
Great, I see they have appeared (in unstable/autobuild/ for those who are
unfamiliar with the Angstrom website structure as I was a short time ago). So
should I copy these to
Hi there,
Attached is a patch to add Opie to the autobuilder script. It adds a separate
block to build opie-image for just those machines that are supported in Opie
at the moment. I know this is a lot of images to build, but we do want a wide
range of testers. I'm not sure if we should really
Koen Kooi wrote:
+1 under one condition: remove the merge_feeds crap from opie image
recipes. Opie has no business poking in operating system files that are
under packagemanagement. Furthermore, /etc/ipkg/* will be re-populated
once people do 'ipkg upgrade', so you're back to square one.
Hi there,
I would like to propose applying two important Opie patches previously applied
by Paul S. to .dev to the stable branch. They are as follows:
1) http://bugs.openembedded.org/attachment.cgi?id=3197
This corrects a path so that the Opie first run wizard works again (see bug
#2875 for
Paul Sokolovsky wrote:
Yes, and to have them applied, I need to know .dev revisions, to
cherry-pick them into stable branch.
Oh, right, now I understand, sorry.
Also, FYI, OE viewmtn is returning internal server error at the
moment.
Ok, I'll dig them myself then.
Just in case you
Hi all,
Please review the attached simple patch to add
preferred-opie-versions-1.2.3.inc to angstrom-2007.1.conf. As far as I can
see, this is required if we are to be able to build Opie images using
autobuilder scripts as is required by current policy.
This needs to go into the stable branch
Todd Blumer wrote:
SDG Systems will have one person available 10-20 hours per week to
help with the Opie work. We will help to support the hx4700, and our
TDS products. They will begin helping later this week.
Wow, that's fantastic news! :) As Koen suggests, please let me know how we
can best
58 matches
Mail list logo
