mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Yinghai Lu" <yinghai.lu@amd.com>
To: yadviga <yadviga@ru.mvista.com>, "Greg KH" <gregkh@suse.de>,
	"Andrew Morton" <akpm@osdl.org>
Cc: "Linux Kernel ML" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] large pci adress space in pci/probe.c for linux-2.6.18
Date: Mon, 20 Nov 2006 07:59:19 -0800	[thread overview]
Message-ID: <86802c440611200759t6c6bbac9od4a3837a05906760@mail.gmail.com> (raw)
In-Reply-To: <4561CBF9.CA21F786@ru.mvista.com>

On 11/20/06, yadviga <yadviga@ru.mvista.com> wrote:
> This is a request from Cisco to update pci address space for 64-bit mips
> Cavium Octeon.
>
> The size returned by a 4GB or greater sized BAR register returns zero
> which made the algorithm in pci_read_bases() hit a continue instead of
> continuing to read the upper 32-bits of the address space. I needed to
> add the code to check if it was a 64-bit memory space by checking the
> relevant lower bits, in which case the lower 32-bits of the size are
> 0xffffffff by the way they calculate size. As far as I can tell this has
> still not been fixed in the latest release of Linux which is 2.6.18. I
> guess no one has
> encountered such a large BAR register yet.
>

There is one version and it is G HK tree. and Adrew has cleaned that code.

for AMD K8 system with co-processor installed in opteron socket, the
co-processor may have 4G above ram installed.

YH

      reply	other threads:[~2006-11-20 15:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-20 15:38 yadviga
2006-11-20 15:59 ` Yinghai Lu [this message]

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=86802c440611200759t6c6bbac9od4a3837a05906760@mail.gmail.com \
    --to=yinghai.lu@amd.com \
    --cc=akpm@osdl.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yadviga@ru.mvista.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

all inboxes | Powered by JetHome®