From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Marko Koivusalo <marko.koivusalo@gmail.com>
Cc: jgarzik@pobox.com, linux-ide@vger.kernel.org
Subject: Re: Promise TX4 performance problems
Date: Sat, 12 Apr 2008 16:26:28 +0100 [thread overview]
Message-ID: <20080412162628.334d66f1@core> (raw)
In-Reply-To: <cdcaea5a0804120556w6ef4479fi86c05a4613b12a97@mail.gmail.com>
> replacement card (HPT rr174x) that has binary-wrapper drivers only
> (sigh) and I'm unable to compile them in 2.6.24.4.
Isn't the 174x just a marvell with different PCI identifiers ?
The dmesg output and hdparm -t values for that controller/device would be
useful just as a guide to low level behaviour
next prev parent reply other threads:[~2008-04-12 15:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-12 12:56 Promise TX4 performance problems Marko Koivusalo
2008-04-12 15:26 ` Alan Cox [this message]
2008-04-12 20:50 ` Marko Koivusalo
2008-04-12 21:56 ` Mikael Pettersson
2008-04-12 23:20 ` Marko Koivusalo
2008-04-12 17:47 ` Mikael Pettersson
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=20080412162628.334d66f1@core \
--to=alan@lxorguk.ukuu.org.uk \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=marko.koivusalo@gmail.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).