mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 08:51:26 +0200	[thread overview]
Message-ID: <20020830085126.A19532@ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.10.10208292329150.7329-100000@master.linux-ide.org>; from andre@linux-ide.org on Thu, Aug 29, 2002 at 11:31:39PM -0700

On Thu, Aug 29, 2002 at 11:31:39PM -0700, Andre Hedrick wrote:
> 
> Vojtech,
> 
> Ball is in your court, DO IT!
> Lets see what you got and how we can debloat the driver more.
> 
> Looking to put the past behind, will you help?

Sure.

> Cheers,
> 
> Andre Hedrick
> LAD Storage Consulting Group
> 
> 
> On Fri, 30 Aug 2002, Vojtech Pavlik wrote:
> 
> > > 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

  reply	other threads:[~2002-08-30  6:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-29 18:26 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
2002-08-30  6:31         ` Andre Hedrick
2002-08-30  6:51           ` Vojtech Pavlik [this message]
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=20020830085126.A19532@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

all inboxes | Powered by JetHome®