From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Richard A Nelson <cowboy@cavein.org>
Cc: Jeff Garzik <jeff@garzik.org>,
torvalds@osdl.org, linux-ide@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ahci: Fix long standing Marvell regressions
Date: Wed, 3 Sep 2008 20:06:49 +0100 [thread overview]
Message-ID: <20080903200649.71eb6bfb@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <alpine.DEB.1.10.0809031151200.742@hygvzn-guhyr.pnirva.bet>
On Wed, 3 Sep 2008 11:54:36 -0700 (PDT)
Richard A Nelson <cowboy@cavein.org> wrote:
> On Wed, 3 Sep 2008, Alan Cox wrote:
>
> > We can't automate that for the other devices as we don't actually know
> > how to check the PATA port on them.
>
> I happen to have one of the others:
> Marvell Technology Group Ltd. 88SE6121 SATA II Controller (rev b1)
>
> It is not in use, likely as a result of the issues at hand, I don't
> recall exactly what transpired at the time.
>
> I have no specs, but would be happy to run any software diagnostics
> if they'd be of help
Load the pata_marvell driver and it dumps out BAR5: .... lists of values
Can you do that with a PATA device attached and with no PATA device
attached and see what changes.
next prev parent reply other threads:[~2008-09-03 19:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-02 23:05 [PATCH] ahci: Fix long standing Marvell regressions Alan Cox
2008-09-02 23:40 ` Jeff Garzik
2008-09-03 0:27 ` Alan Cox
2008-09-03 13:29 ` Alan Cox
2008-09-03 13:42 ` Jeff Garzik
2008-09-03 13:48 ` Alan Cox
2008-09-03 14:01 ` Jeff Garzik
2008-09-03 18:54 ` Richard A Nelson
2008-09-03 19:06 ` Alan Cox [this message]
2008-09-08 16:12 ` Jeff Garzik
2008-09-09 22:18 ` Chuck Ebbert
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=20080903200649.71eb6bfb@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=cowboy@cavein.org \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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).