From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] omap3evm: Update board and defconfig files
Date: Thu, 3 Aug 2017 08:44:35 -0400 [thread overview]
Message-ID: <20170803124435.GF29197@bill-the-cat> (raw)
In-Reply-To: <CA+CtpRgLtikGb_CqTxtn95GzS0BZeKABC997nH+eHzdHwyzOSg@mail.gmail.com>
On Thu, Aug 03, 2017 at 07:37:34AM -0500, Derald Woods wrote:
> On Thu, Aug 3, 2017 at 6:31 AM, Tom Rini <trini@konsulko.com> wrote:
>
> > On Wed, Aug 02, 2017 at 10:00:06PM -0500, Derald D. Woods wrote:
> >
> > > This patch brings the OMAP3 EVM to a bootable state, on master, as of
> > > v2017.09-rc1.
> > >
> > > Signed-off-by: Derald D. Woods <woods.technical@gmail.com>
> >
> > Reviewed-by: Tom Rini <trini@konsulko.com>
> >
> > Thanks. Since you have one of these boards, would you like to take over
> > maintainership of it?
>
>
> ​Yes. I do have this board, with the OMAP3530 processor module, and will be
> able to test releases.
>
> On a side note, I recently posted the following:
>
> http://u-boot.10912.n7.nabble.com/PATCH-arm-omap-Fix-get-device-type-for-OMAP34XX-td300937.html#a300993
>
> I verified the small patch with omap3evm, beagleboard(revc4), and overo.
> CPU information can be directly read, as it was previously. Is there some
> consistent road-map for SRAM usage for OMAP34XX specifically?
Ah yes, I had that on my to reply to list, sorry. What I was wondering
was, why does current mainline fail? I had tested that series on the
beagleboard xM but indeed not on plain beagleboard.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20170803/df9dd2eb/attachment.sig>
next prev parent reply other threads:[~2017-08-03 12:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-03 3:00 [U-Boot] [PATCH] omap3evm: Update board and defconfig files Derald D. Woods
2017-08-03 11:31 ` Tom Rini
2017-08-03 12:37 ` Derald Woods
2017-08-03 12:44 ` Tom Rini [this message]
2017-08-04 23:58 ` [U-Boot] [PATCH v2] " Derald D. Woods
2017-08-05 15:42 ` Tom Rini
2017-08-06 5:00 ` [U-Boot] [PATCH v3] omap3: evm: Update board, defconfig, and maintainer file Derald D. Woods
2017-08-06 13:44 ` Tom Rini
2017-08-12 13:15 ` [U-Boot] [U-Boot, " Tom Rini
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=20170803124435.GF29197@bill-the-cat \
--to=trini@konsulko.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