On Maw, 2006-04-18 at 13:34 +0200, Andreas Mohr wrote: > However, while this is much better than a compile-time setting, it's still > not fully satisfying since many users won't realize that they're hitting this > problem and thus won't search for and find this obscure boot parameter. > Is there any way at all to get this condition detected automatically? Not that I can think off immediately. The controller and the drive both report the modes they support. If that is wrong then we either need to be able to identify the specific device (as libata does with the Palmax systems) or try it and see (which we indeed do but takes time to error out). For PCMCIA CF adapters we are ok because they are ISA bus so PIO 0 cycles are all that are supported. For other controllers it will depend whether the CF adapter is integrated into a PCI card with unique subvendor/dev identifiers which can be blacklisted, or a motherboard with DMI entries that can be used. If it's just some poorly engineered 'shove a cable in one end and a CF card the other' device which is therefore not directly detectable I think you lose. Alan - : 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
