From: Vojtech Pavlik <vojtech@suse.cz>
To: Petr Vandrovec <VANDROVE@vc.cvut.cz>
Cc: linux-kernel@vger.kernel.org, gandalf@winds.org
Subject: Re: [preview] VIA IDE 4.0 and AMD IDE 2.0 with automatic PC
Date: Fri, 9 Feb 2001 17:36:00 +0100 [thread overview]
Message-ID: <20010209173600.A2887@suse.cz> (raw)
In-Reply-To: <1500B3C52526@vcnet.vc.cvut.cz>
In-Reply-To: <1500B3C52526@vcnet.vc.cvut.cz>; from VANDROVE@vc.cvut.cz on Fri, Feb 09, 2001 at 05:29:52PM +0000
On Fri, Feb 09, 2001 at 05:29:52PM +0000, Petr Vandrovec wrote:
> > Unfortunately the PCI speed measuring code needs help from the chipset
> > itself, so it isn't possible to implement in generic code. Maybe a
> > callback could be added to the chipset-specific drivers, though ...
> >
> > I do have some plans with ide-pci.c, so ...
>
> Is not PCI speed determined by host-bridge setting (and not by IDE
> interface)?
I found no way of measuring the PCI speed than by doing an IDE PIO
transfer unfortunately. Measuring all other PCI transactions gives bad
results, because it is dependent on waitstates and other variables.
> In that case we should determine bus speed on PCI bus scan
> using chipset specific drivers. Other non IDE devices, such as matroxfb,
> may be interested in PCI speed too.
Not the case, sorry. An IDE drive is needed. However, it still might be
worth to pass the PCI speed to other drivers ...
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-02-09 16:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-09 17:29 [preview] VIA IDE 4.0 and AMD IDE 2.0 with automatic PC Petr Vandrovec
2001-02-09 16:36 ` Vojtech Pavlik [this message]
2001-02-10 13:30 ` Martin Mares
2001-02-10 14:21 ` Jonathan Morton
2001-02-10 6:06 ` Andre Hedrick
2001-02-10 9:03 ` Vojtech Pavlik
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=20010209173600.A2887@suse.cz \
--to=vojtech@suse.cz \
--cc=VANDROVE@vc.cvut.cz \
--cc=gandalf@winds.org \
--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