public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Vladimir Zapolskiy <vz@mleia.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/3 v2] devkit3250: add Timll DevKit3250 board initial support
Date: Tue, 15 Nov 2011 09:25:28 +0200	[thread overview]
Message-ID: <4EC213E8.9070607@mleia.com> (raw)
In-Reply-To: <4EC209D1.2010001@compulab.co.il>

Hi Igor,

On 15.11.2011 08:42, Igor Grinberg wrote:
> Hi Vladimir,
>
> On 11/14/11 19:43, Vladimir Zapolskiy wrote:
>> This change adds a basic support for Embest/Timll DevKit3250 board,
>> NOR and UART are the only supported peripherals for a moment. The board
>> doesn't require low-level init, because the initial SDRAM and GPIO
>> configuration is performed during kickstart bootloader execution.
>>
>> Signed-off-by: Vladimir Zapolskiy<vz@mleia.com>
>> ---
>> Changes from v1 to v2:
>> * corrected address in GPLv2+ licence header in files
>
> I think you should remove the address part completely,
> because next time it changes, will you be around to fix it?
I promise I'll be around, that's why I desire to become a maintainer of 
this board.

> I know that there are many files already with address, but
> to make a big change it is better to start it from small -
> say all new coming patches.
Well, my small contribution is verifying address in license header found 
in new files.

I'd like to invite Wolfgang into discussion to get his opinion about the 
topic. Well, I do not feel myself as a lawer to allege that removing 
address info from the license notice is ok. Has it already been 
discussed in the mailing list?

>> * removed clean and distclean targets from board makefile
>> * do not set machine id explicitly, if CONFIG_MACH_TYPE is defined
>> * minor indentation cleanups
>>
>>   board/timll/devkit3250/Makefile     |   44 +++++++++++++
>>   board/timll/devkit3250/devkit3250.c |   71 ++++++++++++++++++++
>>   boards.cfg                          |    3 +-
>>   include/configs/devkit3250.h        |  121 +++++++++++++++++++++++++++++++++++
>>   4 files changed, 238 insertions(+), 1 deletions(-)
>>   create mode 100644 board/timll/devkit3250/Makefile
>>   create mode 100644 board/timll/devkit3250/devkit3250.c
>>   create mode 100644 include/configs/devkit3250.h
>>

[snip]

-- 
With best wishes,
Vladimir

  reply	other threads:[~2011-11-15  7:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-14 17:43 [U-Boot] [PATCH 0/3] devkit3250: add Timll DevKit3250 board initial support Vladimir Zapolskiy
2011-11-14 17:43 ` [U-Boot] [PATCH 1/3 v5] arm926ejs: add NXP LPC32x0 cpu series support Vladimir Zapolskiy
2011-11-14 17:43 ` [U-Boot] [PATCH 2/3 v2] devkit3250: add Timll DevKit3250 board initial support Vladimir Zapolskiy
2011-11-15  6:42   ` Igor Grinberg
2011-11-15  7:25     ` Vladimir Zapolskiy [this message]
2011-11-15  7:48       ` Igor Grinberg
2011-11-15 18:17         ` Vladimir Zapolskiy
2011-11-14 17:43 ` [U-Boot] [PATCH 3/3] devkit3250: add DevKit3250 board maintainer Vladimir Zapolskiy
2011-11-15 21:34 ` [U-Boot] [PATCH 0/3] devkit3250: add Timll DevKit3250 board initial support Vladimir Zapolskiy

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=4EC213E8.9070607@mleia.com \
    --to=vz@mleia.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