From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/4] ppc4xx: Overhaul for cmd reginfo
Date: Sun, 4 Oct 2009 13:31:06 +0200 [thread overview]
Message-ID: <200910041331.06432.sr@denx.de> (raw)
In-Reply-To: <1254507131-32670-2-git-send-email-niklaus.giger@member.fsf.org>
Hi Niklaus,
On Friday 02 October 2009 20:12:07 Niklaus Giger wrote:
> The command "reginfo" got an overhaul for the ppc4xx. It dumps all the
> relevant HW configuration registers (address, symbolic name, content).
> This allows to easily detect errors in *.h files and changes in the HW
> configuration.
Thanks.
> It is split in the following parts:
> - Cleanup some HW register names:
> Here you find all the changes in the include directory for new register
> names and adapting other ones to the names used by AMCC in their manuals,
> e.g. For 440EPx/GRPPC440EPx/GRX, Revision 1.15 ??? September 22, 2008 For
> PPC405GP Embedded Processor, Revision 1.02 ??? March 22, 2006 - Apply new
> HW register names
> Modify all existing *.c files to use the new register names
> - Rework cmd reginfo
> Here the real work done to improve the reginfo command.
> - respect 80-chars per line in ppc*.h files
> After running checkstyle.pl on the three previous patches I noted that in
> the *.h files there were a lot of long lines. This patch solves this
> problem.
A general comment to all your 4 patches. Please put the description here also
into the patches itself. This patch (0/4) won't be applied, so this
information is lost.
> I tested the changes on my PPC405GPr board HCU4 and PPC440EPx board HCU5.
>
> Only ran MAKEALL 4xx as I have no other cross-compilers installed.
>
> The DMA-registers are not dumped for the PPC440.
>
> I know that I could spend not only many hours but weeks to cleanup all the
> PPC4xx register naming conventions.
Right, this is time consuming. Thanks for your effort so far. Really
appretiated.
Cheers,
Stefan
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-0 Fax: (+49)-8142-66989-80 Email: office at denx.de
prev parent reply other threads:[~2009-10-04 11:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-02 18:12 [U-Boot] [PATCH 0/4] ppc4xx: Overhaul for cmd reginfo Niklaus Giger
2009-10-02 18:12 ` Niklaus Giger
2009-10-02 18:12 ` [U-Boot] [PATCH 1/4] ppc4xx: Cleanup some HW register names Niklaus Giger
2009-10-02 18:12 ` [U-Boot] [PATCH 2/4] ppc4xx: Apply new " Niklaus Giger
2009-10-02 18:12 ` [U-Boot] [PATCH 3/4] ppc4xx: Rework cmd reginfo Niklaus Giger
2009-10-02 18:12 ` [U-Boot] [PATCH 4/4] ppc4xx: respect 80-chars per line in ppc*.h files Niklaus Giger
2009-10-04 11:51 ` [U-Boot] [PATCH 3/4] ppc4xx: Rework cmd reginfo Stefan Roese
2009-10-04 11:36 ` [U-Boot] [PATCH 1/4] ppc4xx: Cleanup some HW register names Stefan Roese
2009-10-04 15:39 ` Niklaus Giger
2009-10-07 7:34 ` Stefan Roese
2009-10-04 11:31 ` Stefan Roese [this message]
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=200910041331.06432.sr@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox