From: Kenneth Johansson <kenneth@southpole.se>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Add mpc5125ads board and processor to the mpc512x family
Date: Wed, 21 Oct 2009 17:20:24 +0200 [thread overview]
Message-ID: <1256138424.22238.65.camel@kenjo-laptop> (raw)
In-Reply-To: <4b73d43f0910191545x3127cba5w7fdec3f6382138e3@mail.gmail.com>
On Mon, 2009-10-19 at 16:45 -0600, John Rigby wrote:
> Regarding 512x psc register maps:
>
> The register map for 5125 does not just change the size of the registers.
> Some registers change locations. The issue is that the hardware guys
> decided to "fix" the old broken register access. The 5200, 5121, 5123 had
> some registers that were:
>
> Function A when read but function B when written.
I would like to hear what the designer had for argument to justify that
solution. Another favorite is the write only register.
GPIO without set/reset registers that force a read/modify/write cycle.
Then we have things that are more bugs than design
The "god" register that is not affected by any reset turning a
reboot/reset into a game of chance.
The occasional write register.
do {
*reg =xx
}while (*reg != xx)
next prev parent reply other threads:[~2009-10-21 15:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-13 17:45 [U-Boot] [PATCH] Add mpc5125ads board and processor to the mpc512x family m stan
2009-10-18 19:46 ` Wolfgang Denk
2009-10-19 22:45 ` John Rigby
2009-10-20 21:58 ` Wolfgang Denk
2009-10-21 15:20 ` Kenneth Johansson [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-10-20 13:53 m stan
2009-10-20 20:57 ` Wolfgang Denk
2009-10-08 7:40 Martha Stan
2009-10-13 10:02 ` Wolfgang Denk
2009-10-04 14:20 m marx
2009-10-04 15:44 ` Wolfgang Denk
2009-09-21 20:27 Martha M Stan
2009-09-21 21:09 ` Fabio Estevam
2009-10-03 22:43 ` 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=1256138424.22238.65.camel@kenjo-laptop \
--to=kenneth@southpole.se \
--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