> One thing is that we definitely don't want to fix this by,
> for example, reading back the PCI_COMMAND register or something
> like that. That causes two problems:
>
> 1) Some PCI config writes shut the device down and make it
> no respond to some kinds of PCI config transactions.
> One example is putting the device into D3 or similar
> power state, another is performing a device reset.
Hmm... it seems there is no other guaranteed way to make sure a config
write has really completed except doing a config read. And only the
driver knows what the config access it's doing means. So the
conclusion we seem to be forced into is that drivers need to include
these reads in the cases where they are needed.
- R.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
