From: Ron Rondis <ron.rondis@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: 64 bit PCI BAR
Date: Thu, 04 Nov 2010 07:51:26 +0200 [thread overview]
Message-ID: <4CD249DE.1050301@gmail.com> (raw)
Hi,
The following section, from PCI spec, explain the mechanism for getting
64 bit region size.
"64-bit (memory) Base Address registers can be handled the same, except
that the second
32-bit register is considered an extension of the first; i.e., bits
32-63. Software writes
0FFFFFFFFh to both registers, reads them back, and combines the result
into a 64-bit value.
Size calculation is done on the 64-bit value."
In pci/proce.c the implementation is:
read low bar
write ~0 to low bar
read low bar
write low bar
read high bar
write ~0 to high bar
read high bar
write high bar
Can someone explain the conflict between the spec and the implementation?
Please add me to CC.
Thanks,
Ron
reply other threads:[~2010-11-04 5:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4CD249DE.1050301@gmail.com \
--to=ron.rondis@gmail.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