From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] SCSI initialisation
Date: Tue, 29 Apr 2003 12:07:48 +0200 [thread overview]
Message-ID: <20030429120747.E26796@cackle.proxima.alt.za> (raw)
In-Reply-To: <HOEHIDJJJINMLFPOLFJCIENMCOAA.nigel@9fs.org>; from Nigel Roles on Tue, Apr 29, 2003 at 10:59:00AM +0100
On Tue, Apr 29, 2003 at 10:59:00AM +0100, Nigel Roles wrote:
>
> > r->sense[12] == 0x04 && r->sense[13] == 0x01
> >
> > and I have no idea what to make of it :-(
>
> It means that the device is "in the process of becoming ready".
>
> I expect you can figure out how to handle that.
I gambled on
if (r->sense[12] == 0x04){
status = SDcheck;
if(r->sense[13] == 0x01)
status = SDok;
break;
}
...
return (status == SDok || status == SDcheck);
which seems to have worked. I guess I ought to take the more patient
approach of actually waiting for r->sense[13] == 0? Or are the sense
values meant to be something else altogether?
++L
prev parent reply other threads:[~2003-04-29 10:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-29 9:15 Lucio De Re
2003-04-29 9:59 ` Nigel Roles
2003-04-29 10:07 ` Lucio De Re [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=20030429120747.E26796@cackle.proxima.alt.za \
--to=lucio@proxima.alt.za \
--cc=9fans@cse.psu.edu \
/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).