Date: Sat, 11 Apr 2015 10:35:11 +0530
From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Ondrej Zary <linux@rainbow-software.org>
Cc: gregkh@linuxfoundation.org, dan.carpenter@oracle.com,
        linux-kernel@vger.kernel.org
Subject: Re: [PATCH WIP] parport: add device model
Message-ID: <20150411050511.GB3496@sudip-PC>
References: <1428676238-17141-1-git-send-email-sudipm.mukherjee@gmail.com>
 <201504102024.24220.linux@rainbow-software.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <201504102024.24220.linux@rainbow-software.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1098
Lines: 26

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.

regards
sudip

> 
> -- 
> Ondrej Zary
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/