From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Alan <alan@lxorguk.ukuu.org.uk>
Cc: Tejun Heo <htejun@gmail.com>, Jeff Garzik <jgarzik@pobox.com>,
linux-ide@vger.kernel.org
Subject: Re: [PATCH] libata: share PIO limits among devices sharing a channel
Date: Thu, 25 Jan 2007 17:54:57 +0300 [thread overview]
Message-ID: <45B8C4C1.4010402@ru.mvista.com> (raw)
In-Reply-To: <20070125145125.698d3a08@localhost.localdomain>
Hello.
Alan wrote:
>> Not really, at least not all drivers. Namely, hpt366.c (still) doesn't
>>merge 8-bit timings (maybe this is handled in hardware but the datasheets
>>don't tell about it then) -- I need to look at fixing this... Well, it was
> I've never been able to find out - but HPT's own drivers don't seem to do
> it under any OS so I assume its ok.
From their drivers/BIOSes/chips I can only assume their engeneers' serious
brain damage and incompetence. :-)
Well, Linux driver was hardly better.
> The timing stuff should be pretty
> much the same for both ide and libata as libata lifted most of the rather
> nice ide-timing stuff directly from the old IDE layer.
Yeah, pata_hpt3*.c still have the same issues as the old hpt366 driver,
namely changing PIO timings when setting DMA modes.
> Alan
WBR, Sergei
prev parent reply other threads:[~2007-01-25 14:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-25 11:29 [PATCH] libata: share PIO limits among devices sharing a channel Tejun Heo
2007-01-25 12:30 ` Alan
2007-01-25 12:44 ` Jeff Garzik
2007-01-25 13:30 ` Tejun Heo
2007-01-25 13:50 ` Alan
2007-01-25 14:36 ` Tejun Heo
2007-01-25 14:25 ` Sergei Shtylyov
2007-01-25 14:51 ` Alan
2007-01-25 14:54 ` Sergei Shtylyov [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=45B8C4C1.4010402@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=htejun@gmail.com \
--cc=jgarzik@pobox.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.