Re: parport problems with devfs
On Wed, 16 May 2001, Nico Schottelius wrote: > 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. > > [...] > > # make our own device out of /dev > flapp:/ # mknod /lp0 c 6 0 ^ You are creating /lp0 and not /dev/lp0. Anuradha -- http://www.bee.lk/people/anuradha/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: parport problems with devfs
On Wed, 16 May 2001, Nico Schottelius wrote: 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. [...] # make our own device out of /dev flapp:/ # mknod /lp0 c 6 0 ^ You are creating /lp0 and not /dev/lp0. Anuradha -- http://www.bee.lk/people/anuradha/ - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: parport problems with devfs
Hmm..seems you are exactly right! Sorry for that wrong though! Nico Philip Blundell wrote: > >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. > > I don't think this is a bug. You need to load the `lp' module. > > p. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: parport problems with devfs
>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. I don't think this is a bug. You need to load the `lp' module. p. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
parport problems with devfs
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 # 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 ptmxroot usb ..console fullinputmisc pts shm vc .devfsd cpu gpmctl kmem null pty tty vcc apm_bios discside 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 charParallel 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 ptmxroot usb ..console fullinputmisc pts shm vc .devfsd cpu gpmctl kmem null pty tty vcc apm_bios discside 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 fullinputmisc ptmx rootusb .devfsd cpu gpmctl kmem null pts shm vc apm_bios discside log port pty tty vcc # there is now the entry printers/0.
parport problems with devfs
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 # 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 ptmxroot usb ..console fullinputmisc pts shm vc .devfsd cpu gpmctl kmem null pty tty vcc apm_bios discside 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 charParallel 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 ptmxroot usb ..console fullinputmisc pts shm vc .devfsd cpu gpmctl kmem null pty tty vcc apm_bios discside 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 fullinputmisc ptmx rootusb .devfsd cpu gpmctl kmem null pts shm vc apm_bios discside log port pty tty vcc # there is now the entry printers/0.
Re: parport problems with devfs
Hmm..seems you are exactly right! Sorry for that wrong though! Nico Philip Blundell wrote: 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. I don't think this is a bug. You need to load the `lp' module. p. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: parport problems with devfs
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. I don't think this is a bug. You need to load the `lp' module. p. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
