From: Jeff Garzik <jgarzik@pobox.com>
To: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Cc: Go Taniguchi <go@turbolinux.co.jp>,
linux-ide@vger.kernel.org, "Nakajima,
Jun" <jun.nakajima@intel.com>
Subject: Re: piix dma setup code
Date: Wed, 19 May 2004 19:19:19 -0400 [thread overview]
Message-ID: <40ABEB77.4090109@pobox.com> (raw)
In-Reply-To: <200405200059.19575.bzolnier@elka.pw.edu.pl>
Bartlomiej Zolnierkiewicz wrote:
> On Thursday 20 of May 2004 00:31, Jeff Garzik wrote:
>
>>(added Jun to CC)
>>
>>Bartlomiej Zolnierkiewicz wrote:
>>
>>>On Tuesday 18 of May 2004 13:19, Go Taniguchi wrote:
>>>
>>>>If speed is XFER_UDMA_6, base clock is set to low base clock.
>>>>It should be "speed >= XFER_UDMA_5". My ICH6 system reported XFER_UDMA_6,
>>>
>>>Jeff, does ICH6 support UDMA6?
>>>ICH5 doesn't but ata_piix.c allows it.
>>
>>Good question. AFAICS ICH5 and ICH6 are the same such that:
>>* PATA does not support UDMA6
>>* internal base clock is 133Mhz for UDMA5
>
>
> strange, it is 100MHz according to the datasheet
Grab the latest ICH5 docs from developer.intel.com, they say the same
thing as the ICH6 docs. Section 5.16.6, "Ultra ATA/33/66/100 Timing":
> The internal Base Clock for Ultra ATA/100 (Mode 5) runs at 133 MHz, and
> the Cycle Time (CT) must be set for three Base Clocks. The ICH5 thus
> toggles the write strobe signal every 22.5 ns, transferring two bytes of
>>* SATA PCI device exports, but completely ignores, PATA timing registers
>>
>>So for ata_piix at least, I would prefer to do
>>* patch1: your patch, based on Go's patch
>>* patch2: only configure timing registers for PATA port (PATA is only
>>used when an #ifdef is defined)
>>* patch3: do not limit SATA to udma5
>
>
> OK
>
> this reminds me that long time ago I spotted small bug in configuring PATA
> timing registers in ata_piix.c but was too lazy to send a patch because code
> is #ifdef-ed and bug was (is?) only for slave device 8)
Patches welcome :) Slave device is a possibility on ICH6, which maps 4
SATA ports onto IDE primary/secondary master/slave, when not in evil
combined mode.
If you are motivated, I need to re-copy the drivers/ide/pci/piix.c
tune_chipset function to ata_piix.c, because I need to add MWDMA support
back to that function.
Jeff
next prev parent reply other threads:[~2004-05-19 23:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-18 11:19 piix dma setup code Go Taniguchi
2004-05-19 1:34 ` Jeff Garzik
2004-05-19 16:51 ` Bartlomiej Zolnierkiewicz
2004-05-19 22:31 ` Jeff Garzik
2004-05-19 22:59 ` Bartlomiej Zolnierkiewicz
2004-05-19 23:19 ` Jeff Garzik [this message]
2004-05-20 0:10 ` 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=40ABEB77.4090109@pobox.com \
--to=jgarzik@pobox.com \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=go@turbolinux.co.jp \
--cc=jun.nakajima@intel.com \
--cc=linux-ide@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.