All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: walt <wa1ter@myrealbox.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Martin Schlemmer <azarah@gentoo.org>
Subject: Re: udev versus parallel-port Zip drive
Date: Wed, 3 Mar 2004 14:01:35 -0800	[thread overview]
Message-ID: <20040303220135.GA32662@kroah.com> (raw)
In-Reply-To: <40465460.1050600@myrealbox.com>

On Wed, Mar 03, 2004 at 01:55:44PM -0800, walt wrote:
> I've been fiddling with Zip-drive support -- both USB and
> parallel-port.
> 
> When I compile everything as modules I find that the
> parallel-port driver for Zip drives (ppa) does not load
> automatically.  To make the parallel Zip drive work I
> need to do a 'modprobe ppa' manually, after which everything
> works as expected.
> 
> I can only imagine the complexity involved in figuring out
> what is attached to the parallel port at boot-time -- there
> must be thousands of possibilities to sort through.
> 
> My question, I suppose, is:  what are the chances that a
> parallel-port device can be automatically detected by udev
> and the appropriate module loaded?  Is this a pipe-dream?
> Or maybe it should already work and I'm just omitting some
> important steps?


udev does no device discovery.  Please, please, please, please remember
this.

udev has nothing to do with this issue.

Here's a little sign to print out for the next time someone tries to
bring this issue up:

	**********************************
	* udev does no device discovery! *
	**********************************

thanks,

greg k-h

  reply	other threads:[~2004-03-03 22:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-03 21:55 udev versus parallel-port Zip drive walt
2004-03-03 22:01 ` Greg KH [this message]
2004-03-04  0:45   ` walt
2004-03-03 22:06 ` viro
2004-03-04 17:08 ` Martin Schlemmer

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=20040303220135.GA32662@kroah.com \
    --to=greg@kroah.com \
    --cc=azarah@gentoo.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wa1ter@myrealbox.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 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.