From: Martin Dalecki <dalecki@evision-ventures.com>
To: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: FUD or FACTS ?? but a new FLAME!
Date: Mon, 03 Jun 2002 14:10:04 +0200 [thread overview]
Message-ID: <3CFB5C9C.3080303@evision-ventures.com> (raw)
In-Reply-To: <Pine.SOL.4.30.0206031451580.17745-100000@mion.elka.pw.edu.pl>
Bartlomiej Zolnierkiewicz wrote:
>>Things would be easier if "you know who" could just say that according to
>>public specs the ICH4 does not support ATA/133 instead of all that technical
>>talk......
>>
>
>
> So, we should change it...
>
> ...and simple idea how to deal with overclocking IDE chipsets
> -> try best we can but put some nice fat warning to user that
> he will probably get screwed due to running chipset out of
> specification...
Done - expect it in the next patch.
next prev parent reply other threads:[~2002-06-03 13:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-02 1:58 INTEL 845G Chipset IDE Quandry Bartlomiej Zolnierkiewicz
2002-06-02 5:30 ` FUD or FACTS ?? but a new FLAME! Andre Hedrick
2002-06-02 12:11 ` Bartlomiej Zolnierkiewicz
2002-06-02 14:29 ` Alan Cox
2002-06-02 14:25 ` Bartlomiej Zolnierkiewicz
2002-06-02 16:00 ` Alan Cox
2002-06-02 21:14 ` Andre Hedrick
2002-06-02 21:50 ` Bartlomiej Zolnierkiewicz
2002-06-02 21:55 ` Andre Hedrick
2002-06-03 5:36 ` Martin Dalecki
2002-06-03 9:19 ` Vojtech Pavlik
2002-06-03 13:01 ` Bartlomiej Zolnierkiewicz
2002-06-03 12:10 ` Martin Dalecki [this message]
2002-06-02 6:01 ` INTEL 845G Chipset IDE Quandry Martin Dalecki
2002-06-03 8:59 ` Andre Hedrick
-- strict thread matches above, loose matches on Subject: below --
2002-06-02 22:25 FUD or FACTS ?? but a new FLAME! Bartlomiej Zolnierkiewicz
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=3CFB5C9C.3080303@evision-ventures.com \
--to=dalecki@evision-ventures.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 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.