All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Kevin P. Fleming" <kpfleming@cox.net>
To: Stanislav Brabec <utx@penguin.cz>
Cc: Andre Hedrick <andre@linux-ide.org>,
	Paul Bristow <paul@paulbristow.net>,
	linux-kernel@vger.kernel.org
Subject: Re: ide-floppy & devfs - /dev entry not created if drive is empty
Date: Tue, 20 Aug 2002 10:02:57 -0700	[thread overview]
Message-ID: <3D627641.4040301@cox.net> (raw)
In-Reply-To: 20020820110910.GB2831@utx

This problem is present on all devices supported by the ide-floppy 
driver. It won't be fixed until the ide-probe patch makes it into the 
official kernel. At that point the /dev/discs/... entry for the drive 
will appear at boot time even without media present in the drive.

However, without my other media change handling patches, the partition 
entries inside the /dev/discs/... directory for the floppy drive will 
not stay in sync terribly well when you make media changes.

Stanislav Brabec wrote:
> Stanislav Brabec wrote:
> 
>>If module ide-floppy is loaded and no disc is present in the drive,
>>/dev/ide/host0/bus1/target1/lun0/disc entry is not created. Later
>>inserted media cannot be checked in any way, because no /dev entry
>>exists.
>>
> 
> Kevin P. Fleming wrote:
> 
>>diff -X dontdiff -urN linux/drivers/ide/ide-probe.c
>>linux-probe/drivers/ide/ide-probe.c
> 
> 
> Does anybody know, whether this problem was present on LS-120/240,
> IOMEGA PocketZip and JAZ devices and is fixed now?
> 


      reply	other threads:[~2002-08-20 16:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-18 18:56 ide-floppy & devfs - /dev entry not created if drive is empty Stanislav Brabec
2002-08-20  0:04 ` Kevin P. Fleming
2002-08-20  0:45   ` Andre Hedrick
2002-08-20  1:12     ` Kevin P. Fleming
2002-08-20  1:19       ` Andre Hedrick
2002-08-20 11:09       ` Stanislav Brabec
2002-08-20 17:02         ` Kevin P. Fleming [this message]

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=3D627641.4040301@cox.net \
    --to=kpfleming@cox.net \
    --cc=andre@linux-ide.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul@paulbristow.net \
    --cc=utx@penguin.cz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.