public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockrwd@gmail.com>
To: protagora27 protagora27 <protagora27@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: pci express bar over 4gb
Date: Wed, 11 Mar 2009 18:01:59 -0600	[thread overview]
Message-ID: <49B850F7.90401@gmail.com> (raw)
In-Reply-To: <5b9cce670903110628p45248032u50dc253ed18b6e46@mail.gmail.com>

protagora27 protagora27 wrote:
> Hello Folks,
> 
> I have intel desktop board dx48bt2. I'm developing sw under linux
> 2.6.24  x86_64  for a pci express card ( pci express 2.0 compliant).
> I have to setup pci bar over 4 gb but bios uses value e0000000 as base
> address for pcie boards.
> I have seen that pciexbar is a register ( x48 chipset)  that decides
> where pcie boards are mapped inside memory map.

No, the PCIEXBAR register controls where the MMCONFIG aperture is mapped 
in memory. (It's a rather unfortunate name, I think, as it doesn't 
really have anything to do with PCI Express other than that you need to 
use MMCONFIG to access PCI Express extended configuration space).

> My goal is rewriting pcibar 0 e pcibar 1 with a value above 4gb. Maybe
>  I have  to rewrite pciexbar and then rewrite pci bar in my board.
> Questions:
> 1) can I rewrite  pciexbar  and where ?
> 2) can i rewrite pcibar 0 and 1 with a value over 4 gb
> 3) If i change bar 0 and bar 1 after linux startup have i to use hotplugging ?
> 
> Thanks
> 
> Luca


  reply	other threads:[~2009-03-12  0:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-11 13:28 pci express bar over 4gb protagora27 protagora27
2009-03-12  0:01 ` Robert Hancock [this message]
     [not found]   ` <5b9cce670903120205yfd0cc5cp203059299877124@mail.gmail.com>
2009-03-12 14:44     ` Robert Hancock

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=49B850F7.90401@gmail.com \
    --to=hancockrwd@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=protagora27@gmail.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