public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Justin T. Gibbs" <gibbs@scsiguy.com>
To: arjanv@redhat.com
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
	Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH] aic7xxx bouncing over 4G
Date: Fri, 03 Jan 2003 08:28:04 -0700	[thread overview]
Message-ID: <610650816.1041607684@aslan.scsiguy.com> (raw)
In-Reply-To: <1041166487.1338.1.camel@laptop.fenrus.com>

>> The main reason why the new driver "breaks" where the old one
>> doesn't is that the new driver does not perform an extra register
>> read to work-around chipsets that screw up memory mapped I/O.  There
>> are four solutions to this problem:
> 
> just to be sure...you're not talking about PCI posting right?
> can you explain in a bit more detail the exact behavior that is the
> problem ? (I'm sure a lot of other drivers will suffer the same so I
> consider it of general interest)

PCI posting is an expected (and desired) characteristic of PCI, so, no
I'm not complaining about that.  According to the PCI spec, prefetch
is only allowed for devices that explicitly indicate that they support
it (via a bit in their BAR registers).  Further, write combining and
byte merging are only allowed for prefetchable regions.  The Adaptec
parts do not set the prefetch bit and do not support either of these
options (most registers are 8bits anyway, so there was nothing to
gain by complicating the part with this support).  Some BIOSes ignore
this rule and attempt to prefetch and/or write combine transactions
to these chips.  Other BIOSes actually have an option so that the user
can say "ignore the rules".  The new tests are designed to weed out
this broken behavior and to fallback to PIO where prefetch and write
combining cannot come into play.

--
Justin


  reply	other threads:[~2003-01-03 15:28 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-21  0:12 [PATCH] aic7xxx bouncing over 4G Janet Morgan
2002-12-21  0:23 ` Justin T. Gibbs
2002-12-21  0:29   ` William Lee Irwin III
2002-12-21  0:59     ` Justin T. Gibbs
2002-12-21  1:35       ` William Lee Irwin III
2002-12-21  1:59         ` Justin T. Gibbs
2002-12-21  4:10           ` David S. Miller
2002-12-21 15:19             ` Justin T. Gibbs
2002-12-21 21:41               ` David S. Miller
2002-12-21  7:10           ` Erik Andersen
2002-12-21 15:23             ` Justin T. Gibbs
2002-12-21  8:55           ` Christoph Hellwig
2002-12-21 15:30             ` Justin T. Gibbs
2002-12-21 17:45               ` Doug Ledford
2002-12-22  0:16                 ` Linus Torvalds
2002-12-21  0:51   ` Samuel Flory
2002-12-28  5:32     ` Marcelo Tosatti
2002-12-28  9:16       ` Tomas Szepe
2002-12-28 13:33         ` Rik van Riel
2002-12-28 13:40           ` Tomas Szepe
2002-12-28 16:23             ` Tony Spinillo
2002-12-28 15:00           ` James Bottomley
2002-12-28 19:16             ` Justin T. Gibbs
2002-12-28 20:16               ` James Bottomley
2002-12-28 21:02                 ` Justin T. Gibbs
2002-12-28 20:18               ` Andrew Morton
2002-12-28 20:50                 ` Justin T. Gibbs
2002-12-28 22:24                   ` James Bottomley
2002-12-28 22:31                     ` Justin T. Gibbs
2002-12-28 22:46                     ` Andrew Morton
2002-12-28 19:13           ` Justin T. Gibbs
2002-12-28 19:19             ` Rik van Riel
2002-12-28 19:42             ` Doug Ledford
2002-12-28 21:04             ` Willy Tarreau
2002-12-28 22:37             ` David Lang
2002-12-29 12:54             ` Arjan van de Ven
2003-01-03 15:28               ` Justin T. Gibbs [this message]
2003-01-06  1:40                 ` aic79xx bug? my stupidity? Roberto Peon
2003-01-06  1:46                   ` Justin T. Gibbs
2002-12-30 21:06           ` [PATCH] aic7xxx bouncing over 4G Samuel Flory
2002-12-28  9:50       ` Christoph Hellwig
2002-12-30  1:23       ` Alan Cox

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=610650816.1041607684@aslan.scsiguy.com \
    --to=gibbs@scsiguy.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=arjanv@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@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