From: Denys Dmytriyenko <denys@ti.com>
To: Rudolf Streif <rstreif@linuxfoundation.org>
Cc: meta-ti@yoctoproject.org
Subject: Re: AM335x EVM and core-image-sato
Date: Fri, 18 Oct 2013 22:39:54 -0400 [thread overview]
Message-ID: <20131019023954.GK2127@edge> (raw)
In-Reply-To: <CA+gsK-qKLdXTq1PJEmXLp0d5n5wEYf+6Na+pFj+UwnWLO_dt2g@mail.gmail.com>
On Fri, Oct 18, 2013 at 06:09:23PM -0700, Rudolf Streif wrote:
> Well, I rebuilt with a newer version of meta-ti
> (master, b3df09902da0d2469a02e9975d404e26c4c5ec0e). Now the /dev/fb0 device
> is in the root file system. However:
>
> - Kernel image is now zImage but u-boot environment still looks for
> uImage; work around that and then
u-boot has changed the preferred default from uImage to zImage somewhere
between 2013.10-rc4 and the final 2013.10 release. The kernel now builds
zImage by default and there's corresponding u-boot update:
http://git.yoctoproject.org/cgit/cgit.cgi/meta-ti/commit/?id=3f3bad888972776b4740f7210e709b74362631f5
Looks like you hit it at the wrong time... Sorry, that sometimes happens
when there are multiple components being actively developed and the API
between them changes...
> - kernel panic - not syncing: Attempting to kill init! exitcode=0x0b.
Have you tried the latest update to 3.12-rc5? That combination seems to be
building and booting fine, according to our automated reports:
http://article.gmane.org/gmane.linux.embedded.yocto.meta-arago/1245
> One step forward, two steps back. Pulled again, and this time build fails
> because branch ti-linux-312.y is not available.
The branch was and is called ti-linux-3.12.y and it hasn't changed since the
beginning of 3.12 integration and is still there:
http://git.ti.com/gitweb/?p=ti-linux-kernel/ti-linux-kernel.git;a=shortlog;h=refs/heads/ti-linux-3.12.y
> What branch of meta-ti and what commit is working?
Both master and dylan are currently in sync and always are, when it comes to
3.12-rc5 kernel and 2013.10 u-boot. Other recipes can differ between master
and dylan, but the integration trees are the same. The above link to automated
build and test report used dylan branch of meta-ti and the latest commit ID of
f61008a20340373247ebfd8f381e377b21f11afe. If you want to use meta-ti master,
then the corresponding commit ID is c11504664990f007c3903d349e7cc135a904f8e2.
--
Denys
next prev parent reply other threads:[~2013-10-19 2:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-17 21:29 AM335x EVM and core-image-sato Rudolf Streif
2013-10-17 21:45 ` Denys Dmytriyenko
2013-10-19 1:09 ` Rudolf Streif
2013-10-19 2:39 ` Denys Dmytriyenko [this message]
2013-10-19 18:53 ` Rudolf Streif
2013-10-21 8:16 ` Rudolf Streif
2013-10-21 17:42 ` Rudolf Streif
2013-10-21 21:15 ` Denys Dmytriyenko
2013-10-21 22:19 ` Rudolf Streif
2013-10-21 23:19 ` Denys Dmytriyenko
2013-10-22 7:57 ` Rudolf Streif
2013-10-22 19:36 ` Denys Dmytriyenko
2013-10-22 20:16 ` Denys Dmytriyenko
2013-10-22 19:37 ` Denys Dmytriyenko
-- strict thread matches above, loose matches on Subject: below --
2013-10-22 20:36 Vanderpool Josh
2013-10-22 22:28 ` Denys Dmytriyenko
2013-10-22 23:47 ` Rudolf Streif
2013-10-22 23:54 ` Dmytriyenko, Denys
2013-10-23 16:32 ` Vanderpool Josh
2013-10-25 12:07 ` Vanderpool Josh
2013-10-25 14:11 ` Dmytriyenko, Denys
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=20131019023954.GK2127@edge \
--to=denys@ti.com \
--cc=meta-ti@yoctoproject.org \
--cc=rstreif@linuxfoundation.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.