mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: Daniela Engert <dani@ngrt.de>,
	LKML <linux-kernel@vger.kernel.org>,
	Martin Dalecki <martin@dalecki.de>,
	Shawn Starr <spstarr@sh0n.net>
Subject: Re: [patch] PIIX rewrite patch, pre-final
Date: Thu, 14 Mar 2002 09:23:22 +0100	[thread overview]
Message-ID: <20020314092322.A32260@ucw.cz> (raw)
In-Reply-To: <20020314083038.A31923@ucw.cz> <20020314063843.E0E3210921@mail.medav.de> <20020314091808.B31998@ucw.cz>
In-Reply-To: <20020314091808.B31998@ucw.cz>; from vojtech@suse.cz on Thu, Mar 14, 2002 at 09:18:08AM +0100

On Thu, Mar 14, 2002 at 09:18:08AM +0100, Vojtech Pavlik wrote:
> On Thu, Mar 14, 2002 at 08:44:42AM +0100, Daniela Engert wrote:
> 
> > The PIIX3 bug is real, I have several user reports about it!
> 
> Thanks A LOT for the tables, added are some comments from me ...
> 
> >  Vendor
> >  | Device
> >  | | Revision			       ATA	ATAPI	     ATA66  ATA133
> >  | | | south/host bridge id	     PIO  DMA  PIO  DMA  ATA33 | ATA100|   Docs
> >  | | | | south/host bridge rev.     32bit  |  32bit  |	   |   |   |   |  avail
> >  | | | | |			      |    |	|    |	   |   |   |   |    |
> >  v v v v v			      v    v	v    v	   v   v   v   v    v
> > 
> >  0x8086 Intel
> >    0x1230 PIIX		      x    x	x    x	   -   -   -   -    x
> >      < 02			      x    -	x    -	   -   -   -   -    x
> 
> I suppose this means on PIIXes with rev 00 and 01 of the IDE controller
> DMA transfers don't work reliably, right?
> 
> >        0x84C4 Orion
> > 	 < 04			      x    -	x    -	   -   -   -   -    x
> 
> And this means that if there is an 84c4 PCI bridge in the system with
> rev less than 04 (04 is OK), then DMA transfers are broken again.

And there is one more Intel chip:

0x1234, the infamous MPIIX. Can do PIO only, 32 bit is OK, has a single
channel switchable to primary or secondary, IDETIM is located in
registers 6C-6D on the ISA bridge. Docs available.

-- 
Vojtech Pavlik
SuSE Labs

  reply	other threads:[~2002-03-14  8:23 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-13 23:14 Vojtech Pavlik
2002-03-14  1:04 ` Shawn Starr
2002-03-14  6:52   ` Vojtech Pavlik
2002-03-14  7:24     ` Daniela Engert
2002-03-14  7:30       ` Vojtech Pavlik
2002-03-14  7:36         ` Andre Hedrick
2002-03-14  7:46           ` Vojtech Pavlik
2002-03-14  7:38         ` Andre Hedrick
2002-03-14  7:44         ` Daniela Engert
2002-03-14  8:18           ` Vojtech Pavlik
2002-03-14  8:23             ` Vojtech Pavlik [this message]
2002-03-14  9:48             ` Daniela Engert
2002-03-14 10:14               ` Vojtech Pavlik
2002-03-14 14:19           ` Alan Cox
2002-03-14 14:39       ` Shawn Starr
2002-03-14 16:47 ` Tom Rini
2002-03-14 16:49   ` 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=20020314092322.A32260@ucw.cz \
    --to=vojtech@suse.cz \
    --cc=dani@ngrt.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin@dalecki.de \
    --cc=spstarr@sh0n.net \
    /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

all inboxes | Powered by JetHome®