Alan Cox wrote: > This makes no sense. If the SETXFER failed how did the device get into > the mode it is in ? How will change down work ? Why does the old IDE > driver work ? IDE ignores SETXFER failure and for SATA devices SETXFER doesn't really mean anything (unless it's bridged). In this case, IDE didn't seem to be seeing SETXFER failures but the chip being quite weird (SETXFER failure is associated with the specific device slot not the device itself. it's probably a bridge problem.) and from the vendor it's from, I thought whatever works is okay. > I think this needs a lot more explanation Feel free to re-open bug 8563. I'd be happy to help. :-) Thanks. -- tejun - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
