From: Ryan Pipkin <ryan.pipkin@inet.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Data abort during type 0 pci scan
Date: Tue, 02 Dec 2003 18:51:31 -0600 [thread overview]
Message-ID: <3FCD3393.9080905@inet.com> (raw)
Hello,
I am attempting to setup the pci_controller device for my target board.
PCI Type 0 configuration addresses are directly mapped into local memory
so I am not using the indirect method.
I have routed everything to be dword accessed like
board/dave/common/pci.c:189
It appears that the pci_hose_scan_bus uses type 1 addresses when
scanning the pci bus.
In my read_dword: and write_dword I convert the dev (type 1 address)
into an appropriate type 0 address.
Is this the correct method for doing type0 scanning ?
In addition, the ixp2800 processor will data abort when scanning a type
0 address that is not present.
In our simple bootloader we implemented the data abort handler to catch
these exceptions and continue to scan.
I have not been able to find an example in the uboot code of a data
abort that is anything but fatal.
Has anyone else run into this ?
Thanks.
------------------------------------------------------------------------
Confidentiality Notice: This e-mail transmission may contain
confidential and/or privileged information that is intended only for the
individual or entity named in the e-mail address. If you are not the
intended recipient, you are hereby notified that any disclosure,
copying, distribution or reliance upon the contents of this e-mail
message is strictly prohibited. If you have received this e-mail
transmission in error, please reply to the sender, so that proper
delivery can be arranged, and please delete the message from your
computer. Thank you.
Inet Technologies, Inc.
------------------------------------------------------------------------
reply other threads:[~2003-12-03 0:51 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=3FCD3393.9080905@inet.com \
--to=ryan.pipkin@inet.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