mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
To: Allen Martin <AMartin@nvidia.com>, Vojtech Pavlik <vojtech@suse.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH][IDE] small cleanup for AMD/nVidia IDE driver
Date: Fri, 3 Oct 2003 22:35:14 +0200	[thread overview]
Message-ID: <200310032235.14733.bzolnier@elka.pw.edu.pl> (raw)
In-Reply-To: <DCB9B7AA2CAB7F418919D7B59EE45BAF49F704@mail-sc-6.nvidia.com>

On Friday 03 of October 2003 21:51, Allen Martin wrote:
> > I've seen 2.4.x patches from Allen Martin@nVidia on lkml.
> > In UDMA133 patch he mentioned that UDMA should be programmed by mode,
> > not UDMA cycle timing on nVidia chipsets (probably the same
> > applies to AMD).
> > Can you comment on this?
>
> Yes, these controllers have a 1:1 mapping between UDMA mode and
> AMD_UDMA_TIMING value.  Trying to map UDMA mode to cycle time and then map
> back to UDMA mode is error prone, and cause for some of the ugly
> workarounds in the current driver.  My patch to add Ultra133 support just
> expands this ugliness, but works.
>
> The mapping is as follows:
>
> UDMA2 0
> UDMA1 1
> UDMA0 2
> UDMA3 4
> UDMA4 5
> UDMA5 6
> UDMA6 7

Thanks for explaining this.
Vojtech please consider it in your future patches. ;-)

> Other ACPI aware OS'es use an ACPI method to change IDE timing, so this is
> hidden from the OS.

Damn, I must take a look at ACPI specification 8-).

--bartlomiej


  reply	other threads:[~2003-10-03 20:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-03 19:51 Allen Martin
2003-10-03 20:35 ` Bartlomiej Zolnierkiewicz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-10-03 18:34 Bartlomiej Zolnierkiewicz
2003-10-03 19:04 ` Vojtech Pavlik
2003-10-03 19:36   ` Bartlomiej Zolnierkiewicz

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=200310032235.14733.bzolnier@elka.pw.edu.pl \
    --to=b.zolnierkiewicz@elka.pw.edu.pl \
    --cc=AMartin@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vojtech@suse.cz \
    /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®