> fact even io_delay=udelay would be wrong because any problem will be > less clearly triggerable and thus less bisectable/debuggable.
And if this eats someones disk because you drive the hardware out of spec you are going to sit there and tell them to bisect it ? Lovely. Ingo - put the christmas wine away and have a coffee. Now think first. You won't bisect obscure timing triggered problems, and the _p users are almost all for hardware where performance doesn't matter one iota (eg CMOS). This isn't even all down to the chipset internal logic - several of my boxes have external CMOS NVRAM/RTC chips which are probably the same design (if a little smaller) as ten years ago. io_delay = none is exactly the same thing as CPU overclocking. Hard to debug, unpredictable and stupid. Alan -- 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/
