lkml.org 
[lkml]   [2002]   [Aug]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRE: IDE-flash device and hard disk on same controller
Date
> Heater, Daniel (IndSys, GEFanuc, VMIC) wrote:
> > The IDE driver, file ide-probe.c currently contains this
> test do prevent
> > hard drives and IDE-flash devices (ex CompactFlash) from
> co-existing on the
> > same IDE controller.
> >
> > /*
> > * 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;
> > mate->noprobe = 1;
> > }
> > }
> >
> > This test's assumption that a spinning hard drive cannot
> coexist on the same
> > controller as an IDE-flash device is incorrect. I have a
> working setup with
> > such a configuration. I don't think that the IDE subsystem
> should punish
> > everyone because _some_ hardware cannot tolerate this configuration.
> >
> > One solution may be to remove this test from the IDE
> subsystem and force
> > users with buggy hardware to explicitly disable probing
> for a second
> > device. I think the parameters hdx=none or hdx=noprobe
> should work for
> > them.
> >
> > Comments??
>
> Mentioned several times (and there is a workaround), see:
> http://marc.theaimsgroup.com/?l=linux-kernel&m=100446144028502&w=2
>
> I really think some of the default CF logic is bogus.
>
> Pádraig.
>


OK. hdc=flash works where hdc=hard drive and hdd=CompactFlash.

Thanks Padraig.

I guess it's 6 of one, half-dozen the other, but telling the kernel that my
hard drive is a flash drive just makes me feel squidgy! I'm still inclined
to suggest that the test that _prevents_ hard drive + CF configuration is no
longer appropriate now that _some_ (most??) hardware vendors have figured
out how to get ide-flash devices to work without "hanging" when no second
device is present. Users with incompatible hardware can still prevent the
long system hang by using hdx=none.

I also used this workaround (hdb=flash) to configure a system with hda=flash
and hdb=cdrom. This seems to work also. Are there any side effects to
telling the kernel that the hard drive or cdrom is a flash device (such as
marking it removable or not marking it removable)?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:28    [W:0.131 / U:0.752 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site