mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Phillips <phillips@arcor.de>
To: Todd Inglett <tinglett@vnet.ibm.com>, linux-kernel@vger.kernel.org
Cc: Martin Mares <mj@ucw.cz>
Subject: Re: BUG: PCI driver 64-bit bar size
Date: Sat, 7 Sep 2002 13:41:35 +0200	[thread overview]
Message-ID: <E17ndy4-0006Sj-00@starship> (raw)
In-Reply-To: <1031249810.12740.72.camel@q.rchland.ibm.com>

On Thursday 05 September 2002 20:16, Todd Inglett wrote:
> Now in my case, I have an adapter that insists the upper 32-bits of a
> 64-bit BAR must be zero (don't ask me why -- doesn't make sense to me
> either, but they are indeed hard-wired).  So after plugging in ffff's
> into both BARs I effectively get 0x00000000fffff000 (again after masking
> flags).  I would expect a length of 0x1000 for this (extent 0xfff), but
> Linux computes an extent of 0xffffffffffffffff!  Since the spec says the
> length is computed from the first one bit I'll assume this is wrong. 
> The code should account for the lower dword as well as the upper.
> 
> So my fix is attached.  I chose to use pci_size() in the computation of
> the upper dword for consistency.  Perhaps there should be a defined mask
> for the upper dword in pci.h (i.e. PCI_BASE_ADDRESS_MEM_64_MASK?) rather
> than hard coding 0xffffffff.  The patch is against 2.4.20-pre4.

A bug fix like this should at least be cc'd to Marcelo.

-- 
Daniel

      reply	other threads:[~2002-09-07 11:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-05 18:16 Todd Inglett
2002-09-07 11:41 ` Daniel Phillips [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=E17ndy4-0006Sj-00@starship \
    --to=phillips@arcor.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mj@ucw.cz \
    --cc=tinglett@vnet.ibm.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®