From: "Tom Cernius" <tcernius@correlant.com>
To: <ppopov@mvista.com>
Cc: <linux-mips@linux-mips.org>
Subject: FW: Db1500 PCI Auto Scan Question
Date: Wed, 11 Jun 2003 15:12:18 -0700 [thread overview]
Message-ID: <000201c33066$8623dac0$d452dad1@correlant.com> (raw)
Hello,
I am porting my first PCI driver for a PCI card hosted by the AMD Db1500
"Zinfandel" development board.
This driver had been previously working on another host, where
CONFIG_PCI_AUTO was not enabled.
My PCI card REQUIRES 0xFF000000 and 0x90000000 be programmed into BAR0
and BAR1 respectively.
My PCI card has nothing programmed into BAR0 and BAR1 at power-up.
My host Linux kernel was built with CONFIG_PCI, CONFIG_NEW_PCI, and
CONFIG_PCI_AUTO turned on in the .config file.
I noticed that during boot, the kernel tickles my devices BAR's and
then writes these BARs with addresses in the range of
4000 0000 thru 43FF FFFF
I have tried everything and although I am able to write the proper
(0xFF00 0000 and 0x9000 0000) addresses into the BAR's,
I have been unable to successfully read anything from my PCI cards CPU
Register/Sdram space.
I suspect that it is NOT possible to use hardcoded PCI BAR addresses
with the MIPS processor AND CONFIG_PCI_AUTO turned on,
as the kernel expects (and configures the PCI BARS of) PCI devices to
reside in the address space 0x4000 0000 thru 0x43FF FFFF ??
I tried disabling the device, updating my BARS, reenabling in the
driver code (a loadable module).
I tried writing the BARS just prior to tickling in the
linux/arch/mips/kernel/pci_auto.c code.
I tried writing the BARS as soon as my device/vendor id are detected
also in the linux/arch/mips/kernel/pci_auto.c code.
Thanks,
Tom
WARNING: multiple messages have this Message-ID (diff)
From: "Tom Cernius" <tcernius@correlant.com>
To: ppopov@mvista.com
Cc: linux-mips@linux-mips.org
Subject: FW: Db1500 PCI Auto Scan Question
Date: Wed, 11 Jun 2003 15:12:18 -0700 [thread overview]
Message-ID: <000201c33066$8623dac0$d452dad1@correlant.com> (raw)
Message-ID: <20030611221218.1MhLnDxtRt5P6HysAk4Jx2bfjktWqlOZC6HsL1yA9jI@z> (raw)
Hello,
I am porting my first PCI driver for a PCI card hosted by the AMD Db1500
"Zinfandel" development board.
This driver had been previously working on another host, where
CONFIG_PCI_AUTO was not enabled.
My PCI card REQUIRES 0xFF000000 and 0x90000000 be programmed into BAR0
and BAR1 respectively.
My PCI card has nothing programmed into BAR0 and BAR1 at power-up.
My host Linux kernel was built with CONFIG_PCI, CONFIG_NEW_PCI, and
CONFIG_PCI_AUTO turned on in the .config file.
I noticed that during boot, the kernel tickles my devices BAR's and
then writes these BARs with addresses in the range of
4000 0000 thru 43FF FFFF
I have tried everything and although I am able to write the proper
(0xFF00 0000 and 0x9000 0000) addresses into the BAR's,
I have been unable to successfully read anything from my PCI cards CPU
Register/Sdram space.
I suspect that it is NOT possible to use hardcoded PCI BAR addresses
with the MIPS processor AND CONFIG_PCI_AUTO turned on,
as the kernel expects (and configures the PCI BARS of) PCI devices to
reside in the address space 0x4000 0000 thru 0x43FF FFFF ??
I tried disabling the device, updating my BARS, reenabling in the
driver code (a loadable module).
I tried writing the BARS just prior to tickling in the
linux/arch/mips/kernel/pci_auto.c code.
I tried writing the BARS as soon as my device/vendor id are detected
also in the linux/arch/mips/kernel/pci_auto.c code.
Thanks,
Tom
next reply other threads:[~2003-06-11 22:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-11 22:12 Tom Cernius [this message]
2003-06-11 22:12 ` FW: Db1500 PCI Auto Scan Question Tom Cernius
2003-06-11 23:22 ` Pete Popov
2003-06-12 2:15 ` FW: Db1500 PCI Auto Scan Question, bus master operation fpga dsp
2003-06-12 4:22 ` fpga dsp
2003-06-12 17:12 ` Pete Popov
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='000201c33066$8623dac0$d452dad1@correlant.com' \
--to=tcernius@correlant.com \
--cc=linux-mips@linux-mips.org \
--cc=ppopov@mvista.com \
/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