From: Martin Dalecki <dalecki@evision-ventures.com>
To: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Anthony Spinillo <tspinillo@linuxmail.org>,
linux-kernel@vger.kernel.org
Subject: Re: INTEL 845G Chipset IDE Quandry
Date: Sun, 02 Jun 2002 08:01:48 +0200 [thread overview]
Message-ID: <3CF9B4CC.7020205@evision-ventures.com> (raw)
In-Reply-To: <Pine.SOL.4.30.0206020318090.29792-100000@mion.elka.pw.edu.pl>
Bartlomiej Zolnierkiewicz wrote:
>>Alan,
>>
>>This is one of the versions of INTEL which has extra bandwidth if you
>>want
>>wanted to the async IO. Meaning the device could be set faster than the
>>host when reading from the host. However when writing to the host the
>>device "must" be set to match. The buffer is not capable of safely
>>handling the extra push.
>>
>>So in 2.4 we will properly time the host, unlike 2.5 which has elected
>>to overdrive the hardware.
>
>
> Only in piix driver (Intel & Efar) and user have to explicitly compile
> support for it, it have nothing to do with kernel version and everything
> with driver version.
>
>
>>The effect is the following. "LINUS are you listening?"
>
> ^^^^^^^^^^^^^^^^^^^^^^^^
> Andre, you forgot to cc Linus ;)
>
>
>>Ultra DMA 100 uses 4 data clocks to transfer "X" amount of data.
>>Ultra DMA 133 uses 3 data clocks to transfer "X" amount of data.
>>
>>So if a bad host trys to push the limits, it ends up missing a data
>>strobe and the DATA goes away quietly without warning. NICE!
>>
>>Maybe now people will understand why 2.5 is falling apart and it is not
>>Martin's fault. He is just getting bad information and bad patches.
>
>
> Poor Marcin, he is so misinformed by bad people trying to spoil ATA stuff.
>
> Bad patches? Who is the bad guy making the bad patches?
> Let me guess, it is Vojtech removing others people copyrighted "sick
> timing tables". Or maybe it is Jens doing at least TCQ?
> Or maybe it is me... etc.
>
>
>>He actual has nearly the same model I was working on to use fucntion
>
>
> It is really funny... but some people read code and know facts...
>
>
>>pointers in the style of "MiniPort (tm)". I will explain why this is
>>desired later.
>
>
> in Q4 I guess
Of year 2010 - remember learning proper C will take him time.
Becouse I never ever saw any code contributed by him
despite the fact that I'm still open for patches, as
I have told him upon request.
Once exception was a broken patch which even didn't
compile and couldn't solve the problem it was
proclaiming to solve.
next prev parent reply other threads:[~2002-06-02 7:01 UTC|newest]
Thread overview: 35+ 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
2002-06-02 6:01 ` Martin Dalecki [this message]
2002-06-03 8:59 ` INTEL 845G Chipset IDE Quandry Andre Hedrick
-- strict thread matches above, loose matches on Subject: below --
2002-06-03 23:35 Anthony Spinillo
2002-06-03 1:04 Anthony Spinillo
2002-06-03 9:22 ` Vojtech Pavlik
2002-06-02 10:16 Anthony Spinillo
2002-06-02 19:36 ` Martin Dalecki
2002-06-02 21:30 ` Vojtech Pavlik
2002-06-03 1:13 ` Alan Cox
2002-06-03 8:43 ` Vojtech Pavlik
2002-06-03 11:49 ` Kjartan Maraas
2002-06-03 10:10 ` Andre Hedrick
2002-06-03 4:46 ` Martin Dalecki
2002-06-03 8:47 ` Vojtech Pavlik
2002-06-03 8:04 ` Martin Dalecki
2002-06-03 9:37 ` Vojtech Pavlik
2002-06-03 9:28 ` Martin Dalecki
2002-06-01 21:43 Anthony Spinillo
2002-06-01 11:03 Anthony Spinillo
2002-06-01 12:40 ` Alan Cox
2002-06-01 20:13 ` Andre Hedrick
2002-06-01 19:53 ` Andre Hedrick
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=3CF9B4CC.7020205@evision-ventures.com \
--to=dalecki@evision-ventures.com \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=tspinillo@linuxmail.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.