From: Sandro Latini <smanet@tiscali.it>
To: linux-hotplug@vger.kernel.org
Subject: Strange parport detection
Date: Sat, 14 May 2005 20:37:15 +0000 [thread overview]
Message-ID: <4286617B.8070000@tiscali.it> (raw)
Hi,
i'm using a LFS linux with udev version 0.57. All works fine except for
the parport device that is not correctly rappresented in /dev.
I have just looked in dmesg for the right assignament of the parallel
port and all seems fine. In sysfs there is a "parport0" too.
Then i have looked udev rules file and found this:
"KERNEL="parport[0-9]*", NAME="%k", GROUP="lp"
This is the standard file of LFS udev rules and searching around with
google i have seen that it's widley used. Is it right? Or is a bug?
Because i have tried to change the string above with this:
KERNEL="parport0", NAME="%k", GROUP="lp"
matching completly the name of the port.. and it's a mistake but
parport0 dev node is now in /dev!
This is my dmesg when parport is loaded:
pnp: the driver 'parport_pc' has been registered
pnp: match found with the PnP device '00:07' and the driver 'parport_pc'
parport: PnPBIOS parport detected.
parport0: PC-style at 0x378 (0x778), irq 7, dma 3
[PCSPP,TRISTATE,COMPAT,EPP,ECP,DMA]
Thanks in advance for any support or fix :)
Sandro Latini
-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_ids93&alloc_id\x16281&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next reply other threads:[~2005-05-14 20:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-14 20:37 Sandro Latini [this message]
2005-05-15 4:31 ` Strange parport detection Alexander E. Patrakov
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=4286617B.8070000@tiscali.it \
--to=smanet@tiscali.it \
--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 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.