All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 2/5] arm: mvebu: Add Marvell's integrated CPUs
Date: Tue, 19 Feb 2019 07:34:27 +0100	[thread overview]
Message-ID: <04000a9e-24c1-18f3-02a9-8db9429278a0@denx.de> (raw)
In-Reply-To: <20190215224902.28351-3-judge.packham@gmail.com>

On 15.02.19 23:48, Chris Packham wrote:
> Marvell's switch chips with integrated CPUs (collectively referred to as
> MSYS) share common ancestry with the Armada SoCs. Some of the IP blocks
> (e.g. xor) are located at different addresses and DFX server exists as a
> separate target on the MBUS (on Armada-38x it's just part of the core
> complex registers).
> 
> Signed-off-by: Chris Packham <judge.packham@gmail.com>

Reviewed-by: Stefan Roese <sr@denx.de>

Thanks,
Stefan

  reply	other threads:[~2019-02-19  6:34 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-15 22:48 [U-Boot] [PATCH v2 0/5] Marvell DB-XC3-24G4XG board support Chris Packham
2019-02-15 22:48 ` [U-Boot] [PATCH v2 1/5] arm: sync armada-xp dts files from Linux 5.0 Chris Packham
2019-02-19  6:33   ` Stefan Roese
2019-04-11 11:50   ` Stefan Roese
2019-02-15 22:48 ` [U-Boot] [PATCH v2 2/5] arm: mvebu: Add Marvell's integrated CPUs Chris Packham
2019-02-19  6:34   ` Stefan Roese [this message]
2019-02-15 22:49 ` [U-Boot] [PATCH v2 3/5] arm: mvebu: NAND clock support for MSYS devices Chris Packham
2019-02-19  6:34   ` Stefan Roese
2019-02-15 22:49 ` [U-Boot] [PATCH v2 4/5] tools: kwbimage: don't adjust for image_header for Armada MSYS Chris Packham
2019-02-18  7:13   ` Stefan Roese
2019-02-18 22:23     ` Chris Packham
2019-02-19  6:18       ` Stefan Roese
2019-02-15 22:49 ` [U-Boot] [PATCH v2 5/5] arm: mvebu: Add DB-XC3-24G4XG board Chris Packham
2019-02-19  6:37   ` Stefan Roese
2019-04-11  6:45   ` Stefan Roese
2019-04-11  7:23     ` Chris Packham
2019-04-11  8:21       ` Chris Packham
2019-04-11  8:35         ` Stefan Roese
2019-04-11 10:16           ` Chris Packham

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=04000a9e-24c1-18f3-02a9-8db9429278a0@denx.de \
    --to=sr@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 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.