From: Nico Schottelius <nicos@pcsystems.de>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Philip.Blundell@pobox.com, tim@cyberelk.demon.co.uk,
campbell@torque.net, andrea@e-mind.com, linux-parport@torque.net
Subject: parport problems with devfs
Date: Wed, 16 May 2001 15:19:02 +0200 [thread overview]
Message-ID: <3B027E46.5095E8BB@pcsystems.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 182 bytes --]
Hello!
I attached the problem occured with parport and devfs.
I don't exactly know where the problem in the parport source
is. If someone has a patch for it, I will test it.
Nico
[-- Attachment #2: DEVFS_parport --]
[-- Type: text/plain, Size: 2058 bytes --]
# Loading the parport and parport_pc modules for my parallelport
flapp:/home/user/nico/gpm-1.19.3 # modprobe parport_pc
# is there an entry in /dev ?
flapp:/home/user/nico/gpm-1.19.3 # ls /dev/
. cdroms fb initctl mem ptmx root usb
.. console full input misc pts shm vc
.devfsd cpu gpmctl kmem null pty tty vcc
apm_bios discs ide log port random urandom zero
# What does the kernel message say ?
flapp:/home/user/nico/gpm-1.19.3 # dmesg | tail -n 14
usb.c: registered new driver hid
mice: PS/2 mouse device common for all mice
0x378: FIFO is 16 bytes
0x378: writeIntrThreshold is 7
0x378: readIntrThreshold is 7
0x378: PWord is 8 bits
0x378: Interrupts are ISA-Pulses
0x378: ECP port cfgA=0x10 cfgB=0x49
0x378: ECP settings irq=7 dma=1
parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE,COMPAT,ECP]
parport0: cpp_daisy: aa5500ff(38)
parport0: assign_addrs: aa5500ff(38)
parport0: cpp_daisy: aa5500ff(38)
parport0: assign_addrs: aa5500ff(38)
# Have a look what lp0 has been before
>From /usr/src/linux/Documentation/ :
6 char Parallel printer devices
0 = /dev/lp0 Parallel printer on parport0
1 = /dev/lp1 Parallel printer on parport1
# make our own device out of /dev
flapp:/ # mknod /lp0 c 6 0
# has anything happened ? No!
flapp:/ # ls /dev/
. cdroms fb initctl mem ptmx root usb
.. console full input misc pts shm vc
.devfsd cpu gpmctl kmem null pty tty vcc
apm_bios discs ide log port random urandom zero
# Use the printer the easiest way :)
flapp:/ # cat /tmp/* > lp0
# And now...
flapp:/ # ls /dev/
. cdroms fb initctl mem printers random urandom zero
.. console full input misc ptmx root usb
.devfsd cpu gpmctl kmem null pts shm vc
apm_bios discs ide log port pty tty vcc
# there is now the entry printers/0.
next reply other threads:[~2001-05-16 13:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-16 13:19 Nico Schottelius [this message]
2001-05-16 13:31 ` parport problems with devfs Philip Blundell
2001-05-16 13:33 ` Nico Schottelius
2001-05-21 19:09 ` Anuradha Ratnaweera
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=3B027E46.5095E8BB@pcsystems.de \
--to=nicos@pcsystems.de \
--cc=Philip.Blundell@pobox.com \
--cc=andrea@e-mind.com \
--cc=campbell@torque.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parport@torque.net \
--cc=tim@cyberelk.demon.co.uk \
/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.