From: Albert Lee <albertcc@tw.ibm.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: albertl@mail.com, Sergei Shtylyov <sshtylyov@ru.mvista.com>,
Bahadir Balban <bahadir.balban@gmail.com>,
linux-ide@vger.kernel.org, Mikael Pettersson <mikpe@it.uu.se>
Subject: Re: ide/dma not working from 2.6.19 to 2.6.21
Date: Tue, 26 Jun 2007 13:05:43 +0800 [thread overview]
Message-ID: <46809EA7.5090005@tw.ibm.com> (raw)
In-Reply-To: <20070625101009.48269d6e@the-village.bc.nu>
Alan Cox wrote:
>>Reloading the pata_pdc2027x module then the problem goes away.
>>I guess maybe somehow mdelay() is not as precise as before...
>
>
> It's not the most accurate of things once power management and the like
> get invovled. HT doesn't help it either. You should have get much more
> accurate timing information if you query gettimeofday before/after and do
> a few loops.
>
Thanks for the advice. Patch to follow.
--
albert
next prev parent reply other threads:[~2007-06-26 5:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-21 11:47 ide/dma not working from 2.6.19 to 2.6.21 Bahadir Balban
2007-06-21 15:28 ` Sergei Shtylyov
2007-06-21 18:17 ` Sergei Shtylyov
2007-06-25 5:22 ` Albert Lee
2007-06-25 9:10 ` Alan Cox
2007-06-26 5:05 ` Albert Lee [this message]
2007-06-26 5:43 ` [PATCH 1/1] libata: pata_pdc2027x PLL input clock fix Albert Lee
2007-07-02 14:14 ` Jeff Garzik
2007-07-02 18:13 ` Bartlomiej Zolnierkiewicz
2007-07-02 18:00 ` Sergei Shtylyov
2007-07-03 5:21 ` [PATCH 1/1] ide: pdc202xx_new " Albert Lee
2007-07-03 14:24 ` Sergei Shtylyov
2007-07-03 18:59 ` Bartlomiej Zolnierkiewicz
2007-07-03 20:36 ` Sergei Shtylyov
2007-07-04 8:20 ` Albert Lee
2007-07-03 18:57 ` Bartlomiej Zolnierkiewicz
2007-07-20 14:38 ` Bahadir Balban
-- strict thread matches above, loose matches on Subject: below --
2007-06-21 15:29 ide/dma not working from 2.6.19 to 2.6.21 Mikael Pettersson
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=46809EA7.5090005@tw.ibm.com \
--to=albertcc@tw.ibm.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=albertl@mail.com \
--cc=bahadir.balban@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=mikpe@it.uu.se \
--cc=sshtylyov@ru.mvista.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.