From: Joe <joeja@mindspring.com>
To: Zwane Mwaikambo <zwane@linux.realnet.co.sz>,
linux-kernel@vger.kernel.org
Subject: Re: 2.4.14/2.4.15 cpia driver IS broke.. no its parport
Date: Sat, 24 Nov 2001 13:19:35 -0800 [thread overview]
Message-ID: <3C000EE7.D69C1482@mindspring.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0111230950580.24427-100000@netfinity.realnet.co.sz> <3BFF16F0.C331F0E4@mindspring.com>
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.
next prev parent reply other threads:[~2001-11-24 21:14 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 ` Joe [this message]
2001-11-24 21:43 ` 2.4.14/2.4.15 cpia driver IS broke.. no its parport Jakob Kemi
2001-11-24 22:20 ` Jakob Kemi
2001-11-25 19:08 ` Joe
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=3C000EE7.D69C1482@mindspring.com \
--to=joeja@mindspring.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zwane@linux.realnet.co.sz \
/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