The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	Dan Carpenter <dan.carpenter@oracle.com>,
	linux-kernel@vger.kernel.org, jdelvare@suse.de
Subject: Re: [PATCH v2 WIP 1/2] parport: add device-model to parport subsystem
Date: Sat, 25 Apr 2015 11:39:29 +0530	[thread overview]
Message-ID: <20150425060929.GB3222@sudip-PC> (raw)
In-Reply-To: <20150424193702.2f14d4a6@lxorguk.ukuu.org.uk>

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@gmail.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

  reply	other threads:[~2015-04-25  6:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-21 13:52 [PATCH v2 WIP 1/2] parport: add device-model to parport subsystem Sudip Mukherjee
2015-04-21 13:52 ` [PATCH v2 WIP 2/2] staging: panel: modify driver to use new parport device model Sudip Mukherjee
2015-04-23 15:18 ` [PATCH v2 WIP 1/2] parport: add device-model to parport subsystem Dan Carpenter
2015-04-24  6:50   ` Sudip Mukherjee
2015-04-24  7:04     ` Dan Carpenter
2015-04-24  7:45       ` Sudip Mukherjee
2015-04-24  7:26     ` Greg KH
2015-04-24  7:38       ` Sudip Mukherjee
2015-04-24 18:37         ` One Thousand Gnomes
2015-04-25  6:09           ` Sudip Mukherjee [this message]
2015-04-25  9:59             ` Sudip Mukherjee

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=20150425060929.GB3222@sudip-PC \
    --to=sudipm.mukherjee@gmail.com \
    --cc=dan.carpenter@oracle.com \
    --cc=gnomes@lxorguk.ukuu.org.uk \
    --cc=gregkh@linuxfoundation.org \
    --cc=jdelvare@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    /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