From: Andre Hedrick <andre@aslab.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Ross Boylan <RossBoylan@stanfordalumni.org>,
<sfr@canb.auug.org.au>, Andre Hedrick <andre@suse.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: IDE drive won't come back after power down
Date: Tue, 28 Aug 2001 21:29:38 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.31.0108261844570.12817-100000@postbox.aslab.com> (raw)
In-Reply-To: <E15aoRL-0008V0-00@the-village.bc.nu>
That is the prefered location; however, setting/writing up hold over code
that will be deleted in 2.5 is silly. The basics are the non-data
taskfile registers operations.
Thoughts of accepting patches early for taskfile now?
Andre Hedrick
CTO ASL, Inc.
Linux ATA Development
-----------------------------------------------------------------------------
ASL, Inc. Tel: (510) 857-0055 x103
38875 Cherry Street Fax: (510) 857-0010
Newark, CA 94560 Web: www.aslab.com
On Sun, 26 Aug 2001, Alan Cox wrote:
> > The problem is that the requirements of ACPI is to have a
>
> My PC110 does the same as Ross' machine, and like this box it has no ACPI.
> This isnt an ACPI problem on the boxes I've seen do it.
>
> > You can attempt the noisy reset additions to some versions of hdparm, and
> > then issuing the the checkpower commands until staus is reported as ready,
>
> Any reason you cant do that in kernel space, if an app can do it then
> pm thread code can do it ...
>
> Alan
>
next prev parent reply other threads:[~2001-08-29 4:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010825154508.A949@wheat.boylan.org>
2001-08-26 0:24 ` IDE drive won't come back after power down Andre Hedrick
2001-08-26 0:41 ` Ross Boylan
2001-08-26 1:10 ` Alan Cox
2001-08-29 4:29 ` Andre Hedrick [this message]
2001-08-29 14:38 ` Alan Cox
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=Pine.LNX.4.31.0108261844570.12817-100000@postbox.aslab.com \
--to=andre@aslab.com \
--cc=RossBoylan@stanfordalumni.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andre@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).