All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jack Howarth <howarth@nitro.med.uc.edu>
To: linux-kernel@vger.kernel.org
Subject: ide-floppy.c vs devfs
Date: Sat, 10 Nov 2001 23:39:48 -0500 (EST)	[thread overview]
Message-ID: <200111110439.XAA53352@nitro.msbb.uc.edu> (raw)

Paul,
   Is ide-floppy supposed to be devfs friendly? I ask
because on Linux 2.4.15-pre2 (and previous kernels)
on the Powermac (Debian ppc sid) I find that the
ide-floppy driver only creates device for my ide 
zip if a zip disk is inserted at boot time. Otherwise
the /dev/ide/host1/bus0/target1/lun0 directory doesn't
contain a device node for the zip whereas the ide-cdrom
driver creates a /dev/ide/host1/bus0/target0/lun0/cd
fine without a cdrom disk inserted at boot time. I find
that the only way I can get the zip device created at
boot time without media inserted is to use ide-scsi 
emulation and turn off ide-floppy when I configure the
kernel. Is this issue a known problem and does it
exist for other arches than powerpc (Powermac)? Thanks
in advance for any advice.
                      Jack
------------------------------------------------------------------------------
Jack W. Howarth, Ph.D.                                    231 Albert Sabin Way
NMR Facility Director                              Cincinnati, Ohio 45267-0524
Dept. of Molecular Genetics                              phone: (513) 558-4420
Univ. of Cincinnati College of Medicine                    fax: (513) 558-8474

             reply	other threads:[~2001-11-11  4:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-11  4:39 Jack Howarth [this message]
2001-11-23  5:13 ` ide-floppy.c vs devfs Richard Gooch
2001-11-25 22:07 ` Paul Bristow
2001-11-25 22:31   ` Richard Gooch
  -- strict thread matches above, loose matches on Subject: below --
2001-11-12  6:48 Borsenkow Andrej
2001-11-26 10:04 Borsenkow Andrej
2001-11-26 17:44 ` Paul Bristow
2001-11-27 12:34   ` Borsenkow Andrej
2001-11-27 17:47     ` Paul Bristow
2001-11-27 20:38       ` Mike Fedyk

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=200111110439.XAA53352@nitro.msbb.uc.edu \
    --to=howarth@nitro.med.uc.edu \
    --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 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.