public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Xiaoshan Zuo <xzuo@vinesystech.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] walnut 405gp bridge setting
Date: Tue, 14 Oct 2003 16:49:59 -0700	[thread overview]
Message-ID: <3F8C8BA7.9020204@vinesystech.com> (raw)

I have a customized walnut 405 gp board. While using u-boot the bridge 
was not set correclty. The problem was that the bridge didn't respond to 
requst. The problem was traced down to PCIC0_CMD[MA]=0 on the bridge. 
The bit is set correclty in pci_405gp_init,
later it is got changed in pci_hose_scan_bus. It is not supposed to be 
changed, as suggested by the comment below in the code. But this comment 
contradict with function pci_hose_scan_bus which intentionly doesn't 
skip the bridge.  Removing #ifndef in pci_hose_scan_bus makes the bridge 
work. My question is: is this a typo?

Where can I search for u-boot mailing list archive? linuxppc is very 
easy to serach useful information.  Sorry for the newbie question.

Thanks,

Xiaoshan

/*
 * drivers/pci.c skips every host bridge but the 405GP since it could
 * be set as an Adapter.
 *
 * I (Andrew May) don't know what we should do here, but I don't want
 * the auto setup of a PCI device disabling what is done pci_405gp_init
 * as has happened before.
 */

void pci_405gp_setup_bridge(struct pci_controller *hose, pci_dev_t dev,
                            struct pci_config_table *entry)
{
#ifdef DEBUG
        printf("405gp_setup_bridge\n");
#endif
}

In drivers/pci.c:

int pci_hose_scan_bus(struct pci_controller *hose, int bus)
{
#ifndef CONFIG_405GP /* don't skip host bridge on ppc405gp */
                /* Skip our host bridge */
                if ( dev == PCI_BDF(hose->first_busno,0,0) )
                        continue;
#endif

                 reply	other threads:[~2003-10-14 23:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3F8C8BA7.9020204@vinesystech.com \
    --to=xzuo@vinesystech.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox