linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Grant Likely" <grant.likely@secretlab.ca>
To: "LIU KAN" <liukanh@gmail.com>, linuxppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: Using C67x00 on PXA255 with ov511
Date: Tue, 1 Jan 2008 21:34:03 -0700	[thread overview]
Message-ID: <fa686aa40801012034t4cbf4827m82f05ee8f65cd4ee@mail.gmail.com> (raw)
In-Reply-To: <e99250190801011938w54ad1921oc85bb54fc0481b9d@mail.gmail.com>

On 1/1/08, LIU KAN <liukanh@gmail.com> wrote:
> Hello, Grant
>
>         Thank you for the work on the patch of c67x00, I have use it
> successfully on PXA255, but I still have some problem.
>         Now I can use c67x00 together with usb-disk in 2.6 kerenl at a
> writing speed around 5MB/s. But when I use c67x00 to connect webcam, which
> is drived by ov511, I get the mosaic like picture in  attachment. And when I
> use cy7c67300 provided by cypress in 2.4 kernel with ov511, it work fine. Is
> this because the speed the c67x00 driver for iso_ transfers is too slow? or
> any other reason?
>         How can I solve the problem?

Most likely the scheduling algorithm is not quite right for the
c67x00.  I've had problems with that in the past myself.  You can try
playing around with the parameters in claim_frame_bw() in
c67x00-sched.c.  The web cam is probably using iso transfers so you
should try to find out if all the requested ISO transfers are actually
getting scheduled by the driver.

Please let me know what you find out.  This driver still needs a lot
of tuning and your observations will help a lot.

Cheers,
g.

-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195

           reply	other threads:[~2008-01-02  4:34 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <e99250190801011938w54ad1921oc85bb54fc0481b9d@mail.gmail.com>]

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=fa686aa40801012034t4cbf4827m82f05ee8f65cd4ee@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=liukanh@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).