From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2 v3] arm: suen3, suen3_v1, mgcoge2_arm_p1a support
Date: Wed, 10 Feb 2010 08:09:23 +0100 [thread overview]
Message-ID: <4B725BA3.9050304@denx.de> (raw)
In-Reply-To: <4B699BA5.6090001@denx.de>
Hello Prafulla,
do you have some comments on the following 2 points?
(If they are clarified, I can post v4 of the patch ...)
Heiko Schocher wrote:
> Prafulla Wadaskar wrote:
>>> -----Original Message-----
>>> From: Heiko Schocher [mailto:hs at denx.de]
>>> Sent: Monday, February 01, 2010 1:07 PM
>>> To: U-Boot user list
>>> Cc: Wolfgang Denk; Prafulla Wadaskar; Tom
>>> Subject: [PATCH 2/2 v3] arm: suen3, suen3_v1, mgcoge2_arm_p1a support
>>>
>>> This patch adds support for the Keymile SUEN3 board variants which
>>> are based on the Marvell Kirkwood (88F6281) SoC. All variants
>>> uses common code stored in board/keymile/km_arm/km_arm.c
>>>
>>> mgcoge2_arm_p1a board:
>>> This adds support for the ARM part of the mgcoge2. The suen3
>>> target was moved to the correct suen3 p1b version. There is a
>>> difference between the GPIO configuration between suen3 and mgcoge2.
>>>
>>> Signed-off-by: Holger Brunck <holger.brunck@keymile.com>
>>> Signed-off-by: Stefan Roese <sr@denx.de>
>>> Signed-off-by: Heiko Schocher <hs@denx.de>
>>> ---
>>> - changes since v1:
>>> added comments from Wolfgang Denk:
>>> get rid of flash_info_t define in board config
>>> (to get this working patch 1/2 is introduced/needed)
>>> - changes since v2:
>>> added comments from Wolfgang Denk
>>> - rearranged if/else in do_spi_toggle()
>>> - added I/O accessor functions for bootcounter
>>>
>>> MAINTAINERS | 2 +
>>> MAKEALL | 4 +
>>> Makefile | 8 +
>>> board/keymile/common/common.c | 23 ++-
>>> board/keymile/km_arm/Makefile | 51 +++++
>>> board/keymile/km_arm/config.mk | 25 +++
>>> board/keymile/km_arm/km_arm.c | 343
>>> +++++++++++++++++++++++++++++++++
>>> board/keymile/km_arm/sdramregs.txt | 31 +++
>>> board/keymile/km_arm/sdramregs_v1.txt | 28 +++
>>> include/configs/km-arm.h | 189 ++++++++++++++++++
[...]
>>> include/configs/mgcoge2_arm_p1a.h | 96 +++++++++
>>> include/configs/suen3.h | 103 ++++++++++
>>> include/configs/suen3_p1a.h | 82 ++++++++
>>> include/configs/suen3_p1b_p1c.h | 110 +++++++++++
>> ...snip...
>>
>> the include/config files indicates that there are five board supports.
>> Please provide one patch for each board, may be first will be master one.
>
> This question also asked Tom, see:
>
> http://lists.denx.de/pipermail/u-boot/2010-January/067182.html
>
> But if you prefer to split this in 5 patches, I can do it.
Is it OK in one patch, or should I split it in 4 patches?
[...]
>>> diff --git a/board/keymile/km_arm/sdramregs.txt
>>> b/board/keymile/km_arm/sdramregs.txt
>>> new file mode 100644
>>> index 0000000..68c53a7
>>> --- /dev/null
>>> +++ b/board/keymile/km_arm/sdramregs.txt
>>> @@ -0,0 +1,31 @@
>> What is this file?
>> Which license?
>> Who is using it?
>
> Ok, you are right, some comments are here necessary.
>
> On this boards is a preloader, which initializes
> the RAM. Therefore the preloader reads the RAM settings
> from the image he should load, through an header. This
> header is created with a tool doimage (I think it is
> from marvell), and this tool needs this file ...
>
> So, I have no idea where to put this files, and think
> they are in the board directory on the right place ...
>
> I found something similiar in current mainline:
>
> board/Marvell/mv88f6281gtw_ge/dramregs_333h.txt
>
> This file is also without comments, license info ...
> Maybe this tool don;t accept comments?
What should I do with this file?
bye
Heiko
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
next prev parent reply other threads:[~2010-02-10 7:09 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-07 7:56 [U-Boot] arm: suen3, suen3_v1, mgcoge2_arm_p1a support Heiko Schocher
2010-01-17 23:51 ` Wolfgang Denk
2010-01-18 8:34 ` Heiko Schocher
2010-01-18 9:31 ` Stefan Roese
2010-01-27 7:23 ` Heiko Schocher
2010-01-27 7:30 ` [U-Boot] [PATCH 1/2 v2] cramfs: make cramfs usable on non NOR flash Heiko Schocher
2010-01-27 19:28 ` Wolfgang Denk
2010-01-28 7:30 ` Heiko Schocher
2010-01-28 10:15 ` Wolfgang Denk
2010-01-28 11:02 ` Heiko Schocher
2010-01-27 7:31 ` [U-Boot] [PATCH 2/2 v2] arm: suen3, suen3_v1, mgcoge2_arm_p1a support Heiko Schocher
2010-01-27 13:50 ` Tom
2010-01-27 14:43 ` Heiko Schocher
2010-01-28 13:54 ` Tom
2010-01-27 19:49 ` Wolfgang Denk
2010-02-01 7:37 ` [U-Boot] [PATCH 2/2 v3] " Heiko Schocher
2010-02-02 18:07 ` Prafulla Wadaskar
2010-02-03 6:42 ` Wolfgang Denk
2010-02-03 15:52 ` Heiko Schocher
2010-02-03 16:53 ` Stefan Roese
2010-02-03 22:32 ` Scott Wood
2010-02-04 7:24 ` Heiko Schocher
2010-02-08 19:23 ` Scott Wood
2010-02-10 7:09 ` Heiko Schocher [this message]
2010-02-10 7:41 ` Prafulla Wadaskar
2010-02-10 9:27 ` Heiko Schocher
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=4B725BA3.9050304@denx.de \
--to=hs@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