From: erik quanstrom <quanstro@quanstro.net>
To: cinap_lenrek@gmx.de, 9fans@9fans.net
Subject: Re: [9fans] SB600 i/o error on read/write FIXED
Date: Thu, 25 Sep 2008 17:38:53 -0400 [thread overview]
Message-ID: <7bea5af7f394b193612b1b93550d1116@quanstro.net> (raw)
> using eriks /n/sources/contrib/quanstro/sdiahci.c works.
>
> this thread is closed now ;-)
>
> sorry for the brain->9fans noise.
westerndigitalhung isn't the problem. the problem is that
the locking used by sdiahci.c originally had several races
waiting for drives to become ready. (is there any chance you
have a quirky drive?)
i submitted a patch on may 29 that i believe fixes this problem.
but you can also use the version in my contrib area, which i
updated today. the major change is that broken sata:pata
bridges that don't do udma mode 5 (required for sata) are
now supported. there's also an attempt to support a via
southbridge. but having no hardware, it's not clear that i've
got that working.
- erik
next reply other threads:[~2008-09-25 21:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-25 21:38 erik quanstrom [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-09-25 20:41 cinap_lenrek
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=7bea5af7f394b193612b1b93550d1116@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
--cc=cinap_lenrek@gmx.de \
/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).