public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Martin Dalecki <dalecki@evision-ventures.com>
Cc: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>,
	linux-kernel@vger.kernel.org
Subject: Re: FUD or FACTS ?? but a new FLAME!
Date: Mon, 3 Jun 2002 11:19:10 +0200	[thread overview]
Message-ID: <20020603111910.A13204@ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.10.10206021451310.5846-100000@master.linux-ide.org> <3CFB0063.3070309@evision-ventures.com>

On Mon, Jun 03, 2002 at 07:36:35AM +0200, Martin Dalecki wrote:

> I have been reading the stuff about the difference between ATA/100 and
> ATA/133 talking about clock cycles, buffer sizes, transmission directions
> and what not and were quite unable to understand what the point was until I
> looked at the public Intel ICH4 spec (the one available to us mortals
> without connections :-)
> 
> ftp://download.intel.com/design/chipsets/manuals/29860002.pdf

Thanks for the pointer, I was unable to find it when I was assing ICH4
support - and most board-maker sites at that time advertised ATA-133.

> Intel do state that the ICH4/82801DB supports only ATA/100 not ATA/133.
> Looking through some reviews on the net on the 845E/G they do say the same
> thing.

Actually, it doesn't support ATA-100 correctly either. It has a 133MHz
base clock, and for ATA-100 uses a 3 clock cycle. 133MHz/3*2byte = 88.6 MB/sec.

So the maximum documented speed on ICH chips is 88.6 write, and 100.0
read - because there the drive dictates the speed.

> In the light of that perhaps the code in drivers/ide/piix.c stating that the
> ICH4 does ATA/133 is a bit optimistic and should be moved to the "try it if
> you want to " CONFIG_BLK_DEV_PIIX_TRY133 option.

Agreed. Martin, please do that. Also, please change the Config.in
comment to something like "Enable undocumented ATA-133 on ICH chips",
or somehting alike..

> Of course Vojtek might have better info that says otherwise.

No, I don't. ICH4 was designed to have ATA-133 capability, Intel
probably downgraded that in the spec because of some problems.

-- 
Vojtech Pavlik
SuSE Labs

  reply	other threads:[~2002-06-03  9:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-02  1:58 INTEL 845G Chipset IDE Quandry Bartlomiej Zolnierkiewicz
2002-06-02  5:30 ` FUD or FACTS ?? but a new FLAME! Andre Hedrick
2002-06-02 12:11   ` Bartlomiej Zolnierkiewicz
2002-06-02 14:29     ` Alan Cox
2002-06-02 14:25       ` Bartlomiej Zolnierkiewicz
2002-06-02 16:00         ` Alan Cox
2002-06-02 21:14     ` Andre Hedrick
2002-06-02 21:50       ` Bartlomiej Zolnierkiewicz
2002-06-02 21:55         ` Andre Hedrick
2002-06-03  5:36           ` Martin Dalecki
2002-06-03  9:19             ` Vojtech Pavlik [this message]
2002-06-03 13:01             ` Bartlomiej Zolnierkiewicz
2002-06-03 12:10               ` Martin Dalecki
2002-06-02  6:01 ` INTEL 845G Chipset IDE Quandry Martin Dalecki
2002-06-03  8:59   ` Andre Hedrick
  -- strict thread matches above, loose matches on Subject: below --
2002-06-02 22:25 FUD or FACTS ?? but a new FLAME! Bartlomiej Zolnierkiewicz

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=20020603111910.A13204@ucw.cz \
    --to=vojtech@suse.cz \
    --cc=B.Zolnierkiewicz@elka.pw.edu.pl \
    --cc=dalecki@evision-ventures.com \
    --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