linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: groudier@free.fr
Cc: matthias@winterdrache.de, linux-kernel@vger.kernel.org
Subject: Re: sym53c875: reading /proc causes SCSI parity error
Date: Wed, 28 Nov 2001 14:49:25 -0800 (PST)	[thread overview]
Message-ID: <20011128.144925.94842859.davem@redhat.com> (raw)
In-Reply-To: <20011128203718.L2777-100000@gerard>
In-Reply-To: <20011128.131503.22504634.davem@redhat.com> <20011128203718.L2777-100000@gerard>

   From: Gérard Roudier <groudier@free.fr>
   Date: Wed, 28 Nov 2001 20:51:01 +0100 (CET)
   
   On Wed, 28 Nov 2001, David S. Miller wrote:
   
   > Why not just put some bitmap pointer into the pci device
   > struct.  If it is non-NULL, it specifies PCI config space
   > areas which have side-effects.
   
   Or a simple offset beyond which reading data isn't desirable for
   whatever reasons.

I do not think that is sufficient.

I have seen chips where only one single PCI config space word would
trigger problems, and it was due to a hw bug.  The "offset beyond"
scheme would not allow to cover this case.

  parent reply	other threads:[~2001-11-28 22:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-28 18:28 sym53c875: reading /proc causes SCSI parity error Matthias Benkmann
2001-11-28 18:14 ` Gérard Roudier
2001-11-28 19:13 ` Mathieu Chouquet-Stringer
2001-11-28 19:40   ` Matthias Benkmann
2001-11-28 19:56     ` Mathieu Chouquet-Stringer
2001-11-28 21:15 ` David S. Miller
2001-11-28 19:51   ` Gérard Roudier
2001-11-28 22:49   ` David S. Miller [this message]
2001-11-29 19:40     ` Gérard Roudier
2001-11-28 23:47   ` 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=20011128.144925.94842859.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=groudier@free.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthias@winterdrache.de \
    /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).