From: Andre Hedrick <andre@linux-ide.org>
To: Alex Davis <alex14641@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Possible bug and question about ide_notify_reboot in 2.4.19
Date: Sat, 14 Sep 2002 21:16:21 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.10.10209141548370.6925-100000@master.linux-ide.org> (raw)
In-Reply-To: <20020914214152.15900.qmail@web40512.mail.yahoo.com>
On Sat, 14 Sep 2002, Alex Davis wrote:
> --- Andre Hedrick <andre@linux-ide.org> wrote:
> >
> > Hi Alex,
> >
> > We (T13 Standards) only recently required (shall) all non-packet device to
> > support flush cache. No where does it state that a device supporting PM
> > for a standby (shall), the key word here is "shall", issue a flush-cache.
> I am assuming that a hard drive is a non-packet device. Let me make sure I'm
Today, yes ... In the past no.
There are a handfull of these strange beasts which still exists.
> interpreting this correctly: older ( and some current ) drives may flush cache
> on standby/sleep; current and future drives may not. In addition, older drives
It means there are not rules (rules is a loose term) for how to do this in
the standard.
> may not support the flush cache command.
There is supported v/s enabled, and these can be optional.
Optional == (Mandatory Optional) because nobody wants to not have the
feature ready or they will miss the sale.
> > I will not break support for older hardware, on a whim.
> Not my intention.
Cool.
> > You said you can make a patch, please do so and apply it to your tree.
> > Now, if you want the option, submit the patch for review. For two or
> > three days there has been no patch to test.
> Still testing locally. I also want to fix the code so that the flush is
> done before the standby.
Wait, how did the order go south?
> >
> > To be absolutely honest, I really do not like to give options in the
> > kernel-config build which can cause backwards compatablity problems.
> This wouldn't be a config option. You would have to modify ide.c by
> hand to disable standby.
So a manual config option? That is more reasonable and not doable by
accident.
Cheers,
Andre Hedrick
LAD Storage Consulting Group
next prev parent reply other threads:[~2002-09-15 4:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-14 18:28 Alex Davis
2002-09-14 19:32 ` Alan Cox
2002-09-14 19:52 ` Alex Davis
2002-09-14 21:14 ` Andre Hedrick
2002-09-14 20:57 ` Andre Hedrick
2002-09-14 21:41 ` Alex Davis
2002-09-15 4:16 ` Andre Hedrick [this message]
2002-09-15 7:40 ` Alex Davis
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.10.10209141548370.6925-100000@master.linux-ide.org \
--to=andre@linux-ide.org \
--cc=alex14641@yahoo.com \
--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
all inboxes | Powered by JetHome®