From: Alan Cox <alan@redhat.com>
To: B.Zolnierkiewicz@elka.pw.edu.pl (Bartlomiej Zolnierkiewicz)
Cc: alan@redhat.com (Alan Cox), linux-kernel@vger.kernel.org
Subject: Re: [PATCH] IDE: fix "biostimings" and legacy chipsets' boot parameters
Date: Mon, 26 May 2003 20:01:48 -0400 (EDT) [thread overview]
Message-ID: <200305270001.h4R01mh24989@devserv.devel.redhat.com> (raw)
In-Reply-To: <Pine.SOL.4.30.0305262111440.7018-100000@mion.elka.pw.edu.pl> from "Bartlomiej Zolnierkiewicz" at Mai 26, 2003 09:16:36
> > > IDE: fix "biostimings" and legacy chipsets' boot parameters interaction.
> >
> > I have to admit I don't care since biostimings is a stupid patch Linus
> > forced into the tree against my wishes. Its a great way to lose all your
> > data if you turn it on
>
> You mean setting using_dma in ide_setup_dma() or comment in setup-pci.c?
> If it is data risky, why not kill it? I will be very happy - one sucky
> parameter less.
Very few BIOSes set up complete timings. The only ones that you can rely
on to handle this are those that do magic with bios tables such as
serverworks. In the serverworks case we implement the bios timing reading
per their NDA'd documents *regardless* of that setting.
Its only there because Linus applied the change despite my requests not to,
then refused to remove it. The sooner it dies the better
prev parent reply other threads:[~2003-05-26 23:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-26 14:35 [PATCH] IDE: fix "biostimings" and legacy chipsets' boot parameters interaction Bartlomiej Zolnierkiewicz
2003-05-26 18:14 ` Alan Cox
2003-05-26 19:16 ` Bartlomiej Zolnierkiewicz
2003-05-27 0:01 ` Alan Cox [this message]
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=200305270001.h4R01mh24989@devserv.devel.redhat.com \
--to=alan@redhat.com \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=linux-kernel@vger.kernel.org \
/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®