From: Mike Rapoport <mike@compulab.co.il>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCHi v3] OMAP3: add CM-T35 board
Date: Sun, 15 Nov 2009 16:47:39 +0200 [thread overview]
Message-ID: <4B00148B.8020003@compulab.co.il> (raw)
In-Reply-To: <0554BEF07D437848AF01B9C9B5F0BC5D940250EB@dlee01.ent.ti.com>
Paulraj, Sandeep wrote:
>
>> Add CM-T35 board support
>>
>> Signed-off-by: Mike Rapoport <mike@compulab.co.il>
>>
>> --
>> v2 changes:
>> - rename board config file from omap3_cm-t35.h to cm-t35.h
>> - remove SZ_xx references
>> - add MAKEALL/MAINTEINERS entries
>>
>> v3 changes:
>> - fix whitespace and indentation
>> - remove eth_init from board_eth_init
>> - add CM-T35 entry to doc/README.omap3
>> - fixed board name in MAINTAINERS
>>
>> ---
>> MAINTAINERS | 4 +
>> MAKEALL | 1 +
>> Makefile | 2 +
>> board/cm-t35/Makefile | 47 ++++++++
>> board/cm-t35/cm-t35.c | 190 +++++++++++++++++++++++++++++
>> board/cm-t35/cm-t35.h | 173 +++++++++++++++++++++++++++
>> board/cm-t35/config.mk | 30 +++++
>> doc/README.omap3 | 16 ++-
>> include/configs/cm-t35.h | 296
>> ++++++++++++++++++++++++++++++++++++++++++++++
>> 9 files changed, 757 insertions(+), 2 deletions(-)
>> create mode 100644 board/cm-t35/Makefile
>> create mode 100644 board/cm-t35/cm-t35.c
>> create mode 100644 board/cm-t35/cm-t35.h
>> create mode 100644 board/cm-t35/config.mk
>> create mode 100644 include/configs/cm-t35.h
>
> Was this patch made against the current u-boot-ti/next.
>
> The reason I say this is because there was a DDR patch that affects all OMAP3 boards. So this support should be added against u-boot-ti/next and tested against it. I believe there is a config option to choose between MICRON and INFINEON DDR's.
>
Rebasing, thanks.
>
--
Sincerely yours,
Mike.
prev parent reply other threads:[~2009-11-15 14:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-15 7:34 [U-Boot] [PATCHi v3] OMAP3: add CM-T35 board Mike Rapoport
2009-11-15 14:21 ` Paulraj, Sandeep
2009-11-15 14:47 ` Mike Rapoport [this message]
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=4B00148B.8020003@compulab.co.il \
--to=mike@compulab.co.il \
--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