From: Andy Pont <andy.pont@sdcsystems.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Falcon mode for TI DM355
Date: Thu, 11 Feb 2016 17:02:16 -0000 [thread overview]
Message-ID: <023801d164ed$f6d31370$e4793a50$@pont@sdcsystems.com> (raw)
In-Reply-To: <20160211165041.GT23166@bill-the-cat>
Hi Tom,
> So, git commit 6761946f is what removed the board in question. Now,
> looking in mainline today (and also looking at 6761946f) I see that we
> had and have support for CONFIG_TARGET_OMAPL138_LCDK and that uses SPL
> which is a prerequisite for falcon mode. So there's nothing too low
> level that would need to be done for the DM355, just the board specific
> portions.
The current implementation for the target hardware is based on 2013.07. Can
we make it work with that or should we look to move to something more
recent? Not wanting to make too many changes unnecessarily.
Andy.
next prev parent reply other threads:[~2016-02-11 17:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <56bc77b1.d5671c0a.c9367.79bdSMTPIN_ADDED_BROKEN@mx.google.com>
2016-02-11 16:50 ` [U-Boot] Falcon mode for TI DM355 Tom Rini
2016-02-11 17:02 ` Andy Pont [this message]
[not found] ` <56bcbeab.88671c0a.78a8b.3722SMTPIN_ADDED_BROKEN@mx.google.com>
2016-02-11 18:04 ` Tom Rini
2016-02-11 11:53 Andy Pont
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='023801d164ed$f6d31370$e4793a50$@pont@sdcsystems.com' \
--to=andy.pont@sdcsystems.com \
--cc=u-boot@lists.denx.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox