From: Martin Dalecki <dalecki@evision-ventures.com>
To: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Cc: Neil Conway <nconway_kernel@yahoo.co.uk>, linux-kernel@vger.kernel.org
Subject: Re: PATCH, IDE corruption, 2.4.18
Date: Sun, 05 May 2002 17:04:28 +0200 [thread overview]
Message-ID: <3CD549FC.4040406@evision-ventures.com> (raw)
In-Reply-To: <Pine.SOL.4.30.0205051741140.23671-100000@mion.elka.pw.edu.pl>
Uz.ytkownik Bartlomiej Zolnierkiewicz napisa?:
>>Explanation: some code now differs in the code path concerned, and
>>ide_register_subdriver now only calls ide_dma_check for UDMA drives
>>(previously all DMA drives), but ultimately ide_dma_check still ends up
>>in ide_config_drive_speed, and that's still fuctionally the same as
>>2.4.
>
>
> You've got been mistaken by unfortunate name (Martin changed
> name dmaproc() to udma() in 2.5.12).
> Code calls ide_dma_check for chipsets which registerered udma()
> handler (formerly dmaproc()), I think the same 2.4 does.
>
> btw. udma() name is really misleading,
> it should be read (u)dma() not udma() :)
It's just an intermediate step before this whole crap get's
trown over ;-).
next prev parent reply other threads:[~2002-05-05 16:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-05 15:49 PATCH, IDE corruption, 2.4.18 Bartlomiej Zolnierkiewicz
2002-05-05 15:04 ` Martin Dalecki [this message]
2002-05-05 20:44 ` Neil Conway
2002-05-06 0:23 ` Mike Fedyk
-- strict thread matches above, loose matches on Subject: below --
2002-05-04 12:15 Neil Conway
2002-05-04 22:58 ` Andre Hedrick
2002-05-05 2:10 ` Neil Conway
2002-05-05 0:22 ` Mike Fedyk
2002-05-05 0:47 ` Andre Hedrick
2002-05-05 1:54 ` Neil Conway
2002-05-05 7:36 ` Mike Fedyk
2002-05-05 9:44 ` Neil Conway
2002-05-03 20:39 Neil Conway
2002-05-03 20:36 Neil Conway
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=3CD549FC.4040406@evision-ventures.com \
--to=dalecki@evision-ventures.com \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=nconway_kernel@yahoo.co.uk \
/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