From: Peter Schlaf <peter.schlaf@web.de>
To: linux-media@vger.kernel.org
Subject: Re: Probably a new board ID for em28xx: [1b80:e349]
Date: Wed, 30 Dec 2015 16:22:36 +0100 [thread overview]
Message-ID: <5683F6BC.2070005@web.de> (raw)
In-Reply-To: <567FC93D.7060602@web.de>
To whom it may concern...
Added this device to em28xx-cards.c and used
"EM2860_BOARD_HT_VIDBOX_NW03" as ID
because it's the only device listed there that has the same chips as my
hardware.
Recompiled the module and it works!
--- /usr/src/linux/drivers/media/usb/em28xx/em28xx-cards.c 2015-11-26
17:35:17.000000000 +0100
+++ em28xx-cards.c 2015-12-30 14:54:19.000000000 +0100
@@ -2475,6 +2475,8 @@ struct usb_device_id em28xx_id_table[] =
.driver_info = EM2861_BOARD_LEADTEK_VC100 },
{ USB_DEVICE(0xeb1a, 0x8179),
.driver_info =
EM28178_BOARD_TERRATEC_T2_STICK_HD },
+ { USB_DEVICE(0x1b80, 0xe349),
+ .driver_info = EM2860_BOARD_HT_VIDBOX_NW03 },
{ },
};
MODULE_DEVICE_TABLE(usb, em28xx_id_table);
prev parent reply other threads:[~2015-12-30 15:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-27 11:19 Probably a new board ID for em28xx: [1b80:e349] Peter Schlaf
2015-12-30 15:22 ` Peter Schlaf [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=5683F6BC.2070005@web.de \
--to=peter.schlaf@web.de \
--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).