public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@rpsys.net>
To: Mark Lord <lkml@rtr.ca>
Cc: Greg KH <greg@kroah.com>, Alan Cox <alan@lxorguk.ukuu.org.uk>,
	linux-kernel@vger.kernel.org, damir.perisa@solnet.ch,
	akpm@osdl.org, Kay Sievers <kay.sievers@vrfy.org>
Subject: Re: [patch] Re: 2.6.14-rc5-mm1 - ide-cs broken!
Date: Thu, 10 Nov 2005 15:03:01 +0000	[thread overview]
Message-ID: <1131634982.8499.63.camel@localhost.localdomain> (raw)
In-Reply-To: <43735FC8.2090101@rtr.ca>

On Thu, 2005-11-10 at 09:57 -0500, Mark Lord wrote: 
> Richard Purdie wrote:
> >
> > - *	FIXME: This treatment is probably applicable for *all* PCMCIA (PC CARD)
> > - *	devices, so in linux 2.3.x we should change this to just treat all
> > - *	PCMCIA  drives this way, and get rid of the model-name tests below
> > - *	(too big of an interface change for 2.4.x).
> > - *	At that time, we might also consider parameterizing the timeouts and
> > - *	retries, since these are MUCH faster than mechanical drives. -M.Lord
> > - */
> 
> I believe the latter half of those comments (timeouts) should
> be left in the IDE layer (somewhere), as a note to current/future
> maintainers about something that does need fixing eventually.
> 
> Something like this:
> 
> /*
>   * FIXME:  Someday we ought to parameterize IDE timeouts to use
>   * much smaller values when dealing with flash memory cards.
>   * For example, these devices never require more than a second
>   * (much less, actually) for "spin-up", compared with a limit
>   * of 31 seconds for mechanical ATA drives.  This would speed up
>   * error recovery for these popular devices, especially in embedded work
>   */

Does this still apply given the existence of devices like microdrives?
My microdrive certainly sounds like it could take a second or two to
spin up...

Richard


  reply	other threads:[~2005-11-10 15:03 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20051103220305.77620d8f.akpm@osdl.org>
2005-11-04  7:19 ` 2.6.14-rc5-mm1 - ide-cs broken! Greg KH
2005-11-04 15:14   ` Alan Cox
2005-11-04 16:37     ` Greg KH
2005-11-09 10:17       ` [patch] " Richard Purdie
2005-11-09 12:08         ` Alan Cox
2005-11-09 16:41         ` Bill Davidsen
2005-11-09 17:27           ` Richard Purdie
2005-11-09 20:56             ` Bill Davidsen
2005-11-09 21:37               ` Richard Purdie
2005-11-09 22:55                 ` Bill Davidsen
2005-11-09 23:02                   ` Damir Perisa
2005-11-09 21:48               ` Damir Perisa
2005-11-10 14:57         ` Mark Lord
2005-11-10 15:03           ` Richard Purdie [this message]
2005-11-04 23:22   ` ide-cs broken / udev magic Damir Perisa
2005-11-04 23:28     ` Greg KH
2005-11-05  2:06       ` Richard Purdie
2005-11-05 12:36         ` Damir Perisa

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=1131634982.8499.63.camel@localhost.localdomain \
    --to=rpurdie@rpsys.net \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=damir.perisa@solnet.ch \
    --cc=greg@kroah.com \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@rtr.ca \
    /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