All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Tyser <ptyser@xes-inc.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/3] XPedite5370 board support
Date: Wed, 19 Nov 2008 12:00:50 -0600	[thread overview]
Message-ID: <1227117650.3065.124.camel@localhost.localdomain> (raw)
In-Reply-To: <49244D05.8020706@freescale.com>

Hi Jon,

On Wed, 2008-11-19 at 11:29 -0600, Jon Loeliger wrote:
> Peter Tyser wrote:
> 
> >>> We have the standard Freescale DDR printf's turned into debug as that is
> >>> much, much more verbose than the output above.
> >> Indeed :-(
> 
> Hrm.  Out of curiosity, which printf()s do you find noisy?

There are some printf()s related to chip/bank interleaving in
cpu/mpc8xxx/main.c:
	printf("\nMemory controller interleaving enabled: ");
	printf("Cache-line interleaving!\n");
	printf("Bank(chip-select) interleaving enabled: ");
	printf("CS0+CS1 and CS2+CS3\n");

I do think the info is useful, just a bit wordy (and are the !'s
necessary:).  With those printfs in main.c enabled, there could be 4
printf lines on bootup related to DDR - clocking, size, and 2 for
interleaving.

> > Many boards I look at don't use TABS.  In particular Freescale reference
> > platforms.  Many boards even have different amounts of spaces:)  I don't
> > see the value of indentation in this case as it doesn't increase
> > readability and just makes already long lines even longer.
> 
> Really?  Which ones?  We should clean those up!

The MPC8548CDS and MPC8349EMDS headers were the 2 I looked at that had
inconsistent spacing, but I didn't look all that thoroughly.  An 'ls
include/configs/MPC* | xargs grep -i "^\ \+\""' should show the boards
which don't use proper indentation for the environment variables in
general.

So much cleanup, so little time:)

Best,
Peter

  reply	other threads:[~2008-11-19 18:00 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-23 22:23 [U-Boot] [PATCH 0/3] Support for XPedite5370 and misc GPIO Peter Tyser
2008-10-23 22:23 ` [U-Boot] [PATCH 1/3] Add support for PCA953x I2C gpio devices Peter Tyser
2008-10-23 22:23   ` [U-Boot] [PATCH 2/3] Add support for Maxim's DS4510 I2C device Peter Tyser
2008-10-23 22:23     ` [U-Boot] [PATCH 3/3] XPedite5370 board support Peter Tyser
2008-10-24 23:21       ` Andy Fleming
2008-10-25  0:30         ` Peter Tyser
2008-11-18 21:44       ` Wolfgang Denk
2008-11-18 22:13         ` Peter Tyser
2008-11-18 22:20           ` Wolfgang Denk
2008-11-18 22:39             ` Peter Tyser
2008-11-18 23:03               ` Wolfgang Denk
2008-11-19 17:29               ` Jon Loeliger
2008-11-19 18:00                 ` Peter Tyser [this message]
2008-11-18 21:37     ` [U-Boot] [PATCH 2/3] Add support for Maxim's DS4510 I2C device Wolfgang Denk
2008-11-18 21:57       ` Peter Tyser
2008-11-18 23:16         ` Wolfgang Denk
2008-11-18 21:33   ` [U-Boot] [PATCH 1/3] Add support for PCA953x I2C gpio devices Wolfgang Denk
2008-11-18 21:51     ` Peter Tyser
2008-11-18 23:11       ` Wolfgang Denk
2008-11-18 21:29 ` [U-Boot] [PATCH 0/3] Support for XPedite5370 and misc GPIO 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=1227117650.3065.124.camel@localhost.localdomain \
    --to=ptyser@xes-inc.com \
    --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.