From: Albert ARIBAUD <albert.aribaud@free.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V4] Add support for Bluewater Systems Snapper9260/9G20 modules
Date: Mon, 14 Feb 2011 08:10:10 +0100 [thread overview]
Message-ID: <4D58D552.9050107@free.fr> (raw)
In-Reply-To: <4D584123.9080501@bluewatersys.com>
Le 13/02/2011 21:37, Ryan Mallon a ?crit :
> Add support for Bluewater Systems AT91 based Snapper 9260 and 9G20
> single board computer modules. Includes NAND flash and Ethernet
> support.
>
> Signed-off-by: Ryan Mallon<ryan@bluewatersys.com>
> ---
> Build and run tested with new changes.
>
> Changes for v4:
> - Rebased on atmel/rework110202 branch
> - Changed text base to 0x20000000 due to new relocation rules.
>
> Changes for v3:
> - Replaced SZ_ macros with shifts
> - Remove defined values from CONFIG_ defines
> - Moved boards.cfg entry to correct place
> - Added MAINTAINERS entry
>
> Changes for v2:
> - Updated for recent at91 changes
> - Use CONFIG_AT91FAMILY in soft_i2c driver
> - Fixed missing snapper9260.h config file
> - Add config to boards.cfg not Makefile
> - Removed config.mk (now in snapper9260.h)
> ---
>
> diff --git a/MAINTAINERS b/MAINTAINERS
Uhm... Is it me or should there be a summing-up of files modified before
this? It would help knowing at once which files are touched and hence,
if/which Custodians are to be involved.
> diff --git a/board/bluewater/snapper9260/Makefile b/board/bluewater/snapper9260/Makefile
> diff --git a/board/bluewater/snapper9260/snapper9260.c b/board/bluewater/snapper9260/snapper9260.c
> diff --git a/boards.cfg b/boards.cfg
> diff --git a/include/configs/snapper9260.h b/include/configs/snapper9260.h
Amicalement,
--
Albert.
prev parent reply other threads:[~2011-02-14 7:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-13 20:37 [U-Boot] [PATCH V4] Add support for Bluewater Systems Snapper9260/9G20 modules Ryan Mallon
2011-02-14 7:10 ` Albert ARIBAUD [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=4D58D552.9050107@free.fr \
--to=albert.aribaud@free.fr \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.