linux-kernel - Re: [PATCH v2 WIP 1/2] parport: add device-model to parport subsystem

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20150425060929.GB3222@sudip-PC>
Date:	Sat, 25 Apr 2015 11:39:29 +0530
From:	Sudip Mukherjee <sudipm.mukherjee@...il.com>
To:	One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>
Cc:	Greg KH <gregkh@...uxfoundation.org>,
	Dan Carpenter <dan.carpenter@...cle.com>,
	linux-kernel@...r.kernel.org, jdelvare@...e.de
Subject: Re: [PATCH v2 WIP 1/2] parport: add device-model to parport subsystem

On Fri, Apr 24, 2015 at 07:37:02PM +0100, One Thousand Gnomes wrote:

Hi Alan,
> On Fri, 24 Apr 2015 13:08:25 +0530
> Sudip Mukherjee <sudipm.mukherjee@...il.com> wrote:
> 
> > On Fri, Apr 24, 2015 at 09:26:08AM +0200, Greg KH wrote:
> > > On Fri, Apr 24, 2015 at 12:20:26PM +0530, Sudip Mukherjee wrote:
> > > > > What does ddev stand for?  Anyway, it's probably better to call it
> > > > > bus_dev?
> > > > ok.
> > > > I think I will wait today for some comments from Greg and then send in
> > > > the v3 tomorrow.
> > > 
> > > Don't wait for me, it's going to be a week or so at the earliest before
> > > I have a chance to look at this, sorry.
> > 
> > No problem. I will change what Dan has suggested and will
> > request Alan and Dean to check on their hardware as well (ofcourse if
> > they have time).
> 
> Let me know when you have a set of patches you feel are good for testing
> and I'll give them a go.
This series of WIP is also good for testing. But for next version of WIP
I need to know something from Jean about his i2c-parport.
For all other drivers using the parallel port, they are choosing which
port to use. But i2c-parport is not specifying that. So as a result, in
my test system which has multiple parallel ports, when I load the module,
i2c-parport is claiming all the ports with exclusive access. So if i
want to use i2c-parport on one parallel port and any other device on
another port then that is not possible. If that is the intended behaviour
then I need to change some parts in the way I was making the parallel
port device-model. Anyways, I have mailed Jean yesterday, and waiting
for his comments now. Adding cc to Jean also to this mail.

>I just picked up a backpack CD-ROM drive on ebay
> for 99p as well 8)

wow, share me the link please. I will also get one.
I am able to manage only one parallel printer and staging/panel for
testing. I am looking for a parallel port zip drive or cdrom or scanner
to manage and test the code better. but :(

regards
sudip

> 
> Alan
--
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/