All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Althoefer <stefan.althoefer@web.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] IXP425: Fixing PCI access Part 1/1
Date: Thu, 18 Dec 2008 00:52:03 +0100	[thread overview]
Message-ID: <gic38k$d52$1@ger.gmane.org> (raw)
In-Reply-To: <20081215232415.109B4832E8A1@gemini.denx.de>

Hi Wolfgang Denk,

> 
>> @@ -304,9 +355,7 @@ void pci_ixp_init (struct pci_controller
>>  	pci_write_config_word (0, PCI_CFG_COMMAND, INITIAL_PCI_CMD);
>>  	REG_WRITE (PCI_CSR_BASE, PCI_ISR_OFFSET, PCI_ISR_PSE
>>  		   | PCI_ISR_PFE | PCI_ISR_PPE | PCI_ISR_AHBE);
>> -#ifdef CONFIG_PCI_SCAN_SHOW
>> -	printf ("Device  bus  dev  func  deviceID  vendorID \n");
>> -#endif
>> +
>>  	pci_bus_scan ();
> 
> Why do you remove the message?
> 
>> -#ifdef CONFIG_PCI_SCAN_SHOW
>> -		printf ("%06d    %03d %03d %04d  %08d      %08x\n", nDevices,
>> -			devices[nDevices].vendor_id);
>> -#endif
> 
> ???
> 

I found the following initialization sequence for the IXP425:
     cpu_init() -> pci_init() -> pci_init_board() ->
	        pci_ixp_init() -> pci_bus_scan()
and later:
     serial_init()

If printf()->...->serial_putc() is called in pci_bus_scan()
before serial_init() it hung up the IXP425.

Assuming that there is good reason to call pci_init() so early,
CONFIG_PCI_SCAN_SHOW cannot be used.

Therefore I removed the dead code.

I think I noticed this in the revised version of the patch.
I'm working on a beautified version.

-- Stefan

      reply	other threads:[~2008-12-17 23:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-04 21:09 [U-Boot] [PATCH] IXP425: Fixing PCI access Part 1/1 Stefan Althoefer
2008-12-06 22:41 ` Stefan Althoefer
2008-12-15 23:25   ` Wolfgang Denk
2008-12-15 23:24 ` Wolfgang Denk
2008-12-17 23:52   ` Stefan Althoefer [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='gic38k$d52$1@ger.gmane.org' \
    --to=stefan.althoefer@web.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.