From: Simon Guinot <simon@sequanux.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 5/6] ARM: add support for Network Space v2 Lite and Mini
Date: Fri, 25 May 2012 16:42:22 +0200 [thread overview]
Message-ID: <20120525144222.GS29241@kw.sim.vm.gnt> (raw)
In-Reply-To: <F766E4F80769BD478052FB6533FA745D1A2FB28A12@SC-VEXCH4.marvell.com>
On Thu, May 24, 2012 at 01:03:07AM -0700, Prafulla Wadaskar wrote:
>
>
> > -----Original Message-----
> > From: Simon Guinot [mailto:simon.guinot at sequanux.org]
> > Sent: 16 May 2012 19:51
> > To: Prafulla Wadaskar
> > Cc: Albert ARIBAUD; u-boot at lists.denx.de; Simon Guinot
> > Subject: [PATCH 5/6] ARM: add support for Network Space v2 Lite and
> > Mini
> >
> > This patch adds support for the LaCie boards Network Space v2 (Lite
> > and
> > Mini). This two boards are derived from the Network Space v2 and a lot
> > of hardware caracteristics are shared.
> >
> > - CPU: Marvell 88F6192 800Mhz
> > - SDRAM memory: 128MB DDR2 200Mhz
> > - 1 SATA port: internal
> > - Gigabit ethernet: PHY Marvell 88E1318
> > - Flash memory: SPI NOR 512KB (Macronix MX25L4005A)
> > - i2c EEPROM: 512 bytes (24C04 type)
> > - 2 USB2 ports (Lite only): host and host/device
> > - 1 push button
> > - 1 SATA LED (bi-color, blue and red)
> >
> > Signed-off-by: Simon Guinot <simon.guinot@sequanux.org>
> > ---
> > arch/arm/include/asm/mach-types.h | 13 +++
>
> I think the updates to this file to be done by ARM maintainer.
OK, I will move this part in a separate patch.
>
> > board/LaCie/common/common.c | 36 ++++++-
> > board/LaCie/common/common.h | 1 +
> > board/LaCie/netspace_v2/kwbimage-ns2l.cfg | 162
> > +++++++++++++++++++++++++++++
> > board/LaCie/netspace_v2/netspace_v2.c | 4 +
> > boards.cfg | 2 +
> > include/configs/lacie_kw.h | 26 ++++-
> > 7 files changed, 237 insertions(+), 7 deletions(-)
> > create mode 100644 board/LaCie/netspace_v2/kwbimage-ns2l.cfg
>
> Again, can the current cfg files be reused? Instead of adding new?
No, they can't be reused because the memory type and size are different
between Network Space v2 and Network Space Lite v2.
Regards,
Simon
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20120525/35e4dd31/attachment.pgp>
next prev parent reply other threads:[~2012-05-25 14:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-16 14:20 [U-Boot] [PATCH 0/6] Bug fixes and board support for LaCie devices Simon Guinot
2012-05-16 14:20 ` [U-Boot] [PATCH 1/6] lacie_kw: fix SDRAM banks number for net2big_v2 Simon Guinot
2012-05-16 14:20 ` [U-Boot] [PATCH 2/6] lacie_kw: fix CONFIG_SYS_KWD_CONFIG for inetspace_v2 Simon Guinot
2012-05-16 14:20 ` [U-Boot] [PATCH 3/6] lacie_kw: add support for EFI partitions Simon Guinot
2012-05-16 14:20 ` [U-Boot] [PATCH 4/6] ARM: don't probe PHY address for LaCie boards Simon Guinot
2012-05-16 14:20 ` [U-Boot] [PATCH 5/6] ARM: add support for Network Space v2 Lite and Mini Simon Guinot
2012-05-24 8:03 ` Prafulla Wadaskar
2012-05-25 14:42 ` Simon Guinot [this message]
2012-05-16 14:20 ` [U-Boot] [PATCH 6/6] ARM: add support for d2 Network v2 Simon Guinot
2012-05-24 7:57 ` [U-Boot] [PATCH 0/6] Bug fixes and board support for LaCie devices Prafulla Wadaskar
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=20120525144222.GS29241@kw.sim.vm.gnt \
--to=simon@sequanux.org \
--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