From: "Timothy D. Lenz" <tlenz@vorgon.com>
To: linux-media@vger.kernel.org
Subject: Re: laggy remote on x64
Date: Thu, 01 Jul 2010 21:20:10 -0700 [thread overview]
Message-ID: <4C2D68FA.6010603@vorgon.com> (raw)
In-Reply-To: <4C2A87A4.1090104@vorgon.com>
I have now noticed that IR drivers are being loaded when I modprobe
cx23885 to load the drivers for the HVR-1800 which doesn't even have a
remote. The 32bit computer doesn't have this card, it has a Nexus and a
FusionHDTV7 express. The drivers that are being loaded seem to be enough
to get a responce from the nexus remote, but it's doing exactly the same
thing as when I also modprobe ir_kbd_i2c which was always used in the
past to load remote drivers for the nexus and is what I have been using
to load drivers for the Fusion card. Is there some kind of conflict now?
I've had the 1800 in the x64 system with the nexus for a long time but
stopped using/updating it to get the 32bit system running. There seems
to be a problem with the new IR drivers.
On 6/29/2010 4:54 PM, Timothy D. Lenz wrote:
> I have 2 systems nearly identical except one runs 64bit and the other
> runs 32bit. I'm now trying to use the remote port on the nexus-s card.
> The 32 bit seems to be working ok, but the 64bit acts like it's bussy
> doing somthing else. It randomly won't respond to the remote. It doesn't
> buffer the keys or anything. Wait a moment and maybe it works fine for a
> few presses. When it doesn't respond is highly random. Kernel-2.6.34,
> debian squeeze updated a few days ago, v4l is hg from 06/25/2010
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2010-07-02 4:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-29 23:54 laggy remote on x64 Timothy D. Lenz
2010-07-02 4:20 ` Timothy D. Lenz [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=4C2D68FA.6010603@vorgon.com \
--to=tlenz@vorgon.com \
--cc=linux-media@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;
as well as URLs for NNTP newsgroup(s).