From: Yinghai Lu <yinghai@kernel.org>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: sumit chaudhary <flyingbee.linux@gmail.com>, linux-pci@vger.kernel.org
Subject: Re: 64 bit address to a pcie card
Date: Thu, 5 Jul 2012 17:14:49 -0700 [thread overview]
Message-ID: <CAE9FiQWCeBRfwA2D+GoLCv+97KbzA5c-Fv76NZz7BOyLE7HoWQ@mail.gmail.com> (raw)
In-Reply-To: <CAErSpo5_srroOSahe3tdeD_UQVfbqe4ixZtKfVJqc7a9-j3SQg@mail.gmail.com>
On Thu, Jul 5, 2012 at 8:16 AM, Bjorn Helgaas <bhelgaas@google.com> wrote:
> [Added back cc: linux-pci so others can help, too]
>
> What exactly is the problem? Is there a device that isn't working as expected?
>
> The device at 07:00.0 does indeed have 64-bit BARs, and they happen to
> be assigned addresses below 4GB:
>
> pci 0000:07:00.0: reg 10: [mem 0xfddff000-0xfddfffff 64bit]
> pci 0000:07:00.0: reg 18: [mem 0xbf000000-0xbfffffff 64bit pref]
> pci 0000:07:00.0: reg 20: [mem 0x40000000-0x7fffffff 64bit pref]
>
> This is perfectly normal. The fact that the BAR supports a full
> 64-bit address doesn't mean it has to be assigned space above 4GB.
> The BIOS assigned these addresses, and Linux found no reason to change
> them, so we just left them alone.
The system only has 1G ram installed, and the card need 1G 64bit pref.
Maybe BIOS could push that above 4G, if the system get 4G RAM installed.
Yinghai
next prev parent reply other threads:[~2012-07-06 0:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-04 6:33 64 bit address to a pcie card sumit chaudhary
2012-07-04 13:59 ` Bjorn Helgaas
[not found] ` <CAJkVMNpZaMKm8tc+axdOBySpp68_j=EegEUOO+B=cYudsxNCgw@mail.gmail.com>
2012-07-05 15:16 ` Bjorn Helgaas
2012-07-06 0:14 ` Yinghai Lu [this message]
2012-07-06 3:49 ` Bjorn Helgaas
2012-07-09 5:39 ` sumit chaudhary
2012-07-09 8:41 ` Yinghai Lu
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=CAE9FiQWCeBRfwA2D+GoLCv+97KbzA5c-Fv76NZz7BOyLE7HoWQ@mail.gmail.com \
--to=yinghai@kernel.org \
--cc=bhelgaas@google.com \
--cc=flyingbee.linux@gmail.com \
--cc=linux-pci@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;
as well as URLs for NNTP newsgroup(s).