Linux MIPS Architecture development
 help / color / mirror / Atom feed
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 11:12:57 -0700	[thread overview]
Message-ID: <3AFADA29.674BA111@mvista.com> (raw)
In-Reply-To: 20010510175339.83183.qmail@web11904.mail.yahoo.com

Wayne Gowcher wrote:
> 
> Geert, Pete,
> 
> Thanks for your input, it makes me question things I
> should have questioned before.

> 0xC000 0000 is the actual address I am trying to use.
> I used it because another PCI card that I have a
> driver for was using it and so I just carried on its
> use. I didnt really question the value or its use. But
> obviously it works for that card.

And this driver works on mips?  When you read the base mem register from
this card that works, it says "0xC0000000"?

> After your emails I revisited that code and now I
> partially understand why it works. The chip has an
> internal bus that translates address requests
> internally. So when i write to 0xC000 0000 it would
> never make to the actual address lines of the chip and
> instead be routed to the PCI controller ( I think :) )

I'm not clear on how this works with the good driver. If you write to
0xC000 0000, that's a mips virtual address in the kseg2 region, which is
a mapped region.  So what physical address you put on the bus when you
write to 0xC000 0000 depends on the tlb entry you've setup.  If 0xC000
0000 is truly a PCI memory physical address, then you need to setup a
tlb entry that maps some virtual address to the physical address 0xC000
0000.  I doubt you want to muck with that and would suggest you redo
your PCI bus memory map so that the PCI bus is at a lower address, like
0x1000 0000. You can then access physical 0x1000 0000 through virtual
address 0xB000 0000 (kseg1). I think you already told me, but what
board/CPU are you working with?

Pete

  reply	other threads:[~2001-05-10 18:15 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
2001-05-10 17:53     ` Wayne Gowcher
2001-05-10 18:12       ` Pete Popov [this message]
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=3AFADA29.674BA111@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox