linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergey Vlasov <vsu@altlinux.ru>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev and parallel port support
Date: Wed, 05 Oct 2005 11:48:17 +0000	[thread overview]
Message-ID: <20051005154817.3cd31784.vsu@altlinux.ru> (raw)
In-Reply-To: <000101c5c83f$4c7184d0$3502a8c0@cisit.local>

[-- Attachment #1: Type: text/plain, Size: 1037 bytes --]

On Tue, 4 Oct 2005 17:14:11 -0500 Jason Dravet wrote:

> Thank you for the response.  I realize that some devices need static nodes,
> but I am wondering why parallel ports fall into this category at least they
> do according to redhat anyways?

Actually, the lowlevel port driver (parport_pc, or maybe something
other like parport_serial) can in many cases be loaded automatically
(on most modern machines the presence of a legacy parallel port is
shown by PnP or ACPI).  Only old hardware which does not support any
form of PnP will require manual loading of parport_pc.

The real problem is that currently there is nothing which will trigger
loading of the highlevel driver (lp or ppdev).  With recent hardware
it is possible to find out what is connected to the parallel port
(look at /proc/sys/dev/parport/parport0/autoprobe), but this is often
unreliable.  So the easy way is to create static nodes for /dev/lp*
and /dev/parport*, and then a program which tries to use these devices
will trigger loading of the appropriate module.

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2005-10-05 11:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-03 17:24 udev and parallel port support Jason Dravet
2005-10-04 21:31 ` Greg KH
2005-10-04 21:48 ` Jason Dravet
2005-10-04 21:56 ` Greg KH
2005-10-04 21:57 ` Kay Sievers
2005-10-04 22:12 ` Jason Dravet
2005-10-04 22:14 ` Jason Dravet
2005-10-04 22:26 ` Greg KH
2005-10-04 22:38 ` 'Kay Sievers'
2005-10-05 11:48 ` Sergey Vlasov [this message]
2005-10-05 14:05 ` Jason Dravet
2005-10-06  7:15 ` Marco d'Itri

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=20051005154817.3cd31784.vsu@altlinux.ru \
    --to=vsu@altlinux.ru \
    --cc=linux-hotplug@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).