From: Vojtech Pavlik <vojtech@suse.cz>
To: Andre Hedrick <andre@linux-ide.org>
Cc: Vojtech Pavlik <vojtech@suse.cz>,
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: Fri, 30 Aug 2002 07:51:47 +0200 [thread overview]
Message-ID: <20020830075147.D18904@ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.10.10208292003080.24156-100000@master.linux-ide.org>; from andre@linux-ide.org on Thu, Aug 29, 2002 at 08:04:58PM -0700
On Thu, Aug 29, 2002 at 08:04:58PM -0700, Andre Hedrick wrote:
>
> 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.
I think you can drop the chipset specific /proc code. It'll simplify the
drivers a lot as well as making them smaller.
On the other hand, I'd suggest that some generic /proc code is put in
place instead of the chipset-specific one - the values that cannot be
read from PCI config registers, like:
The PIO/MMIO/(U)DMA mode (and transfer rate) the IDE driver is operating
the in. The bus speed the driver thinks is running at. Whether the IDE
driver has detected a 80 or 40 wire cable. Etc, etc. This would be very
useful, can be done by a single common routine, and most users actually
don't need the exact timings.
--
Vojtech Pavlik
SuSE Labs
next prev parent reply other threads:[~2002-08-30 5:47 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
2002-08-30 5:51 ` Vojtech Pavlik [this message]
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=20020830075147.D18904@ucw.cz \
--to=vojtech@suse.cz \
--cc=andre@linux-ide.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mroos@tartu.cyber.ee \
/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).