From: Alan <alan@lxorguk.ukuu.org.uk>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: jgarzik@pobox.com, linux-ide@vger.kernel.org
Subject: Re: [PATCH] (2.6.20) pata_mpiix: fix PIO setup issues
Date: Mon, 5 Feb 2007 19:00:36 +0000 [thread overview]
Message-ID: <20070205190036.68388b4c@localhost.localdomain> (raw)
In-Reply-To: <200702052024.57511.sshtylyov@ru.mvista.com>
On Mon, 5 Feb 2007 20:24:57 +0300
Sergei Shtylyov <sshtylyov@ru.mvista.com> wrote:
> Fix clearing/setting the wrong TIME/IE/PPE bits for a slave drive caused by a
> wrong shift count.
> Fix the PIO mode 1 being overclocked by wrongly selecting the fast timing bank.
> Also, fix/rephrase some comments while at it.
>
> Signed-off-by: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Thanks - I've not managed to find an MPIIX with two devices on it yet.
Acked-by: Alan Cox <alan@redhat.com>
next prev parent reply other threads:[~2007-02-05 18:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-05 17:24 [PATCH] (2.6.20) pata_mpiix: fix PIO setup issues Sergei Shtylyov
2007-02-05 19:00 ` Alan [this message]
2007-02-07 0:53 ` Jeff Garzik
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=20070205190036.68388b4c@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=sshtylyov@ru.mvista.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).