All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Daniela Engert <dani@ngrt.de>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.4.2ac12 (vt82c686 info)
Date: Fri, 9 Mar 2001 08:53:03 +0100	[thread overview]
Message-ID: <20010309085303.A690@suse.cz> (raw)
In-Reply-To: <20010308195107.A8509@suse.cz> <20010309072110.DB1C73E75@mail.medav.de>
In-Reply-To: <20010309072110.DB1C73E75@mail.medav.de>; from dani@ngrt.de on Fri, Mar 09, 2001 at 08:25:43AM +0100

On Fri, Mar 09, 2001 at 08:25:43AM +0100, Daniela Engert wrote:

> >They're about the same - only Alan didn't like the PCI speed measurement
> >code that's new in the 4.x series, so I added all the other changes to
> >the 3.20 driver, and 3.21 was born.
> 
> I do understand Alan's objections against this speed measurement code
> very well. I have similar code built into other (non-Linux) drivers,
> and according to the many user reports that I got the measurement
> results should be taken with a grain of salt. It is working perfectly
> in most cases, but it may fail from time to time. There is a hidden
> assumption in this type of measurement which the device that you run
> the test against has to fulfill. If it doesn't (and it is not required
> to do to be conforming to the ATA spec), the measurement results (PCI
> bus clock) are bogus (typically way too high).

Actually I don't think my method can ever result in a measurement higher
than real PCI clock, but can result in a lower one (if the device
deasserts IORDY even on a speed slower than PIO_0), which is also a
problem. Anyway, on fast machines the accuracy of the current algorithm
is +- .01 MHz.

Once tested a little more, the measurement will probably go in, however
with an option for the user to override it with a command line
parameter.

Btw, if it isn't a secret - what other drivers are those and what is the
exact method you used ... ?

-- 
Vojtech Pavlik
SuSE Labs

  reply	other threads:[~2001-03-09  7:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-06 13:05 Linux 2.4.2ac12 (vt82c686 info) George Garvey
2001-03-07 19:14 ` Vojtech Pavlik
2001-03-07 13:23   ` John Heil
2001-03-08  8:17     ` Vojtech Pavlik
2001-03-08 17:30       ` Wayne Whitney
2001-03-08 18:51         ` Vojtech Pavlik
2001-03-09  7:25           ` Daniela Engert
2001-03-09  7:53             ` Vojtech Pavlik [this message]
2001-03-12 19:33               ` Andre Hedrick
2001-03-08 18:35       ` Harold Oga
2001-03-08 20:54         ` Vojtech Pavlik
2001-03-09 13:10           ` Harold Oga
2001-03-09 15:25             ` Harold Oga
2001-03-08  5:47   ` Rogerio Brito

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=20010309085303.A690@suse.cz \
    --to=vojtech@suse.cz \
    --cc=dani@ngrt.de \
    --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 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.