mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Andreas Mohr <andi@rhlx01.fht-esslingen.de>
Cc: James Ausmus <james.ausmus@gmail.com>,
	Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>,
	linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: [PATCH 1/1] ide: Allow disabling of UDMA for Compact Flash devices
Date: Tue, 18 Apr 2006 12:52:33 +0100	[thread overview]
Message-ID: <1145361153.18736.36.camel@localhost.localdomain> (raw)
In-Reply-To: <20060418113439.GA11815@rhlx01.fht-esslingen.de>

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


  reply	other threads:[~2006-04-18 11:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-17 23:11 James Ausmus
2006-04-18  3:21 ` Mark Lord
2006-04-18 11:14 ` Alan Cox
2006-04-18 11:34   ` Andreas Mohr
2006-04-18 11:52     ` Alan Cox [this message]
2006-04-18 16:32       ` James Ausmus
     [not found] <62LaJ-6vK-5@gated-at.bofh.it>
     [not found] ` <62Wg0-6f8-29@gated-at.bofh.it>
     [not found]   ` <62WJ1-6Od-31@gated-at.bofh.it>
     [not found]     ` <62WSE-70D-21@gated-at.bofh.it>
     [not found]       ` <631pe-5Gt-7@gated-at.bofh.it>
2006-04-19  2:44         ` Robert Hancock
2006-04-19 15:35           ` James Ausmus

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1145361153.18736.36.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=B.Zolnierkiewicz@elka.pw.edu.pl \
    --cc=andi@rhlx01.fht-esslingen.de \
    --cc=james.ausmus@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome