On 09/07/2008 08:08 PM, Dmitry Baryshkov wrote:
I've never been able to boot the 2.6.24 kernel built from oe. debug log
shows the booting stops at
...
Advanced Linux Sound Architecture Driver version 1.0.15 (Tue Nov 20
19:16:42 2007 UTC)
ASoc 0.13.1
On stable branch: after enabling
On 09/08/2008 08:13 AM, Andrea Adami wrote:
ok, so if tosa is happy with 2.6.24 please ad it to the patch here:
http://bugs.openembedded.net/attachment.cgi?id=9980
2.6.23 must really disappear...
Andrea
Not yet, waiting for testing for tosa.
Gordon
On 09/10/2008 06:03 AM, Dmitry Baryshkov wrote:
Verified with the most recent kernel from stable branch. It boots
w/o problems
on my tosa. Could you please e.g. try enabling CONFIG_DEBUG_DRIVER and check
when the kernel really stops?
Dmitry,
Did you just kexec or reflash the device to
)
--
Message: 1
Date: Thu, 11 Sep 2008 10:50:31 +
From: Anthony Callegaro [EMAIL PROTECTED]
Subject: Re: [Angstrom-devel] Machine mentors for h5000, c7x0, spitz,
tosa
To: Discussion of the angstrom distribution development
[EMAIL PROTECTED] wrote:
I am interested in providing test support for tosa.
Where can I find current image?
You can find unstable images for testing here [1].
good luck :)
Bernhard Guillon
1 http://www.angstrom-distribution.org/unstable/autobuild/tosa/
Verified with the most recent kernel from stable branch. It boots w/o problems
on my tosa. Could you please e.g. try enabling CONFIG_DEBUG_DRIVER and check
when the kernel really stops?
Hey Dmitry,
I do not have a working build environment at the moment do you think you
could provide
Junqian Gordon Xu wrote:
On 09/05/2008 03:15 PM, Dmitry Baryshkov wrote:
In principle I can test images for tosa. However I'd like to ask for
commit access to the OE repo. Last time it was necessary to fix smth I
stopped waiting for the patch to be commited after a month or so.
Dmitry,
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
ok, so if tosa is happy with 2.6.24 please ad it to the patch here:
http://bugs.openembedded.net/attachment.cgi?id=9980
2.6.23 must really disappear...
Andrea
On 9/8/08, Dmitry Baryshkov [EMAIL PROTECTED] wrote:
Junqian Gordon Xu wrote:
On 09/05/2008 03:15 PM, Dmitry Baryshkov wrote:
In
On 09/05/2008 03:15 PM, Dmitry Baryshkov wrote:
In principle I can test images for tosa. However I'd like to ask for commit
access to the OE repo. Last time it was necessary to fix smth I stopped
waiting for the patch to be commited after a month or so.
Dmitry,
Do you happen to still have a
Junqian Gordon Xu wrote:
On 09/05/2008 03:15 PM, Dmitry Baryshkov wrote:
In principle I can test images for tosa. However I'd like to ask for
commit access to the OE repo. Last time it was necessary to fix smth I
stopped waiting for the patch to be commited after a month or so.
Dmitry,
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
Le vendredi 05 septembre 2008 à 20:15 +, Dmitry Baryshkov a écrit :
In principle I can test images for tosa. However I'd like to ask for commit
access to the OE repo. Last time it was necessary to fix smth I stopped
waiting for the patch to be commited after a month or so.
I second this.
Ian Bonham wrote:
I've mentioned this before, but maybe if there was a focus on a core group
of software, that gave people a useable machine that would sync with a
desktop for contacts etc, we might start to get a bigger core of people to
Angstrom.
You assume that angstrom only targets PDAs,
Slightly OT,
I would guess we could easily gain new testers (and perhaps mentors)
adding the linux-kexecboot 'second stage bootloader' to the
autobuilder.
Boot from SD/CF/USB = quicker test, no flashing
Most of the above mentioned machines only need a final defconfig
update to match the mtd
Andrea Adami wrote:
Slightly OT,
I would guess we could easily gain new testers (and perhaps mentors)
adding the linux-kexecboot 'second stage bootloader' to the
autobuilder.
For all machines? Angstrom is more than a few zaurus machines! Can't
this made be more generic than forcing machines
[Angstrom-devel] Machine mentors for h5000, c7x0, spitz, tosa
...
Most of the above mentioned machines ...
only referring to the subject. Fell free to add 'akita'.
Andrea
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http
Koen Kooi schrieb:
Andrea Adami wrote:
Slightly OT,
I would guess we could easily gain new testers (and perhaps mentors)
adding the linux-kexecboot 'second stage bootloader' to the
autobuilder.
For all machines? Angstrom is more than a few zaurus machines! Can't
this made be more generic
Paul Eggleton wrote:
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?
In principle I can test images for
Dmitry Baryshkov schrieb:
Paul Eggleton wrote:
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?
In
Koen Kooi wrote:
I think going back to the good-old dumping untested stuff in releases
I would vote for it.
would actually be an improvement over the current mentor apathy.
I have only one spitz (terrier) machine and I want to have it usable.
Testing new image needs a lot of time for
Stanislav Brabec wrote:
I build my own tree for my experiments (see link below). I can
eventually upload my images
No, only an autobuilder may upload images, anything else is a QA nightmare.
regards,
Koen
___
Angstrom-distro-devel mailing list
On Thu, Sep 4, 2008 at 3:41 AM, Stanislav Brabec [EMAIL PROTECTED] wrote:
I have only one spitz (terrier) machine and I want to have it usable.
Testing new image needs a lot of time for re-customizing them for my
needs. That is why I don't volunteer to become a spitz mentor.
I still have my
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
I'm lost!
I've got my SL-C3000 useable (Thanks Stanislav!), but how many machines is
Angstrom trying to support now?
I just get the feeling at the moment that Angstrom is a build of
OpenEmbedded, and that build seems to be forking in many directions. I look
at the feeds and see some software
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]
Paul Eggleton wrote:
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?
I think going back to the good-old
On Wed, Sep 3, 2008 at 2:39 PM, Koen Kooi [EMAIL PROTECTED] wrote:
Paul Eggleton wrote:
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
28 matches
Mail list logo
