mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Lundell <jlundell@pobox.com>
To: Jeff Garzik <jgarzik@mandrakesoft.com>,
	"Khachaturov, Vassilii" <Vassilii.Khachaturov@comverse.com>
Cc: LINUX Kernel <linux-kernel@vger.kernel.org>
Subject: Re: ((struct pci_dev*)dev)->resource[...].start
Date: Wed, 16 May 2001 16:06:51 -0700	[thread overview]
Message-ID: <p05100306b728b73efd94@[10.128.7.49]> (raw)
In-Reply-To: <3B02F30F.5D05C77E@mandrakesoft.com>
In-Reply-To: <6B1DF6EEBA51D31182F200902740436802678ED4@mail-in.comverse-in.com> <3B02F30F.5D05C77E@mandrakesoft.com>

At 5:37 PM -0400 2001-05-16, Jeff Garzik wrote:
>This is not a safe assumption, because the OS may reprogram the PCI BARs
>at certain times.  The rule is:  ALWAYS read from dev->resource[] unless
>you are a bus driver (PCI bridges, for example, need to assign
>resources).

Would you please elaborate? If I understand what you're saying, you 
can't rely on the "pointer" returned by ioremap() because the OS 
might reprogram the relevant BAR out from under you. So one would 
need to know: when does a driver have to re-ioremap() due to the BAR 
having been (potentially) changed? I'd expect the answer to be: for 
all practical purposes never.

-- 
/Jonathan Lundell.

  parent reply	other threads:[~2001-05-16 23:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-16 20:58 Khachaturov, Vassilii
2001-05-16 21:37 ` Jeff Garzik
2001-05-17  5:36   ` Albert D. Cahalan
2001-05-16 23:06 ` Jonathan Lundell [this message]
2001-05-16 23:14   ` Jeff Garzik
2001-05-16 22:13 Khachaturov, Vassilii

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='p05100306b728b73efd94@[10.128.7.49]' \
    --to=jlundell@pobox.com \
    --cc=Vassilii.Khachaturov@comverse.com \
    --cc=jgarzik@mandrakesoft.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

all inboxes | Powered by JetHome®