From: Reinhard Meyer <u-boot@emk-elektronik.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2 V3] AT91: Makes AT91SAM9RL SoC build correctly against u-boot-atmel/master
Date: Mon, 01 Aug 2011 08:00:15 +0000 [thread overview]
Message-ID: <1312185615.3635.105.camel@ubuntu> (raw)
In-Reply-To: <1308107471-22295-1-git-send-email-hong.xu@atmel.com>
Dear Hong Xu,
> Rework for AT91SAM9RL SoC, makes it build again.
> arch/arm/include/asm/arch-at91/at91sam9rl_matrix.h | 121 +++++---------
When I compare at91sam9rl_matrix.h to at91sam9260_matrix.h there is only
one subtle difference:
at91sam9260_matrix.h:
struct at91_matrix {
u32 mcfg[16]; /* Master Configuration Registers */
u32 scfg[16]; /* Slave Configuration Registers */
u32 pras[16][2]; /* Priority Assignment Slave Registers */
u32 mrcr; /* Master Remap Control Register */
u32 filler[0x06];
u32 ebicsa; /* EBI Chip Select Assignment Register */
at91sam9rl_matrix.h:
struct at91_matrix {
u32 mcfg[16]; /* Master Configuration Registers */
u32 scfg[16]; /* Slave Configuration Registers */
u32 pras[16][2]; /* Priority Assignment Slave Registers */
u32 mrcr; /* Master Remap Control Register */
u32 filler[7];
u32 ebicsa; /* EBI Chip Select Assignment Register */
};
1. Is it really filler[7] for the 9rl - can you verify with the data
sheet?
2. It seems there is a possibility to unify all those _matrix files into
one in the future (we are not going to do this now!) ?
Best Regards,
Reinhard
next prev parent reply other threads:[~2011-08-01 8:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-15 3:11 [U-Boot] [PATCH 1/2 V3] AT91: Makes AT91SAM9RL SoC build correctly against u-boot-atmel/master Hong Xu
2011-06-15 3:11 ` [U-Boot] [PATCH 2/2 V3] AT91: Makes AT91SAM9RL-EK " Hong Xu
2011-06-22 8:14 ` Hong Xu
2011-06-22 8:13 ` [U-Boot] [PATCH 1/2 V3] AT91: Makes AT91SAM9RL SoC " Hong Xu
2011-06-22 9:03 ` Wolfgang Denk
2011-06-22 9:15 ` Hong Xu
2011-08-01 2:28 ` Reinhard Meyer
2011-08-01 8:00 ` Reinhard Meyer [this message]
2011-08-01 8:13 ` Hong Xu
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=1312185615.3635.105.camel@ubuntu \
--to=u-boot@emk-elektronik.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