mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "James Ausmus" <james.ausmus@gmail.com>
To: "Robert Hancock" <hancockr@shaw.ca>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] ide: Allow disabling of UDMA for Compact Flash devices
Date: Wed, 19 Apr 2006 08:35:22 -0700	[thread overview]
Message-ID: <b79f23070604190835ibf52c99u9194a4d0078b33d0@mail.gmail.com> (raw)
In-Reply-To: <4445A3F3.6050907@shaw.ca>

On 4/18/06, Robert Hancock <hancockr@shaw.ca> wrote:
> James Ausmus wrote:
> > This is exactly the situation that I have with 2 separate "dumb" (just
> > physical interfaces, essentially - not at all detectable) IDE->CF
> > adapters - both the IDE controller and the CF media support several
> > UDMA modes, so the IDE driver throws the CF device into UDMA mode on
> > bootup. However, as the physical interface between the IDE cable and
> > the CF socket is poorly engineered, it cannot handle the higher
> > speeds, causing the timeout errors. For some people, this can just be
> > fixed with an ide=nodma boot option, but as I also have a (quite
> > large) rotating media device on the controller, this is not an option,
> > as, if a fsck is performed on a boot, the boot-up time is upwards of
> > 30 minutes.
>
> If it's like some of the CF-IDE adapters I've seen, the DMA request/ack
> lines likely aren't even wired up between the card and the cable.
> There's no way the kernel can detect that DMA is not actually possible
> on such a card without trying and waiting for it to timeout. (I've seen
> a few which have jumpers which select whether to connect these or not -
> haven't a clue why you wouldn't want to hook those up unconditionally..)
>
> Isn't there an option to disable DMA for a specific IDE channel
> (ide2=nodma or something like that)?
>

Yes, there is, but that unfortunately does not solve the issue for
configurations where there is also a UDMA capable device on the same
channel. If there was something like ide2=0:nodma,1:dma or some such,
in order to enable/disable dma on a per device basis, instead of a
per-channel basis, then that would also solve the issue.

-James


> --
> Robert Hancock      Saskatoon, SK, Canada
> To email, remove "nospam" from hancockr@nospamshaw.ca
> Home Page: http://www.roberthancock.com/
>
>

  reply	other threads:[~2006-04-19 15:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 [this message]
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
2006-04-18 16:32       ` 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=b79f23070604190835ibf52c99u9194a4d0078b33d0@mail.gmail.com \
    --to=james.ausmus@gmail.com \
    --cc=hancockr@shaw.ca \
    --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

all inboxes | Powered by JetHome®