| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Sat, 11 Apr 2015 11:24:35 +0200 From: Ondrej Zary <linux@...nbow-software.org> To: Sudip Mukherjee <sudipm.mukherjee@...il.com> Cc: gregkh@...uxfoundation.org, dan.carpenter@...cle.com, linux-kernel@...r.kernel.org Subject: Re: [PATCH WIP] parport: add device model On Saturday 11 April 2015 07:05:11 you wrote: > On Fri, Apr 10, 2015 at 08:24:23PM +0200, Ondrej Zary wrote: > > On Friday 10 April 2015 16:30:38 Sudip Mukherjee wrote: > > > > Many newer parallel port devices support plug&play (IEEE1284 device ID) > > but Linux never supported it properly. The ID is probed and even the > > class is printed in the kernel log (drivers/parport/probe.c) but there's > > no support for module autoloading based on that. > > This could be a good opportunity to add this support. I was thinking > > about this while playing with some parport webcams recently. > > I think yes, or maybe immediately after this updation is over. But the > main problem for me will be to get hold of a plug&play parallel port > device. is any available now? Can you please suggest one other than > webcam so that you can test on webcam and I can test it on something > else. Most printers produced since 1995 or 1996 are plug&play capable (lp module could be loaded if a printer-class device is found) and also external drives (ZIP, LS-120). -- Ondrej Zary -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists