From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ide@vger.kernel.org
Subject: [Bug 102741] pata_hpt37x driver refuses to operate with Adaptec 1200A at UDMA/100
Date: Wed, 12 Aug 2015 19:38:46 +0000 [thread overview]
Message-ID: <bug-102741-11633-FUs58pgQ6S@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-102741-11633@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=102741
--- Comment #2 from Andreas E <andi3@gmx.net> ---
NAH!!! I can't believe it. This thing can do UDMA/100 but it was limited
artificially to /66.
In any case, I think the driver messages should *inform* the user about this
being not their HDD(s) at fault, but forced to this speed by the driver itself.
Because every user would initially think that it's their fault, not the
driver's.
Is there any way I can force it to operate at UDMA/100?
Some #define, anything?
>2) UDMA/66 showed much better figures than UDMA/100 on HPT370 I was testing on.
Yes, that happened on the HPT370 *you* were testing on! But you shouldn't
project your results on everyone else's, IMHO.
I'd definitely want to test it on *my* card first, before I believe you. Sorry
'bout that. :)
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2015-08-12 19:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-12 17:11 [Bug 102741] New: pata_hpt370x driver doesn't want to operate with Adaptec 1200A at UDMA/100 bugzilla-daemon
2015-08-12 17:30 ` [Bug 102741] pata_hpt370x driver refuses " bugzilla-daemon
2015-08-12 17:56 ` [Bug 102741] pata_hpt37x " bugzilla-daemon
2015-08-12 18:41 ` bugzilla-daemon
2015-08-12 19:38 ` bugzilla-daemon [this message]
2015-08-12 20:48 ` bugzilla-daemon
2015-08-12 21:41 ` bugzilla-daemon
2015-08-14 10:48 ` bugzilla-daemon
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=bug-102741-11633-FUs58pgQ6S@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--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).