public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* 2.4.14/2.4.15 cpia driver IS broke.. no its parport && other problems  with 2.4.15
       [not found] <Pine.LNX.4.33.0111230950580.24427-100000@netfinity.realnet.co.sz>
@ 2001-11-24  3:41 ` Joe
  2001-11-24 21:19   ` 2.4.14/2.4.15 cpia driver IS broke.. no its parport Joe
  0 siblings, 1 reply; 5+ messages in thread
From: Joe @ 2001-11-24  3:41 UTC (permalink / raw)
  To: Zwane Mwaikambo, linux-kernel

I have been doing some testing and debugging and found out that something in
the 2.4.14 parport driver is breaking my webcam II.  I have a patch that
reverts out all the changes in 2.4.14 parport driver back to 2.4.13 and the
driver now works.  I am going to do some more testing and see if I can narrow
the code down.  Right now the patch is  about 700+ lines, but reverts out
ALL the parport changes.

My hardward is a VIA chipset (686). It is the ABiT KT7A MB.

What's happening is that the cpia is being recgonized, but the video device
is not accessable. This is in both 2.4.15 and 2.4.14, with the creative
WebCam II.

In the /proc/cpia/video0 file it shows the CPIA version as 0.00 instead of
1.20.

On another note it seems that with 2.4.15 umount is not working on my
machine.  It mounts the drives okay, but requires umount -n to be used which
seems to be forcing the unmount of the drive.  I am using mount 2.11g do
I need to upgrade this? I'm NOT using ext3 fs, just ext2.  Do I need to
upgrade something??

Oh and because umount fails all my services leave files in /var/lock and
/tmp.X11** and when the system restarts many of these services are to dumb to
realize that the PID for these processes is not running and don't start
(xdm/gdm).   The other thing that happens is that when I restart the machine
it comes up and runs fsck on most of the drives and then it has other
problems.

The only workaournd seems to be to bring the machine to runlevel 1 (init
1) from runlevel 5 or 3 before I shutdown.    This kills ALL the services.
Then I can umount -n the drives, run e2fsck (if need), remount them and
remove the lock files and tmp files (if they are there still). remount the
drives and then halt the machine.  It shouldnt be that hard though.

Joe


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: 2.4.14/2.4.15 cpia driver IS broke.. no its parport
  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   ` Joe
  2001-11-24 21:43     ` Jakob Kemi
  0 siblings, 1 reply; 5+ messages in thread
From: Joe @ 2001-11-24 21:19 UTC (permalink / raw)
  To: Zwane Mwaikambo, linux-kernel

Okay I have done some more research and found out what is happening!
After further testing I have found out that the problem with the parport driver
is actually in the ieee1294 code.   One of the changes in the file
drivers/parport/ieee1294_ops.c is causing problems.  (for me atleast)

The code has changed from calls to parport_frob_control() to calls to
parport_write_control ().(Fine)

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

> I have been doing some testing and debugging and found out that something in
> the 2.4.14 parport driver is breaking my webcam II.  I have a patch that
> reverts out all the changes in 2.4.14 parport driver back to 2.4.13 and the
> driver now works.  I am going to do some more testing and see if I can narrow
> the code down.  Right now the patch is  about 700+ lines, but reverts out
> ALL the parport changes.
>
> My hardward is a VIA chipset (686). It is the ABiT KT7A MB.
>
> What's happening is that the cpia is being recgonized, but the video device
> is not accessable. This is in both 2.4.15 and 2.4.14, with the creative
> WebCam II.
>
> In the /proc/cpia/video0 file it shows the CPIA version as 0.00 instead of
> 1.20.


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: 2.4.14/2.4.15 cpia driver IS broke.. no its parport
  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
  0 siblings, 1 reply; 5+ messages in thread
From: Jakob Kemi @ 2001-11-24 21:43 UTC (permalink / raw)
  To: joeja, linux-kernel

Great!

I'll test it right away.
	/Jakob


On Saturdayen den 24 November 2001 22.19, Joe wrote:
> Okay I have done some more research and found out what is happening!
> After further testing I have found out that the problem with the parport
> driver is actually in the ieee1294 code.   One of the changes in the file
> drivers/parport/ieee1294_ops.c is causing problems.  (for me atleast)
>
> The code has changed from calls to parport_frob_control() to calls to
> parport_write_control ().(Fine)
>
> 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
>
> > I have been doing some testing and debugging and found out that something
> > in the 2.4.14 parport driver is breaking my webcam II.  I have a patch
> > that reverts out all the changes in 2.4.14 parport driver back to 2.4.13
> > and the driver now works.  I am going to do some more testing and see if
> > I can narrow the code down.  Right now the patch is  about 700+ lines,
> > but reverts out ALL the parport changes.
> >
> > My hardward is a VIA chipset (686). It is the ABiT KT7A MB.
> >
> > What's happening is that the cpia is being recgonized, but the video
> > device is not accessable. This is in both 2.4.15 and 2.4.14, with the
> > creative WebCam II.
> >
> > In the /proc/cpia/video0 file it shows the CPIA version as 0.00 instead
> > of 1.20.
>
> -
> 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/

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: 2.4.14/2.4.15 cpia driver IS broke.. no its parport
  2001-11-24 21:43     ` Jakob Kemi
@ 2001-11-24 22:20       ` Jakob Kemi
  2001-11-25 19:08         ` Joe
  0 siblings, 1 reply; 5+ messages in thread
From: Jakob Kemi @ 2001-11-24 22:20 UTC (permalink / raw)
  To: joeja, linux-kernel

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
>
> On Saturdayen den 24 November 2001 22.19, Joe wrote:
> > Okay I have done some more research and found out what is happening!
> > After further testing I have found out that the problem with the parport
> > driver is actually in the ieee1294 code.   One of the changes in the file
> > drivers/parport/ieee1294_ops.c is causing problems.  (for me atleast)
> >
> > The code has changed from calls to parport_frob_control() to calls to
> > parport_write_control ().(Fine)
> >
> > 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
> >
> > > I have been doing some testing and debugging and found out that
> > > something in the 2.4.14 parport driver is breaking my webcam II.  I
> > > have a patch that reverts out all the changes in 2.4.14 parport driver
> > > back to 2.4.13 and the driver now works.  I am going to do some more
> > > testing and see if I can narrow the code down.  Right now the patch is 
> > > about 700+ lines, but reverts out ALL the parport changes.
> > >
> > > My hardward is a VIA chipset (686). It is the ABiT KT7A MB.
> > >
> > > What's happening is that the cpia is being recgonized, but the video
> > > device is not accessable. This is in both 2.4.15 and 2.4.14, with the
> > > creative WebCam II.
> > >
> > > In the /proc/cpia/video0 file it shows the CPIA version as 0.00 instead
> > > of 1.20.
> >
> > -
> > 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/
>
> -
> 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/

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: 2.4.14/2.4.15 cpia driver IS broke.. no its parport
  2001-11-24 22:20       ` Jakob Kemi
@ 2001-11-25 19:08         ` Joe
  0 siblings, 0 replies; 5+ messages in thread
From: Joe @ 2001-11-25 19:08 UTC (permalink / raw)
  To: Jakob Kemi; +Cc: linux-kernel

[-- 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,

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2001-11-25 19:03 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox