Messages in this thread |  | | Date | Thu, 29 Nov 2001 20:40:06 +0100 (CET) | From | Gérard Roudier <> | Subject | Re: sym53c875: reading /proc causes SCSI parity error |
| |
On Wed, 28 Nov 2001, David S. Miller wrote:
> 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.
OK. I ignored that such weirdness existed.
Gérard.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |