mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Christoph Anton Mitterer <cam@mathematica.scientia.net>
Cc: Andrey Melnikoff <temnota+news@kmv.ru>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Questions about the CMD640 and RZ1000 bugfix support options
Date: Thu, 06 Jan 2005 23:19:19 +0000	[thread overview]
Message-ID: <1105053558.17176.297.camel@localhost.localdomain> (raw)
In-Reply-To: <41DDC55B.2030106@mathematica.scientia.net>

On Iau, 2005-01-06 at 23:10, Christoph Anton Mitterer wrote:
> What about the following idea?
> Both stay enabled by default but the help text explains exactly (as
> far as possible) which systems are affected.
> This would help newbies like me to decide if those bugfixes are
> necessary or not.

Its the ideal solution. The diff for this is available on your computer
already - its kept in /dev/null 8)

          The PC-Technologies RZ1000 IDE chip is used on many common 486
and
          Pentium motherboards, usually along with the "Neptune"
chipset.
          Unfortunately, it has a rather nasty design flaw that can
cause
          severe data corruption under many conditions. Say Y here to
include
          code which automatically detects and corrects the problem
under
          Linux. This may slow disk throughput by a few percent, but at
least
          things will operate 100% reliably.

          The CMD-Technologies CMD640 IDE chip is used on many common
486 and
          Pentium motherboards, usually in combination with a "Neptune"
or
          "SiS" chipset. Unfortunately, it has a number of rather nasty
          design flaws that can cause severe data corruption under many
common
          conditions. Say Y here to include code which tries to
automatically
          detect and correct the problems under Linux. This option also
          enables access to the secondary IDE ports in some CMD640 based
          systems.
                                                                                
  

  reply	other threads:[~2005-01-07  0:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-31 22:26 Christoph Anton Mitterer
2004-12-31 22:41 ` Michelle Konzack
2005-01-02 14:36 ` Alan Cox
2005-01-05 18:58   ` Andrey Melnikoff
2005-01-06 16:30     ` Alan Cox
2005-01-06 22:40       ` Andrey Melnikoff
2005-01-06 23:10         ` Christoph Anton Mitterer
2005-01-06 23:19           ` Alan Cox [this message]
2005-01-07  0:47             ` Christoph Anton Mitterer
2005-01-06 23:16         ` 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=1105053558.17176.297.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=cam@mathematica.scientia.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=temnota+news@kmv.ru \
    /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

Powered by JetHome