Vivek Goyal <[email protected]> writes:
> On Sat, Jun 24, 2006 at 04:30:46AM -0700, Andrew Morton wrote:
>
>> > Or is there a generic way to handle these situations? Fixing them driver
>> > by driver is a long painful process.
>>
>> Some generic way of whacking a PCI device via the standard PCI registers?
>> Not that I know of.
>
> Somebody hinted that think of PCI bus reset. But I think PCI bus reset will
> require firware/BIOS to export a hook to software to so initiate PCI bus
> reset and I don't think many platforms do that. Infact I am not even aware
> of one platform who does that.
Not all pci busses support it but there is a standard pci bus reset bit
in pci bridges.
I don't know if it would help but it might make sense to have a config
option that can be used to mark drivers that are known to have problems,
in these scenarios.
CONFIG_BRITTLE_INIT perhaps?
It would at least make it easier for people to see which drivers
they don't want to use, and give people some incentive to fix things.
Eric
-
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]
