From: Dan Malek <dan@embeddededge.com>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: linux-ppc-dev <linuxppc-dev@ozlabs.org>,
linux-ppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: [PLEASE REVIEW] ppc32 8xx: core PRxK board family support
Date: Mon, 14 Nov 2005 14:06:39 -0500 [thread overview]
Message-ID: <7af23fbbbf8b4b765f4d6c19f637011f@embeddededge.com> (raw)
In-Reply-To: <20051114124538.GB28633@logos.cnet>
On Nov 14, 2005, at 7:45 AM, Marcelo Tosatti wrote:
> +++ linux-2.6.14-rc4/arch/ppc/boot/include/cyc_banner.h 2005-10-25
> 07:01:57.000000000 -0500
I'm not a big fan of all of these banners, printing, and ascii
text in the kernel, but if you think you must have it ........
> +//XXX: remove? Its unused.
> +#if 0
> +struct type0000 {
> + unsigned char flash_sign[FLASH_SIGN_SIZE]; /* mark initialized
> CMOS */
> + unsigned char version; /* Configure vector version */
> + unsigned char routing_protocol; /* RIP, OSPF, etc */
> + unsigned char save_sw; /* TRUE : the RTBOOT must be
> saved into flash */
> +};
> +#endif
Yes please, remove it.
> + //[GB]May/06/05 Ethernet Receive Rate Limit
> + // unsigned char reserved1[4];
Get rid of trash like this, too, or make it a real C style comment
that explains what is going on here for the rest of us.
> +++ linux-2.6.14-rc4/arch/ppc/boot/simple/embed_config.c 2005-10-25
> 13:55:04.000000000 -0500
This is a pretty big chunk of board specific code beyond just setting
up the board configuration info. Consider making it a separate file.
> +++ linux-2.6.14-rc4/arch/ppc/platforms/cpld.h 2005-10-24
> 15:35:25.000000000 -0500
Would you name this something a little more descriptive, like
perhaps cyc_cpld.h? Makes it easier to understand where the
files are used.
> +struct fpga_pc_regs {
> + unsigned char fpga_pc_misc; // Controls PCMCIA IO's window size
I still don't like // comments ....... :-)
> +// mem_addr = (unsigned long *)(&cpmp->cp_dpmem[dp_addr]);
Just remove it.
> +// dp_addr = m8xx_cpm_dpalloc(32);
Ditto, and anywhere else. If code isn't used, let's just get
rid of it. Or put in a comment why there may be alternative
or if you are testing something.
Thanks!
-- Dan
prev parent reply other threads:[~2005-11-14 19:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-14 12:45 [PLEASE REVIEW] ppc32 8xx: core PRxK board family support Marcelo Tosatti
2005-11-14 19:06 ` Dan Malek [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=7af23fbbbf8b4b765f4d6c19f637011f@embeddededge.com \
--to=dan@embeddededge.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc-embedded@ozlabs.org \
--cc=marcelo.tosatti@cyclades.com \
/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;
as well as URLs for NNTP newsgroup(s).