The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Terence Ripperda <tripperda@nvidia.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 64-bit pci bar on a 32-bit kernel
Date: Thu, 24 Feb 2005 16:03:46 -0500	[thread overview]
Message-ID: <421E4132.4010006@pobox.com> (raw)
In-Reply-To: <20050224202218.GK4801@hygelac>

Terence Ripperda wrote:
> 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?

hmmm, that's a good question.

I wonder if ioremap() even supports 64-bit addresses on 32-bit platforms?

64-bit MMIO is a bit different from 64-bit DMA; though its still only 
page tables...

	Jeff




  reply	other threads:[~2005-02-24 21:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-24 20:22 64-bit pci bar on a 32-bit kernel Terence Ripperda
2005-02-24 21:03 ` Jeff Garzik [this message]
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=421E4132.4010006@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tripperda@nvidia.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