linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ondrej Zary <linux@rainbow-software.org>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: gregkh@linuxfoundation.org, dan.carpenter@oracle.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH WIP] parport: add device model
Date: Sat, 11 Apr 2015 11:24:35 +0200	[thread overview]
Message-ID: <201504111124.35691.linux@rainbow-software.org> (raw)
In-Reply-To: <20150411050511.GB3496@sudip-PC>

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

      reply	other threads:[~2015-04-11  9:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-10 14:30 [PATCH WIP] parport: add device model Sudip Mukherjee
2015-04-10 14:49 ` Dan Carpenter
2015-04-11  5:26   ` Sudip Mukherjee
2015-04-11  7:27     ` Greg KH
2015-04-11  8:11       ` Sudip Mukherjee
2015-04-13  8:27         ` Sudip Mukherjee
2015-04-13  8:43         ` Greg KH
2015-04-13 10:02           ` Sudip Mukherjee
2015-04-13 10:42             ` Greg KH
2015-04-13 10:38     ` Dan Carpenter
2015-04-10 18:24 ` Ondrej Zary
2015-04-11  5:05   ` Sudip Mukherjee
2015-04-11  9:24     ` Ondrej Zary [this message]

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=201504111124.35691.linux@rainbow-software.org \
    --to=linux@rainbow-software.org \
    --cc=dan.carpenter@oracle.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sudipm.mukherjee@gmail.com \
    /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).