From: Joseph Harvell <jharvell@dogpad.net>
To: Joseph Harvell <jharvell@dogpad.net>
Cc: linux-ide@vger.kernel.org
Subject: Re: corruption problem with 2.6.10 patch for Promise SATAII TX4
Date: Fri, 11 Mar 2005 08:04:27 -0600 [thread overview]
Message-ID: <4231A56B.6040100@dogpad.net> (raw)
In-Reply-To: <422DBD7F.9030500@dogpad.net>
Jeff:
Is your contribution to 2.6.11 based on Georg's patch? If so, I think
there needs to be a warning in the promise_sata kernel config help at
the very least.
Have you considered porting the Promise driver to 2.6? I have been
using that driver with 2.4.28 with no problems. Plus, it looks like
they have support for native command queueing in the driver. However, I
noticed what appears to be a significant amount of work being done in
the interrupt handler.
---
Joe Harvell
next prev parent reply other threads:[~2005-03-11 14:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-08 14:58 corruption problem with 2.6.10 patch for Promise SATAII TX4 Joseph Harvell
2005-03-11 14:04 ` Joseph Harvell [this message]
2005-03-14 14:52 ` Joseph Harvell
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=4231A56B.6040100@dogpad.net \
--to=jharvell@dogpad.net \
--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 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).