From: Troy Benjegerdes <hozer@hozed.org>
To: Denys Dmytriyenko <denys@ti.com>
Cc: "meta-ti@yoctoproject.org" <meta-ti@yoctoproject.org>
Subject: Re: regression tests for am3517-evm machine?
Date: Wed, 27 Jan 2016 15:56:45 -0600 [thread overview]
Message-ID: <20160127215645.GD2584@nl.grid.coop> (raw)
In-Reply-To: <20160121220740.GF11314@edge>
On Thu, Jan 21, 2016 at 05:07:41PM -0500, Denys Dmytriyenko wrote:
> On Thu, Jan 21, 2016 at 04:03:29PM -0600, Robert Nelson wrote:
> > >> Didn't 3.x kernels start requiring a device tree somewhere along the line?
> > >>
> > >> I know the Beaglebone uses a device tree, but I can't seem to manage find
> > >> all the right pieces to build a working u-boot for am3517-evm that can
> > >> properly pass it off to the kernel, at least with the Legacy image format(s).
> > >
> > > Well, am3517 is one of the legacy platforms and I don't believe it was ever
> > > converted to use device tree...
> >
> > Looks like it should atleast boot to mmc rootfs..
> >
> > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/arch/arm/boot/dts/am3517-evm.dts
>
> Well, I guess my memory is not that great any more... :)
>
> http://git.yoctoproject.org/cgit/cgit.cgi/meta-ti/commit/?id=dbdb539e249c3b55ca3dc601c357634a0dbc909e
>
So the first problem seems to be that the 'u-boot' target produces
a build from the 2014.07 version, which does not seem to have any
environment or other setup to load a device tree.
Is there some patch floating around somewhere that updates the
default u-boot environment to work better with new kernels, or do
I need try and merge something in from the beaglebone
next prev parent reply other threads:[~2016-01-27 21:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-16 6:36 regression tests for am3517-evm machine? Troy Benjegerdes
2016-01-18 16:46 ` Denys Dmytriyenko
2016-01-18 20:05 ` Troy Benjegerdes
2016-01-19 18:48 ` Troy Benjegerdes
2016-01-19 19:08 ` Denys Dmytriyenko
2016-01-21 1:58 ` Troy Benjegerdes
2016-01-21 20:48 ` Denys Dmytriyenko
2016-01-21 22:03 ` Robert Nelson
2016-01-21 22:07 ` Denys Dmytriyenko
2016-01-27 21:56 ` Troy Benjegerdes [this message]
2016-01-27 22:03 ` Denys Dmytriyenko
2016-01-27 22:12 ` Troy Benjegerdes
2016-01-27 22:55 ` Denys Dmytriyenko
2016-01-28 4:52 ` Troy Benjegerdes
2016-01-28 16:13 ` Denys Dmytriyenko
2016-01-28 16:33 ` Troy Benjegerdes
2016-01-29 0:09 ` Denys Dmytriyenko
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=20160127215645.GD2584@nl.grid.coop \
--to=hozer@hozed.org \
--cc=denys@ti.com \
--cc=meta-ti@yoctoproject.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.