From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/3] tqm85xx: Update PCI code
Date: Thu, 28 Oct 2010 23:20:42 +0200 [thread overview]
Message-ID: <20101028212042.4EB64152451@gemini.denx.de> (raw)
In-Reply-To: <1288298646.8967.130.camel@petert>
Dear Peter Tyser,
In message <1288298646.8967.130.camel@petert> you wrote:
>
> So the original behavior of the TQM board was out of sync with the
> majority of other boards, and some boards have a newline.
Let's say a large number of board maintainers do not care about nice
formatting of the output.
So if we use common code for a certain set, please let's not use the
lowest common denominator.
> I agree we should get rid of the newline on all these printfs, but the
> indentation issue is murkier to me. The common Freescale PCI code
> currently assumes there is an indentation, so we should really sync
> boards'/FSL indentation up to be consistent. Anyone have a strong
> preference for the indentation? p2020 way, or socrates way above?
Why should the PCI output be indented? It is not so on any other board
I ever had my fingers on.
Example - all APM boards look like that:
CPU: AMCC PowerPC 460EX Rev. B at 1066.667 MHz (PLB=266 OPB=88 EBC=88)
Security/Kasumi support
Bootstrap Option H - Boot ROM Location I2C (Addr 0x52)
Internal PCI arbiter enabled
32 kB I-Cache 32 kB D-Cache
Board: Canyonlands - AMCC PPC460EX Evaluation Board, 1*PCIe/1*SATA, Rev. 16
I2C: ready
DRAM: 512 MiB (ECC not enabled, 533 MHz, CL4)
FLASH: 64 MiB
NAND: 128 MiB
PCI: Bus Dev VenId DevId Class Int
PCIE1: link is not up.
DTT: 1 is 27 C
Net: ppc_4xx_eth0, ppc_4xx_eth1
...
Output starts in the first column, all nicely aligned.
> > Scanning PCI bus 00
> > PCIE1 on bus 00 - 00
>
> I just sent a patch to address this issue.
Thanks.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Boykottiert Microsoft - Kauft Eure Fenster bei OBI!
next prev parent reply other threads:[~2010-10-28 21:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-29 18:37 [U-Boot] [PATCH 1/3] mpc8641hpcn: Update PCI code Peter Tyser
2010-09-29 18:37 ` [U-Boot] [PATCH 2/3] sbc8641d: " Peter Tyser
2010-10-20 6:37 ` Kumar Gala
2010-09-29 18:37 ` [U-Boot] [PATCH 3/3] tqm85xx: " Peter Tyser
2010-10-20 6:37 ` Kumar Gala
2010-10-26 19:54 ` Wolfgang Denk
2010-10-27 5:15 ` Peter Tyser
2010-10-27 6:47 ` Wolfgang Denk
2010-10-28 20:44 ` Peter Tyser
2010-10-28 21:20 ` Wolfgang Denk [this message]
2010-10-28 20:24 ` [U-Boot] [PATCH] fsl_pci_init: Make fsl_pci_init_port() PCI/PCIe aware Peter Tyser
2010-11-13 22:53 ` Wolfgang Denk
2010-11-14 15:01 ` Peter Tyser
2010-11-14 22:46 ` Wolfgang Denk
2010-10-20 6:37 ` [U-Boot] [PATCH 1/3] mpc8641hpcn: Update PCI code Kumar Gala
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=20101028212042.4EB64152451@gemini.denx.de \
--to=wd@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 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.