linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: John Stoffel <john@stoffel.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: 2.6.21-rc6-mm1 ATA HPT37x regression
Date: Tue, 17 Apr 2007 23:37:21 +0400	[thread overview]
Message-ID: <462521F1.2000806@ru.mvista.com> (raw)
In-Reply-To: <17957.8073.587946.969040@smtp.charter.net>

Hello.

John Stoffel wrote:

>>>>Ok, so do I need to do anything special with the next -mm release and
>>>>the next version?

>>>Well, let Alan decide that (2Alan: and I said that HPT code is bogus :-).

> Alan> Try drivers/ide/pci/hpt366 - if that works grab a dmesg and let
> Alan> me know.  It means that Sergei's DPLL sync code seems to work
> Alan> better than the vendor code and its time to swap it over.

> Ok, I'll give that a whirl under 2.6.21-rc7 tonight.  I'll build them
> in modular so I can switch around more easily.  I hope.  :]

   You can't switch from the old IDE driver -- they're *not* unloadable. :-/

> Alan> Oh how I love highpoint PATA

   More like PITA. :-D

> It seemed like a good buy at the time when I was researching these
> things.  Best bang for the buck I guess.  It's a RocketRaid133 card,

   As for bang, it's true. You can't imagine how many days/nights I spent bangin' with the driver. :-D

> but obviously I got a bum deal somewhere down the line.

   HPT chips are surely not a good example of how to do things, more like an example how *not* to do. :-)

> John

MBR, Sergei

  reply	other threads:[~2007-04-17 19:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-17  2:36 2.6.21-rc6-mm1 ATA HPT37x regression John Stoffel
2007-04-17 14:08 ` Sergei Shtylyov
2007-04-17 16:30   ` John Stoffel
2007-04-17 17:06     ` Sergei Shtylyov
2007-04-17 17:13       ` Alan Cox
2007-04-17 19:27         ` John Stoffel
2007-04-17 19:37           ` Sergei Shtylyov [this message]
2007-04-17 20:03             ` Mark Lord
2007-04-19  1:34           ` John Stoffel
2007-04-19  1:49             ` John Stoffel

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=462521F1.2000806@ru.mvista.com \
    --to=sshtylyov@ru.mvista.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=john@stoffel.org \
    --cc=linux-ide@vger.kernel.org \
    --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 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).