public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Andre Hedrick <andre@linux-ide.org>
Cc: Alan Chandler <alan@chandlerfamily.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: [preview] Latest AMD & VIA IDE drivers with UDMA100 support
Date: Wed, 24 Jan 2001 20:25:27 +0100	[thread overview]
Message-ID: <20010124202527.A2405@suse.cz> (raw)
In-Reply-To: <20010121104606.A398@suse.cz> <Pine.LNX.4.10.10101241003270.14153-100000@master.linux-ide.org>
In-Reply-To: <Pine.LNX.4.10.10101241003270.14153-100000@master.linux-ide.org>; from andre@linux-ide.org on Wed, Jan 24, 2001 at 10:04:50AM -0800

On Wed, Jan 24, 2001 at 10:04:50AM -0800, Andre Hedrick wrote:

> > Well, I know this. But I fear hardcoded timings won't really help here,
> > unless everyone out there ran their chipsets at 33 MHz, in which case the
> 
> You have to run the ATA Chipset at 33MHz or it will fail in 99% of all
> cases. 

No. Though I'd advise everyone to stick with 33MHz PCI when they can
because it is safe. But even the VIA specs mention 25, 37.5 and 41.5 PCI
speeds.

> This is not the FSB running at 66/83/100/133.  So hardcode is
> correct.

If you set a MVP3 or MVP4 chipset to 83 MHz FSB, you'll get 41.5 MHz
or 27.6 MHz PCI. And there are chips speced for 75 and 83 MHz FSB's -
Cyrix 6x86MX etc.

No way to get 33 here, if you *don't* want to over/under-clock the CPU. 

-- 
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/

  reply	other threads:[~2001-01-24 19:25 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-20 17:14 [preview] Latest AMD & VIA IDE drivers with UDMA100 support Alan Chandler
     [not found] ` <Pine.LNX.4.10.11101200938180.2302-100000@master.linux-ide.org>
2001-01-20 18:45   ` Alan Chandler
2001-01-20 20:56     ` Vojtech Pavlik
2001-01-20 22:57       ` Andre Hedrick
2001-01-20 23:55         ` Alan Chandler
     [not found]           ` <Pine.LNX.4.10.10101202015510.1776-100000@coffee.psychology.mcmaster.ca>
2001-01-21 10:51             ` Alan Chandler
2001-01-21 11:44               ` Vojtech Pavlik
2001-01-21  9:46         ` Vojtech Pavlik
2001-01-21 13:04           ` Jan Niehusmann
     [not found]           ` <Pine.Linu.4.10.10101211237230.2017-100000@mikeg.weiden.de>
2001-01-21 16:32             ` Vojtech Pavlik
2001-01-21 20:49               ` Andre Hedrick
2001-01-22  0:12                 ` Dan Hopper
2001-01-22  6:06                 ` Mike Galbraith
2001-01-25 21:54                 ` David D.W. Downey
2001-01-25 21:56                   ` Vojtech Pavlik
2001-01-25 22:00                   ` Andre Hedrick
2001-01-26  0:26                     ` David D.W. Downey
2001-01-24 18:04           ` Andre Hedrick
2001-01-24 19:25             ` Vojtech Pavlik [this message]
2001-01-24 21:58               ` Andre Hedrick
2001-01-25 12:20                 ` Vojtech Pavlik
  -- strict thread matches above, loose matches on Subject: below --
2001-01-19 15:56 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=20010124202527.A2405@suse.cz \
    --to=vojtech@suse.cz \
    --cc=alan@chandlerfamily.org.uk \
    --cc=andre@linux-ide.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