From: Tomas Szepe <szepe@pinerecords.com>
To: Andre Hedrick <andre@linux-ide.org>
Cc: Vojtech Pavlik <vojtech@suse.cz>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Ryan Mack <lists@mackman.net>,
Markus Plail <linux-kernel@gitteundmarkus.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.21 ServerWorks DMA Bugs
Date: Mon, 7 Jul 2003 05:42:17 +0200 [thread overview]
Message-ID: <20030707034217.GD303@louise.pinerecords.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10307061740150.29935-100000@master.linux-ide.org>
> [andre@linux-ide.org]
>
> Caution!
>
> Serverworks has OEM's who have BIOS's which are setup for a reason.
> If the BIOS is configured for any reason the the driver stomps on the BIOS
> settings there will be damage to the content on the media.
>
> Just the view from an insider in the know.
Hmm, I certainly wouldn't expect a $3500 server to come with busted
IDE, but thanks for the suggestion, we'll take extra care.
--
Tomas Szepe <szepe@pinerecords.com>
next prev parent reply other threads:[~2003-07-07 3:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-05 6:45 2.4.21 ServerWorks DMA Bugs Ryan Mack
2003-07-05 6:49 ` Andre Hedrick
2003-07-05 7:21 ` Markus Plail
2003-07-05 16:58 ` Ryan Mack
2003-07-05 17:07 ` Jeff Garzik
2003-07-06 7:40 ` Alan Cox
2003-07-06 9:06 ` Tomas Szepe
2003-07-06 9:10 ` Alan Cox
2003-07-06 11:10 ` Tomas Szepe
2003-07-06 11:38 ` Alan Cox
2003-07-06 16:42 ` Vojtech Pavlik
2003-07-06 17:49 ` Alan Cox
2003-07-07 0:42 ` Andre Hedrick
2003-07-07 3:42 ` Tomas Szepe [this message]
2003-07-07 6:42 ` Alan Cox
2003-07-07 8:49 ` Tomas Szepe
2003-07-07 8:13 ` Andre Hedrick
2003-07-07 8:17 ` Andre Hedrick
2003-07-07 8:45 ` Tomas Szepe
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=20030707034217.GD303@louise.pinerecords.com \
--to=szepe@pinerecords.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andre@linux-ide.org \
--cc=linux-kernel@gitteundmarkus.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@mackman.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.