linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andre Hedrick <andre@linux-ide.org>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: Meelis Roos <mroos@tartu.cyber.ee>, linux-kernel@vger.kernel.org
Subject: Re: Hangs in 2.4.19 and 2.4.20-pre5 (IDE-related?)
Date: Thu, 29 Aug 2002 20:04:58 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.10.10208292003080.24156-100000@master.linux-ide.org> (raw)
In-Reply-To: <20020829224621.A4175@ucw.cz>


Good cause then I take responsiblity for it.

On Thu, 29 Aug 2002, Vojtech Pavlik wrote:

> On Thu, Aug 29, 2002 at 12:37:19PM -0700, Andre Hedrick wrote:
> 
> > On Thu, 29 Aug 2002, Meelis Roos wrote:
> > 
> > > pcibus = 33333
> > > 00:07.1 vendor=8086 device=7111 class=0101 irq=0 base4=f001
> > > ----------PIIX BusMastering IDE Configuration---------------
> > > Driver Version:                     1.3
> > > South Bridge:                       28945
> > > Revision:                           IDE 0x1
> > > Highest DMA rate:                   UDMA33
> > > BM-DMA base:                        0xf000
> > > PCI clock:                          33.3MHz
> > > -----------------------Primary IDE-------Secondary IDE------
> > > Enabled:                      yes                 yes
> > > Simplex only:                  no                  no
> > > Cable Type:                   40w                 40w
> > > -------------------drive0----drive1----drive2----drive3-----
> > > Prefetch+Post:        yes       yes       yes       yes
> > > Transfer Mode:        PIO       PIO       PIO       PIO
> > > Address Setup:       90ns      90ns      90ns      90ns
> > > Cmd Active:         360ns     360ns     360ns     360ns
> > > Cmd Recovery:       540ns     540ns     540ns     540ns
> > > Data Active:         90ns      90ns      90ns      90ns
> > > Data Recovery:       30ns      30ns      90ns      30ns
> > > Cycle Time:         120ns     120ns     180ns     120ns
> > > Transfer Rate:   16.6MB/s  16.6MB/s  11.1MB/s  16.6MB/s
> > 
> > That is not my work and you are on your own for that mess.
> > That looks straight out of 2.5.30.
> 
> Don't be so quick with shooing people away - this is the output of the
> 'atapci' userspace program. It only reads the PCI config registers and

Well if atapci is that complete then I see no reason to keep proc about.
So if it needs to go we delete it.

Regards,

Andre Hedrick
LAD Storage Consulting Group


  reply	other threads:[~2002-08-30  3:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-29 18:26 Hangs in 2.4.19 and 2.4.20-pre5 (IDE-related?) Meelis Roos
2002-08-29 19:37 ` Andre Hedrick
2002-08-29 20:18   ` Meelis Roos
2002-08-29 20:46   ` Vojtech Pavlik
2002-08-30  3:04     ` Andre Hedrick [this message]
2002-08-30  5:51       ` Vojtech Pavlik
2002-08-30  6:31         ` Andre Hedrick
2002-08-30  6:51           ` Vojtech Pavlik
2002-08-30 14:34 ` Meelis Roos
2002-09-26 20:37 Joao S Veiga
2002-10-06 14:08 Jan-Hinnerk Reichert
2002-10-06 16:25 ` Alan Cox
2002-10-06 19:56   ` Jan-Hinnerk Reichert
2002-10-06 21:38     ` Alan Cox

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=Pine.LNX.4.10.10208292003080.24156-100000@master.linux-ide.org \
    --to=andre@linux-ide.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mroos@tartu.cyber.ee \
    --cc=vojtech@suse.cz \
    /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;
as well as URLs for NNTP newsgroup(s).