public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Albert ARIBAUD <albert.aribaud@free.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V6 1/3] Initial support for Marvell Orion5x SoC
Date: Sun, 11 Apr 2010 09:35:59 +0200	[thread overview]
Message-ID: <4BC17BDF.70904@free.fr> (raw)
In-Reply-To: <20100410211601.0E999E6D662@gemini.denx.de>

Wi Wolfgang,

Wolfgang Denk a ?crit :

> Dear Albert Aribaud,
> 
> In message <1270801745-18852-1-git-send-email-albert.aribaud@free.fr> you wrote:
>> This patch adds support for the Marvell Orion5x SoC.
>> It has no use alone, and must be followed by a patch
>> to add Orion5x support for serial, then support for
>> the ED Mini V2, an Orion5x-based product from LaCie.
>> ---
>> Patchset history
>>
>> V1: Initial monolithic patch.
>> V2: split in three patches : orion, serial, edmini;
>>     checkpatch'ed, with only 6 errors, in patch 1/3,
>>     all 6 errors being false positives.
>> V3: useless GPIO and MPP programming support removed;
>>     low level init added/CONFIG_SKIP_LOW_LEVEL_INIT removed.
>> V4: all files licensed GPLv2-only removed;
>>     RAM bank size detection now uses get_ram_size().
>> V5: Replaced macros by C structs in dram code.
>>     Removed compilation warnings in dram code.
>>     Added comments to legacy flash definitions.
>>     Split low level init code into SoC- and Chip-specifics.
>> V6: Set copyright dates to 2010, and put standard GPL notice
>>     mentioning Marvell's copyright on *_lowlevel_init.S files.
> 
> Just to be sure: do you have Marvell's permission to change the
> licensing terms?

Actually this was checked by Prafulla in december:

<http://lists.denx.de/pipermail/u-boot/2009-December/065797.html>

> Best regards,
> 
> Wolfgang Denk

Amicalement,
-- 
Albert.

  reply	other threads:[~2010-04-11  7:35 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-09  8:29 [U-Boot] [PATCH V6 1/3] Initial support for Marvell Orion5x SoC Albert Aribaud
2010-04-09  8:29 ` [U-Boot] [PATCH V6 2/3] Add Orion5x support to 16550 device driver Albert Aribaud
2010-04-09  8:29   ` [U-Boot] [PATCH V6 3/3] Add support for the LaCie ED Mini V2 board Albert Aribaud
2010-04-09  9:37     ` Prafulla Wadaskar
2010-04-12 11:13       ` Prafulla Wadaskar
2010-04-10 21:16 ` [U-Boot] [PATCH V6 1/3] Initial support for Marvell Orion5x SoC Wolfgang Denk
2010-04-11  7:35   ` Albert ARIBAUD [this message]
2010-04-11  7:41     ` Albert ARIBAUD
2010-04-12  8:32       ` Prafulla Wadaskar
2010-04-12 10:42         ` Albert ARIBAUD
2010-04-12 10:45         ` Wolfgang Denk
2010-04-12 11:09           ` Prafulla Wadaskar
2010-04-12 12:00             ` Albert ARIBAUD
2010-04-12 12:41             ` Wolfgang Denk
2010-04-12 15:02             ` Albert ARIBAUD
2010-04-13 10:33               ` Prafulla Wadaskar
2010-04-13 11:08                 ` Albert ARIBAUD
2010-04-13 13:37                   ` Prafulla Wadaskar
2010-04-13 15:40                     ` Albert ARIBAUD
2010-04-14  7:42                       ` Prafulla Wadaskar
2010-04-15  6:34                         ` Albert ARIBAUD
2010-04-29  9:57                           ` Prafulla Wadaskar
2010-04-11 11:56     ` Wolfgang Denk

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=4BC17BDF.70904@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox