public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Padraig Brady <Padraig@AnteFacto.com>
To: Andre Hedrick <andre@linux-ide.org>
Cc: Richard Smith <ras2@tant.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Compact flash disk and slave drives in 2.4.2
Date: Tue, 27 Mar 2001 18:06:52 +0100	[thread overview]
Message-ID: <3AC0C8AC.4010304@AnteFacto.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10103270838450.16125-100000@master.linux-ide.org>

OK the following assumes CF never have slaves which is just wrong.
The CF should be logically treated as an IDE harddisk. So the fix is
probably have a kernel parameter that causes the following check to
be skipped?

/*
   * Prevent long system lockup probing later for non-existant
   * slave drive if the hwif is actually a flash memory card of some 
variety:
   */
  if (drive_is_flashcard(drive)) {
          ide_drive_t *mate = &HWIF(drive)->drives[1^drive->select.b.unit];
          if (!mate->ata_flash) {
                mate->present = 0;
                ide_drive_t *mate = 
&HWIF(drive)->drives[1^drive->select.b.unit]
                mate->noprobe = 1;
          }
  }

But do we need this check? Is it just for speed. If you have an "ordinary"
harddrive as master with no slave, will the check for slave cause the same
"long system lockup", and if not, why.

Padraig.

Andre Hedrick wrote:

> Because in laptops, the primary use of CFA.
> Laptops using CFA do not have slaves.


  reply	other threads:[~2001-03-27 17:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-27  7:25 Compact flash disk and slave drives in 2.4.2 Richard Smith
2001-03-27 14:20 ` Padraig Brady
2001-03-27 16:42   ` Andre Hedrick
2001-03-27 17:06     ` Padraig Brady [this message]
2001-03-27 17:17       ` Andre Hedrick
2001-03-27 18:50         ` Padraig Brady
2001-03-27 18:56           ` Andre Hedrick
2001-03-27 19:25         ` Richard A. Smith
2001-03-27 20:15           ` Andre Hedrick

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=3AC0C8AC.4010304@AnteFacto.com \
    --to=padraig@antefacto.com \
    --cc=andre@linux-ide.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ras2@tant.com \
    /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