From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v6] mx6sx: Add initial support for Samtec VIN|ING 2000 board
Date: Wed, 30 Nov 2016 09:56:47 +0100 [thread overview]
Message-ID: <fb3d68e0-e034-4043-e7e2-6fc51289b038@denx.de> (raw)
In-Reply-To: <1480432420.2233.4.camel@googlemail.com>
On 29/11/2016 16:13, Christoph Fritz wrote:
> This patch adds initial support for Samtec VIN|ING 2000 board.
>
> Signed-off-by: Christoph Fritz <chf.fritz@googlemail.com>
> ---
> Changes since v1:
> - add more comments (enet phy init)
> - fix layout style e.g. multi-line-comments
> - use pinmux macros
> - use helper funcs clrsetbits_le32() and wait_for_bit()
> - make some functions static
> - drop board_ehci_hcd_init() and board_phy_config()
> - simplify environment
> Changes since v2:
> - adapt error handling in board_eth_init() and read_adc()
> - purge unused macros
> - use config_distro_bootcmd as environment
> - fix CONFIG_PWM_IMX undef handling
> Changes since v3:
> - fix comment spelling
> - use u32
> - rearrange if condition
> Changes since v4:
> - use parent error codes
> - rename config string to TARGET_SAMTEC_VINING_2000
> Changes since v5:
> - simplify board_eth_init() error message
>
> arch/arm/cpu/armv7/mx6/Kconfig | 7 +
> board/samtec/vining_2000/Kconfig | 12 +
> board/samtec/vining_2000/MAINTAINERS | 6 +
> board/samtec/vining_2000/Makefile | 6 +
> board/samtec/vining_2000/imximage.cfg | 132 +++++++++
> board/samtec/vining_2000/vining_2000.c | 517 +++++++++++++++++++++++++++++++++
> configs/vining_2000_defconfig | 31 ++
> include/configs/vining_2000.h | 123 ++++++++
> 8 files changed, 834 insertions(+)
> create mode 100644 board/samtec/vining_2000/Kconfig
> create mode 100644 board/samtec/vining_2000/MAINTAINERS
> create mode 100644 board/samtec/vining_2000/Makefile
> create mode 100644 board/samtec/vining_2000/imximage.cfg
> create mode 100644 board/samtec/vining_2000/vining_2000.c
> create mode 100644 configs/vining_2000_defconfig
> create mode 100644 include/configs/vining_2000.h
>
> diff --git a/arch/arm/cpu/armv7/mx6/Kconfig b/arch/arm/cpu/armv7/mx6/Kconfig
> index 762a581..057b8cd 100644
Applied to u-boot-imx, thanks !
Best regards,
Stefano Babic
--
=====================================================================
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de
=====================================================================
prev parent reply other threads:[~2016-11-30 8:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-22 14:48 [U-Boot] [PATCH] mx6sx: Add initial support for Samtec VIN|ING 2000 board Christoph Fritz
2016-11-22 15:22 ` Marek Vasut
2016-11-23 16:30 ` Christoph Fritz
2016-11-23 16:33 ` [U-Boot] [PATCH v2] " Christoph Fritz
2016-11-23 16:49 ` Marek Vasut
2016-11-23 18:39 ` [U-Boot] [PATCH v3] " Christoph Fritz
2016-11-23 19:04 ` Marek Vasut
2016-11-23 22:26 ` [U-Boot] [PATCH v4] " Christoph Fritz
2016-11-23 22:48 ` Marek Vasut
2016-11-24 9:45 ` [U-Boot] [PATCH v5] " Christoph Fritz
2016-11-25 10:39 ` Marek Vasut
2016-11-29 15:13 ` [U-Boot] [PATCH v6] " Christoph Fritz
2016-11-29 15:21 ` Stefano Babic
2016-11-29 17:24 ` Marek Vasut
2016-11-30 8:56 ` Stefano Babic [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=fb3d68e0-e034-4043-e7e2-6fc51289b038@denx.de \
--to=sbabic@denx.de \
--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