Linux Media Controller development
 help / color / mirror / Atom feed
From: Sean Young <sean@mess.org>
To: Patrick Zacharias <littlefighter19@web.de>
Cc: linux-media@vger.kernel.org
Subject: Re: mceusb: No keypresses on Formosa Infrared Receiver
Date: Mon, 20 Jan 2025 09:26:50 +0000	[thread overview]
Message-ID: <Z44W2kpjTpVvsrva@gofer.mess.org> (raw)
In-Reply-To: <f609b2e2-2c7f-4fcc-8f55-4b1c1f0e3671@web.de>

Hi Patrick,

On Sun, Jan 19, 2025 at 05:34:18PM +0100, Patrick Zacharias wrote:
> Hello there,
> 
> while using the Formos Infrared Receiver (147a:e016), I've noticed, that
> it won't stop blinking and doesn't register any presses.
> This issue appears to have been present since 2019,
> according to a thread on a German VDR forum.

That's interesting, mind sharing a link to the forum discussion please.

Also what does the device look like, it would be useful to get it and
test it myself if possible.

> And appears to be a regression, as according to that thread it used to
> work with their software
> (yavdr-0.6.2, which appears to based on kernel 3.13.0).

A git bisect would be useful.

> I've tried this on 5.16-rc2 (mainline on an X86 machine) and with
> 6.6.62+rpt-rpi-v8 from the latest Raspberry Pi OS.
> 
> I've analyzed a PCAP dump from a Windows 7 machine to see where the
> initialization differs and noticed,
> that an undocumented byte 0xF4 is being sent, after DEVICE_RESUME and
> G_REVISION (which are both sent in one packet).

You mean during device probe?

> By unbinding the driver, manually sending 0xF4 to the device and
> rebinding the driver, I'm able to workaround this issue.
> The blinking is gone and keypresses are now received. (Except for the OK
> key).
> 
> No further testing has been done.
> 
> I'm willing to provide PCAP traces, if of interest.

Yes please :)

Thanks,

Sean

  reply	other threads:[~2025-01-20  9:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-19 16:34 mceusb: No keypresses on Formosa Infrared Receiver Patrick Zacharias
2025-01-20  9:26 ` Sean Young [this message]
2025-01-20 23:46   ` Patrick Zacharias

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=Z44W2kpjTpVvsrva@gofer.mess.org \
    --to=sean@mess.org \
    --cc=linux-media@vger.kernel.org \
    --cc=littlefighter19@web.de \
    /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