mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Justin T. Gibbs" <gibbs@scsiguy.com>
To: Matthew Dharm <mdharm-kernel@one-eyed-alien.net>
Cc: Ookhoi <ookhoi@dds.nl>,
	alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org
Subject: Re: 2.4.9-ac17 Adaptec AIC7XXX problems (new driver, old one works fine) (solved)
Date: Sun, 30 Sep 2001 10:15:30 -0600	[thread overview]
Message-ID: <200109301615.f8UGFUY62492@aslan.scsiguy.com> (raw)
In-Reply-To: Your message of "Sun, 30 Sep 2001 00:03:27 PDT." <20010930000327.F2665@one-eyed-alien.net>

>Hrm... this makes me wonder if the Byte Merge option is keeping the PCI
>consistancy rules, or perhaps the aic7xxx driver is making assumptions
>about when PCI writes are actually occuring, without doing a read cycle
>between critical writes to make sure they actually happen.

See my other post on this subject.  The driver knows that a read is
required to ensure that a write is posted, but assumes that 8bit
transactions are forwarded as such, writes are issued in the order
retired (we use a memory barrier to avoid the compiler using a
different order), and that reads cannot pass posted writes.

--
Justin

  parent reply	other threads:[~2001-09-30 16:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-29 14:22 2.4.9-ac17 Adaptec AIC7XXX problems (new driver, old one works fine) Ookhoi
2001-09-29 14:43 ` arjan
2001-09-29 15:33   ` Ookhoi
2001-09-30  0:12   ` Justin T. Gibbs
2001-09-30  0:11 ` Justin T. Gibbs
2001-09-30  6:57   ` 2.4.9-ac17 Adaptec AIC7XXX problems (new driver, old one works fine) (solved) Ookhoi
2001-09-30  7:03     ` Matthew Dharm
2001-09-30 10:21       ` Gérard Roudier
2001-09-30 16:15       ` Justin T. Gibbs [this message]
2001-09-30 16:13     ` Justin T. Gibbs
2001-09-30 16:35       ` Justin T. Gibbs

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=200109301615.f8UGFUY62492@aslan.scsiguy.com \
    --to=gibbs@scsiguy.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mdharm-kernel@one-eyed-alien.net \
    --cc=ookhoi@dds.nl \
    /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®