From: Aron Rubin <arubin@atl.lmco.com>
To: Aron Rubin <aron.rubin@lmco.com>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
"Justin M. Forbes" <64bit_fedora@comcast.net>,
Andre Hedrick <andre@linux-ide.org>
Subject: Re: SII 3512+Seagate on Athlon64 system
Date: Wed, 03 Dec 2003 07:43:01 -0500 [thread overview]
Message-ID: <3FCDDA55.8000608@atl.lmco.com> (raw)
In-Reply-To: <3FCD07C4.7090205@atl.lmco.com>
Ryan Earl's patch did not fix this particular problem, so I am back to
needing help. Does slow but correct comms with an occational "hda: lost
interrupt" (about four total while talking to the drive) indicate that I
should be looking into something specific?
Aron
Aron Rubin wrote:
> SATA controller SII 3512 not recognized by driver. It looks like SII
> 3512 is almost identical to 3112 interface. I copy/paste/alterred all
> code in ide/pci/siimage.[ch] with "3112" in it to "3512". It seems about
> 95% functional. Need help with remaining 5%, related to very, very, slow
> controller comms during init with occational "Interrupt Lost" messages.
> Seems like comms are out of sync and then resync over and over. Other
> than that all drive info comes over. Ryan Earl's patch may fix, I would
> be suprised if it was that simple though. I will try later today.
>
> Aron
>
--
ssh aron@rubinium.org cat /dev/brain | grep ^work:
Aron Rubin Member, Engineering Staff
Lockheed Martin E-Mail: arubin@atl.lmco.com
Advanced Technology Laboratories Phone: 856.792.9865
3 Executive Campus Fax: 856.792.9930
Cherry Hill, NJ USA 08002 Web: http://www.atl.lmco.com
prev parent reply other threads:[~2003-12-03 12:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-02 21:44 SII 3512+Seagate on Athlon64 system Aron Rubin
2003-12-03 12:43 ` Aron Rubin [this message]
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=3FCDDA55.8000608@atl.lmco.com \
--to=arubin@atl.lmco.com \
--cc=64bit_fedora@comcast.net \
--cc=andre@linux-ide.org \
--cc=aron.rubin@lmco.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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).