linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Willy Tarreau <willy@w.ods.org>
To: "Justin T. Gibbs" <gibbs@scsiguy.com>
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] aic7xxx bouncing over 4G
Date: Sat, 28 Dec 2002 22:04:01 +0100	[thread overview]
Message-ID: <20021228210401.GA596@alpha.home.local> (raw)
In-Reply-To: <705128112.1041102818@aslan.scsiguy.com>

On Sat, Dec 28, 2002 at 12:13:38PM -0700, Justin T. Gibbs wrote:
> 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.

Thanks for this clear description, Justin. I now understand why I've had
problems in the past with earlier versions here, since I have other devices
(eg dl2k) which can't do MMIO on my system.

Cheers,
Willy


  parent reply	other threads:[~2002-12-28 20:55 UTC|newest]

Thread overview: 43+ 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-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 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:52                       ` J.A. Magallon
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:43               ` Tomas Szepe
     [not found]                 ` <20021228231122.GC1999@werewolf.able.es>
2002-12-28 23:45                   ` [BUG] new aic code [was Re: [PATCH] aic7xxx bouncing over 4G ] J.A. Magallon
2002-12-28 19:42             ` [PATCH] aic7xxx bouncing over 4G Doug Ledford
2002-12-28 21:04             ` Willy Tarreau [this message]
2002-12-28 22:37             ` David Lang
2002-12-29 12:54             ` Arjan van de Ven
2003-01-03 15:28               ` Justin T. Gibbs
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=20021228210401.GA596@alpha.home.local \
    --to=willy@w.ods.org \
    --cc=gibbs@scsiguy.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;
as well as URLs for NNTP newsgroup(s).