From: Dale Pontius <DEPontius@edgehp.net>
To: Andy Walls <awalls@radix.net>
Cc: "video4linux-list@redhat.com" <video4linux-list@redhat.com>
Subject: Re: cx18: Fix needs test: more robust solution to get CX23418 based cards to work reliably
Date: Tue, 07 Oct 2008 22:20:07 -0400 [thread overview]
Message-ID: <48EC18D7.3070807@edgehp.net> (raw)
In-Reply-To: <1222651357.2640.21.camel@morgan.walls.org>
Andy Walls wrote:
> cx18 driver users:
>
> In this repository:
>
> http://linuxtv.org/hg/~awalls/cx18-mmio-fixes/
>
Can't get there from here:
Mercurial Repositories
The specified repository "~awalls" is unknown, sorry. Please go back to
the main repository list page.
I can see that I'm a bit late, and maybe you've migrated
"cx-18-mmio-fixes" to somewhere else, but the error messages seems to
deny your existence at all, and that seems odd.
I've been getting help from you with problems with my HVR-1600, and have
a friend with WinXP machines who can likely help me out testing it, but
he's been on vacation, and shortly I'll be gone for a bit.
In the meantime, since it appears that I've been having i2c problems and
the mmio_ndelay gave me marginally better operation, I'd like to give
this patch a try. (Or is it folded into the main repository, already.)
Thanks,
Dale Pontius
> is a change to the cx18 driver to (hopefully) improve reliability of
> CX23418 based cards operation in linux. If all goes will, this change
> will supersede the "mmio_ndelay" hack, which I hope to phase out.
>
> This change adds checks and retries to all PCI MMIO access to the
> CX23418 chip and adds a new module parameter 'retry_mmio' which is
> enabled by default.
>
> With this change, the module defaults are set so the following
> statements are equivalent:
>
> # modprobe cx18
> # modprobe cx18 retry_mmio=1 mmio_ndelay=0
>
>
> With checks and retries enabled, limited experiments have shown a card
> operates properly in my old Intel 82801AA based motherboard with this
> fix in place. I found that the mmio_ndelay parameter has little or no
> effect with these checks and retires enabled.
>
> Experiments have also shown that, if you have previously had a problem
> with the cx18 driver/CX23418 in your system, then
>
> # modprobe cx18 retry_mmio=0 mmio_delay=(something)
>
> can put the CX23418 in a state, such that a reset is required to have
> the unit respond properly again when trying to reload cx18 driver
> another time. (So my advice is don't turn off retry_mmio.)
>
> If you've had to use the mmio_ndelay parameter in the past to get the
> card to work for you, or your card has never worked for you, please let
> me know how this patch works for you.
>
> Regards,
> Andy
>
>
> --
> video4linux-list mailing list
> Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
> https://www.redhat.com/mailman/listinfo/video4linux-list
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
next prev parent reply other threads:[~2008-10-08 2:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-29 1:22 cx18: Fix needs test: more robust solution to get CX23418 based cards to work reliably Andy Walls
2008-10-08 2:20 ` Dale Pontius [this message]
2008-10-08 13:45 ` Steven Toth
2008-10-08 21:35 ` Andy Walls
2008-10-10 0:20 ` Dale Pontius
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=48EC18D7.3070807@edgehp.net \
--to=depontius@edgehp.net \
--cc=awalls@radix.net \
--cc=video4linux-list@redhat.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