Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Jon Dufresne <jon.dufresne@infinitevideocorporation.com>
Cc: Ralf Baechle <ralf@linux-mips.org>,
	linux-kernel@vger.kernel.org, linux-mips@linux-mips.org
Subject: Re: PCI resource unavailable on mips
Date: Mon, 17 Dec 2007 18:47:06 +0300	[thread overview]
Message-ID: <476699FA.5050606@ru.mvista.com> (raw)
In-Reply-To: <1197904591.3351.5.camel@microwave.infinitevideocorporation.com>

Hello.

Jon Dufresne wrote:

> I did a bit more work and investigation on this and it turns out I could
> not read the mmio in kernel space because I had not done a
> pci_enable_device_bars() on the device. I had never done this on x86 so
> I didn't realize it was necessary.

>>The virtual address 0xc0300000 looks sensible and the physical address
>>0x24000000 is consistent with what you found in the BAR registers.  So that
>>all looks reasonable but that only means not obviously wrong.  So next I
>>wonder what the value of PCI_MMIO_BASE is ...

> The PCI_MMIO_BASE is a defined as:

>>#define PCI_MMIO_BASE            (0x00040000)

> This is define in the technical documentation as the offset to access
> pci config space from the mmio.

    From what mmio? If it's for accessing a config. space why then you're 
using it as an offset from BAR?

> I am using this because I know what the
> values should be so it provides a nice sanity check.

> Any idea what I might be doing wrong? How can I access this from user
> space?

    Your example doesn't make sense to me so far.

> Thanks,
> Jon

WBR, Sergei

  reply	other threads:[~2007-12-17 15:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1197557806.3370.7.camel@microwave.infinitevideocorporation.com>
2007-12-14  9:39 ` PCI resource unavailable on mips Ralf Baechle
2007-12-14 18:32   ` Jon Dufresne
2007-12-14 21:12   ` Jon Dufresne
2007-12-16 22:46     ` Ralf Baechle
2007-12-17 15:16       ` Jon Dufresne
2007-12-17 15:47         ` Sergei Shtylyov [this message]
2007-12-18 18:11           ` Jon Dufresne
     [not found] <fa.vbvzhsk+kDPCopbmajO8EsxAnKE@ifi.uio.no>
     [not found] ` <4761C26C.3010708@shaw.ca>
2007-12-18 18:40   ` Jon Dufresne

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=476699FA.5050606@ru.mvista.com \
    --to=sshtylyov@ru.mvista.com \
    --cc=jon.dufresne@infinitevideocorporation.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.org \
    /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