Ross Biro <[EMAIL PROTECTED]> writes: > > I even have a single motherboard with both a device that cannot handle > the target abort and an IDE controller that can handle the target > abort behind the same bridge. For this motherboard, I have to choose > the lesser of two evils, network hiccups or potential data corruption. > For the record, I have seen both occur. Other people may make wish to > make a different choice than we did, hence this patch allows the user > to choose the mode at runtime.
I think it is totally wrong to make this Configs and boot options. Nobody can do anything with such obscure boot configurations and it is bad to require kernel recompiles for such things. The right way to do this would be to have sysfs knobs that allow to change these bits, and then let a user space tool change it depending on PCI-ID. If the issue is critical enough that it happens very often then it should be added to kernel pci quirks - but again be unconditional. -Andi - 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/
