From: Pete Popov <ppopov@mvista.com>
To: Wayne Gowcher <wgowcher@yahoo.com>
Cc: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>,
linux-mips@oss.sgi.com
Subject: Re: Configuration of PCI Video card on a BIOS-less board
Date: Thu, 10 May 2001 10:44:08 -0700 [thread overview]
Message-ID: <3AFAD368.9B70E1D5@mvista.com> (raw)
In-Reply-To: Pine.GSO.4.10.10105101919230.14224-100000@rose.sonytel.be
Geert Uytterhoeven wrote:
>
> On Thu, 10 May 2001, Pete Popov wrote:
> > Are you really trying to assign 0xC000 0000 to the card or was that just
> > an example address? Unless your pci to memory window is such that
> > there's a translation that occurs, that address is incorrect. If the
> > window is 1:1, the physical address 0xC000 0000 does not exist. You
> > need to assign the card a real physical address; if your system has 32MB
> > of memory, than that address would have to be between 0 and 0x2000000.
> > (well, you can't give it address "0" because of interrupt vectors, but
> > you get the point). I can point you to some examples if you have
> > problems.
>
> If you have 32 MB of RAM and you put a PCI card at an address between 0 and
> 0x2000000 you'll have a problem! PCI cards must not overlap with real memory.
Sorry Wayne, I'm working on an ethernet driver and was thinking of
descriptors and data buffers for PCI ethernet cards, which have to be in
real physical memory. Geert is right, but 0xC000 0000 still seems
suspicious. That's a very high physical address and pci devices are
usually mapped at lower addresses. Something like 0x2000 0000 is more
reasonable and makes accessing the card through kseg1 possible.
Pete
next prev parent reply other threads:[~2001-05-10 17:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-10 5:55 Configuration of PCI Video card on a BIOS-less board Wayne Gowcher
2001-05-10 6:01 ` Keith M Wesolowski
2001-05-10 6:15 ` Geert Uytterhoeven
2001-05-10 17:11 ` Pete Popov
2001-05-10 17:20 ` Geert Uytterhoeven
2001-05-10 17:44 ` Pete Popov [this message]
2001-05-10 17:53 ` Wayne Gowcher
2001-05-10 18:12 ` Pete Popov
2001-05-10 18:43 ` Wayne Gowcher
2001-05-10 20:14 ` Keith M Wesolowski
2001-05-10 21:15 ` Pete Popov
2001-05-18 20:23 ` Netscape on linux-mipsel ?? Wayne Gowcher
2001-05-18 20:29 ` Pete Popov
2001-05-19 3:50 ` Ralf Baechle
2001-05-10 22:02 ` Configuration of PCI Video card on a BIOS-less board Jun Sun
2001-05-11 0:19 ` Wayne Gowcher
2001-05-10 18:23 ` Geert Uytterhoeven
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=3AFAD368.9B70E1D5@mvista.com \
--to=ppopov@mvista.com \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=linux-mips@oss.sgi.com \
--cc=wgowcher@yahoo.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 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.