public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Lucian Onicescu <lucian.onicescu@gmail.com>
To: linux-media@vger.kernel.org
Subject: [Request] Add USB ID 2040:8360 for Hauppauge WinTV-HVR-935 (media cx231xx)
Date: Fri, 13 Feb 2026 21:57:30 +0200	[thread overview]
Message-ID: <CALbYB1O79OnqKMF--HWVx-nuKtYKJbE+Ux=yK_45HDb4oujQyA@mail.gmail.com> (raw)

The Hauppauge WinTV-HVR-935 HD stick is supported as 2040:b151
(CX231XX_BOARD_HAUPPAUGE_935C).
Some units report USB id 2040:8360 with product string "HVR-935 Audio"
and are not bound by cx231xx, so no DVB adapter is created.

Please consider adding 2040:8360 to the cx231xx_id_table with the same
driver_info as 0xb151 so these devices work without out-of-tree
patches.

How the ID was obtained (Debian, kernel 6.1.0-40-amd64):

  $ lsusb -d 2040:8360
  Bus 001 Device 006: ID 2040:8360 Hauppauge HVR-935 Audio

  $ lsusb -t | grep -A3 "Port 3"
|__ Port 3: Dev 6, If 2, Class=Audio, Driver=snd-usb-audio, 480M
|__ Port 3: Dev 6, If 0, Class=Vendor Specific Class, Driver=, 480M
|__ Port 3: Dev 6, If 1, Class=Audio, Driver=snd-usb-audio, 480M

Interface 0 (Vendor Specific) has no driver; the stock cx231xx module
has no 2040:8360
in its alias table.

Suggested patch:

--- a/drivers/media/usb/cx231xx/cx231xx-cards.c
+++ b/drivers/media/usb/cx231xx/cx231xx-cards.c
@@ -1026,6 +1026,8 @@ struct usb_device_id cx231xx_id_table[] = {
  {USB_DEVICE(0x2040, 0xb151),
  .driver_info = CX231XX_BOARD_HAUPPAUGE_935C},
+ {USB_DEVICE(0x2040, 0x8360),
+ .driver_info = CX231XX_BOARD_HAUPPAUGE_935C},
  {USB_DEVICE(0x2040, 0xb150),
  .driver_info = CX231XX_BOARD_HAUPPAUGE_975},
  {USB_DEVICE(0x2040, 0xb130),

Kind regards,
Lucian Onicescu

             reply	other threads:[~2026-02-13 19:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-13 19:57 Lucian Onicescu [this message]
2026-03-23 19:46 ` [Request] Add USB ID 2040:8360 for Hauppauge WinTV-HVR-935 (media cx231xx) Bradford Love

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='CALbYB1O79OnqKMF--HWVx-nuKtYKJbE+Ux=yK_45HDb4oujQyA@mail.gmail.com' \
    --to=lucian.onicescu@gmail.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