From: Christian Gagneraud <chgans@gna.org>
To: Denys Dmytriyenko <denys@ti.com>
Cc: meta-arago@arago-project.org
Subject: Re: [nightly] Core TISDK 2013.06 build 2013-07-21_01-01-44
Date: Tue, 23 Jul 2013 16:43:54 +1200 [thread overview]
Message-ID: <51EE0A0A.3020902@gna.org> (raw)
In-Reply-To: <20130723031524.GA30573@edge>
On 23/07/13 15:15, Denys Dmytriyenko wrote:
> Christian,
>
> On Tue, Jul 23, 2013 at 02:26:24PM +1200, Christian Gagneraud wrote:
>> Hi there,
>>
>> I have been looking at these test/build reports recently, is there a
>> more detail report available somewhere?
>
> Yes, but detailed reports are not yet published externally - it's on my
> "to do" list.
Good to hear, thanks! I have no strong needs for this, i was just
curious about the am335x-evm test failures.
>
>
>> As a user of a am335x-evm and a BeagleBoard Black, I would like to
>> know more about test failure for the EVM.
>
> There are some issues with the boot sequence of an automated test - looks
> like it's trying to load a wrong kernel image, I'll look into it later.
> Otherwise, the latest Dylan build works and boots fine for me on am335x-evm
> when loaded manually on SD card.
>
>
>> As well, I'm considering moving from Arago/Danny (kernel 3.2) to
>> Arago/Dylan (kernel 3.8?). I would like to know if there are any
>> plan to use Dylan for the next stable Arago.
>
> Actually, Arago/Danny has been using kernel 3.8 for quite some time now - we
> already had couple internal releases with it. You would need to specifically
> request AM-SDK branding to get 3.2 kernel, as the default is 3.8 in Danny and
> in Dylan. The only change Dylan brings is to update the underlying Yocto
> framework with all the user-space apps to the latest versions.
Yes, that's right, Arago/Danny already use kernel 3.8. My mistake!
To be more precise, my question was related to QA stuff. For now, build
and test automation are still done with Arago/Danny, any plan to switch
to or add Arago/Dylan config?
On the side, any plan to add beaglebone and/or beaglebone-black to the
list of machines used by your continuous integration systems?
>
>
>> Also, do you think it is conceivable to hope for a working Qt5 with
>> TI OpenGL stuff?
>
> It's in the plans. Prabu was able to get it built after some massaging, but
> there are still few issues. Also, we would need to make sure the fallback
> mechanism works for legacy devices w/o GLES, since Qt5 requires it...
Interesting! What I found so far:
- https://github.com/prabindh/qt-configs
- http://e2e.ti.com/search/default.aspx#q=qt5&g=29&sc=forum
- and of course https://github.com/meta-qt5/meta-qt5, which depends on
oe master :(
What I would like to achieve by the next months is to provide an
{arago|angstrom|poxy}-danny-qt5 SDK and custom rootfs to the dev guys.
Will see how it goes!
Regards,
Chris
next prev parent reply other threads:[~2013-07-23 4:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-21 5:55 [nightly] Core TISDK 2013.06 build 2013-07-21_01-01-44 Denys Dmytriyenko
2013-07-23 2:26 ` Christian Gagneraud
2013-07-23 3:15 ` Denys Dmytriyenko
2013-07-23 4:43 ` Christian Gagneraud [this message]
2013-07-23 6:02 ` Denys Dmytriyenko
2013-07-23 23:59 ` Denys Dmytriyenko
2013-07-24 2:24 ` Christian Gagneraud
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51EE0A0A.3020902@gna.org \
--to=chgans@gna.org \
--cc=denys@ti.com \
--cc=meta-arago@arago-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.