From: Nishanth Menon <nm@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH RFC] OMAP5: uEVM: Enable USB EHCI functionality (preliminary, not tested)
Date: Wed, 15 May 2013 11:09:38 -0500 [thread overview]
Message-ID: <20130515160938.GA4552@kahuna> (raw)
In-Reply-To: <5193AFEC.60700@mm-sol.com>
On 18:55-20130515, Lubomir Popov wrote:
> Prerequisites: appropriate patches to the USB EHCI and Eth
> drivers, and to the OMAP5 clock register definitions.
proper commit message is needed before this goes from RFC to patch.
>
> Signed-off-by: Lubomir Popov <lpopov@mm-sol.com>
> ---
> Assumption is that this code shall run on TI 750-2628-21X
> hardware (also known as OMAP5432 ES2.0 PandaBoard5) - the
uEVM - there is no PandaBoard5 in existence.
https://www.svtronics.com/index.php?route=product/product&product_id=33
Just a minor nit:
> const struct omap_sysinfo sysinfo = {
> - "Board: OMAP5430 EVM\n"
> + "Board: OMAP5432 uEVM\n"
nit: does not belong to this patch.
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2013-05-15 16:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-15 15:55 [U-Boot] [PATCH RFC] OMAP5: uEVM: Enable USB EHCI functionality (preliminary, not tested) Lubomir Popov
2013-05-15 16:09 ` Nishanth Menon [this message]
2013-05-15 22:06 ` Tom Rini
2013-05-15 22:33 ` Gilles Chanteperdrix
2013-05-16 8:23 ` Lubomir Popov
2013-05-16 12:28 ` Tom Rini
2013-05-16 14:56 ` Lubomir Popov
2013-05-16 15:29 ` Tom Rini
2013-05-16 18:43 ` Lubomir Popov
2013-05-17 13:52 ` Tom Rini
2013-05-17 5:34 ` Sricharan R
2013-05-17 9:35 ` Lubomir Popov
2013-05-15 22:31 ` Gilles Chanteperdrix
2013-05-16 8:39 ` Lubomir Popov
2013-05-18 15:25 ` Gilles Chanteperdrix
2013-05-18 17:07 ` Tom Rini
2013-05-18 17:12 ` Gilles Chanteperdrix
2013-05-18 19:13 ` Lubomir Popov
2013-05-18 19:16 ` Gilles Chanteperdrix
2013-05-18 19:24 ` Lubomir Popov
2013-05-18 20:46 ` Gilles Chanteperdrix
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=20130515160938.GA4552@kahuna \
--to=nm@ti.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