mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Terence Ripperda <tripperda@nvidia.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: tripperda@nvidia.com
Subject: 64-bit pci bar on a 32-bit kernel
Date: Thu, 24 Feb 2005 14:22:19 -0600	[thread overview]
Message-ID: <20050224202218.GK4801@hygelac> (raw)

Hello,

we've gotten a customer report of a problem whereby our framebuffer is
not visible through the kernel. the kernel data structures in struct
pci_dev have bar1 (our framebuffer) set to 0, and the bar does not
appear in /proc/pci.

after a little investigation, it appears that the bios allocated a
64-bit bar in pci config space. our gpu claims 64-bit support in pci
config space and the cpu is an em64t. but the customer is running a
32-bit kernel on the em64t, which is a reasonable thing to do. it
turns out the pci driver does not like 64-bit bars on a 32-bit kernel
and prints out the following messages during boot:

PCI: PCI BIOS revision 2.10 entry at 0xf0031, last bus=5
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
PCI: Ignoring BAR0-3 of IDE controller 00:1f.1
PCI: Unable to handle 64-bit address space for
PCI: Unable to handle 64-bit address space for
PCI: Unable to handle 64-bit address for device 03:00.0
PCI: Unable to handle 64-bit address space for

Is this an expected problem? Is there any reason why the 32-bit kernel
couldn't handle 64-bit bars?

here's what pci config space for our gpu looks like:

00: de 10 ce 00 07 01 10 00 a2 00 00 03 10 00 00 00
10: 00 00 00 de 0c 00 00 f8 0f 00 00 00 04 00 00 dd
20: 00 00 00 00 00 00 00 00 00 00 00 00 de 10 43 02
30: 00 00 ee df 60 00 00 00 00 00 00 00 0a 01 00 00

Thanks,
Terence


             reply	other threads:[~2005-02-24 20:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-24 20:22 Terence Ripperda [this message]
2005-02-24 21:03 ` Jeff Garzik
2005-02-24 22:34 ` Brian Gerst

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=20050224202218.GK4801@hygelac \
    --to=tripperda@nvidia.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®