From: echo6 <echo6_uk@yahoo.com>
To: Bob Stewart <bob@evoria.net>
Cc: Tejun Heo <tj@kernel.org>, linux-ide@vger.kernel.org
Subject: Re: sata_inic162x LED enable request
Date: Thu, 04 Sep 2008 19:14:37 +0100 [thread overview]
Message-ID: <48C0258D.8040002@yahoo.com> (raw)
In-Reply-To: <695462.9268.qm@web904.biz.mail.mud.yahoo.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Bob,
It is a possibility, I guess I need to rape my laptop and replace a
drive with Windows on it to test just to be sure it isn't hardware.
Although I think you may be right, the card is duff.
Jon.
Bob Stewart wrote:
> Jon,
>
> Are you aware that I had a card that "almost" worked, but
> would fail with timeouts under any sort of load?
>
>
> --- echo6 <echo6_uk@yahoo.com> wrote:
>
> Hmmm, thanks Bob, I guess I need to consider what else may be causing
> my system to hang with my setup.
>
> Jon.
>
> Bob Stewart wrote:
>>>> Tejun,
>>>>
>>>> I've been using the new driver to boot my second machine for about 2 weeks,
>>>> now, as well as having another 200GB disk hanging off it; all without any
>>>> problems. Well done! What I would like to see is the LED enabled
> properly,
>>>> although the board uses a different header pin for each drive. Anyway, if
> I've
>>>> got it right, here is my suggested change.
>>>>
>>>> --- linux-2.6.27-rc5.a/drivers/ata/sata_inic162x.c 2008-08-28
>>>> 18:52:02.000000000 -0400
>>>> +++ linux-2.6.27-rc5.b/drivers/ata/sata_inic162x.c 2008-09-01
>>>> 14:05:24.000000000 -0400
>>>> @@ -96,6 +96,7 @@
>>>> PORT_SCR = 0x20,
>>>>
>>>> /* HOST_CTL bits */
>>>> + HCTL_LEDEN = (1 << 3), /* enable LED operation */
>>>> HCTL_IRQOFF = (1 << 8), /* global IRQ off */
>>>> HCTL_FTHD0 = (1 << 10), /* fifo threshold 0 */
>>>> HCTL_FTHD1 = (1 << 11), /* fifo threshold 1*/
>>>> @@ -540,7 +541,7 @@
>>>> void __iomem *port_base = inic_port_base(ap);
>>>>
>>>> /* fire up the ADMA engine */
>>>> - writew(HCTL_FTHD0, port_base + HOST_CTL);
>>>> + writew(HCTL_FTHD0 + HCTL_LEDEN, port_base + HOST_CTL);
>>>> writew(IDMA_CTL_GO, port_base + PORT_IDMA_CTL);
>>>> writeb(0, port_base + PORT_CPB_PTQFIFO);
>>>>
>>
>>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFIwCWMbSv1saVS9ucRAoU6AKCGktFr4jCOa8VnYCBvrgFlq/NzDgCfcP4L
hLhvfiqFGDNq9v7XBEI2SYY=
=yTsD
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2008-09-04 18:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-21 16:58 sata_inic162x echo6
2008-08-21 16:52 ` sata_inic162x Alan Cox
2008-08-21 18:00 ` sata_inic162x echo6
2008-08-30 10:29 ` sata_inic162x Tejun Heo
2008-09-04 0:35 ` sata_inic162x LED enable request Bob Stewart
2008-09-04 7:27 ` echo6
2008-09-04 15:54 ` Bob Stewart
2008-09-04 18:14 ` echo6 [this message]
2008-09-04 8:13 ` Tejun Heo
2008-09-04 15:52 ` Bob Stewart
2008-09-08 12:12 ` Tejun Heo
2008-09-08 15:13 ` Bob Stewart
2008-09-08 19:09 ` Tejun Heo
2008-09-08 20:24 ` Bob Stewart
2008-09-09 7:53 ` Tejun Heo
2008-09-09 19:41 ` Bob Stewart
2008-09-11 9:50 ` [PATCH #upstream-fixes] sata_inic162x: enable LED blinking Tejun Heo
2008-09-13 20:43 ` Jeff Garzik
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=48C0258D.8040002@yahoo.com \
--to=echo6_uk@yahoo.com \
--cc=bob@evoria.net \
--cc=linux-ide@vger.kernel.org \
--cc=tj@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).