public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe <joeja@mindspring.com>
To: Jakob Kemi <jakob.kemi@telia.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.14/2.4.15 cpia driver IS broke.. no its parport
Date: Sun, 25 Nov 2001 11:08:59 -0800	[thread overview]
Message-ID: <3C0141CB.617DEC1D@mindspring.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0111230950580.24427-100000@netfinity.realnet.co.sz> <3C000EE7.D69C1482@mindspring.com> <200111242143.fAOLhsa10672@d1o849.telia.com> <200111242220.fAOMKxa13508@d1o849.telia.com>

[-- Attachment #1: Type: text/plain, Size: 946 bytes --]

In that case I'ss send my patch to 2.4.14 to the list and hope it helps others
with their parallel port webcams.. (its small)

Joe

> This works perfectly for my w9966 parport webcam!
>         /Jakob
>
> On Saturdayen den 24 November 2001 22.43, Jakob Kemi wrote:
> > Great!
> >
> > I'll test it right away.
> >       /Jakob
> >
> > > The problem is that in the call to acknowledge the handshake (Event 44?
> > > about line592) the call to parport_frob_control or
> > > parport_pc_frob_control as it is #defined to is called with a 0 which I
> > > think causes the code to call parport_pc_data_forward and the new code
> > > just calls
> > > parport_pc_data_reverse. I think that we may need to call the
> > > parport_pc_data_forward still.
> > >
> > > -               parport_write_control (port, ctl);   // new code
> > > +               parport_frob_control (port, PARPORT_CONTROL_AUTOFD, 0);
> > > //old working code
> > >
> > > Joe
> > >
>

[-- Attachment #2: ieee1294_ops_fix-2.4.14 --]
[-- Type: text/plain, Size: 458 bytes --]

--- linux-2.4.14/drivers/parport/ieee1284_ops.c	Fri Nov 23 20:59:42 2001
+++ linux-2.4.current/drivers/parport/ieee1284_ops.c	Sun Nov 18 21:13:10 2001
@@ -592,7 +592,7 @@
 		}
 
 		/* Event 44: Set HostAck high, acknowledging handshake. */
-		parport_write_control (port, ctl);
+		parport_frob_control (port, PARPORT_CONTROL_AUTOFD, 0);
 
 		/* Event 45: The peripheral has 35ms to set nAck high. */
 		if (parport_wait_peripheral (port, PARPORT_STATUS_ACK,

      reply	other threads:[~2001-11-25 19:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.33.0111230950580.24427-100000@netfinity.realnet.co.sz>
2001-11-24  3:41 ` 2.4.14/2.4.15 cpia driver IS broke.. no its parport && other problems with 2.4.15 Joe
2001-11-24 21:19   ` 2.4.14/2.4.15 cpia driver IS broke.. no its parport Joe
2001-11-24 21:43     ` Jakob Kemi
2001-11-24 22:20       ` Jakob Kemi
2001-11-25 19:08         ` Joe [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=3C0141CB.617DEC1D@mindspring.com \
    --to=joeja@mindspring.com \
    --cc=jakob.kemi@telia.com \
    --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