From: Thomas Hollstegge <thomas.hollstegge@gmail.com>
To: Markus Rechberger <mrechberger@gmail.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [PATCH] [media] em28xx: support for Sundtek MediaTV Digital Home
Date: Fri, 5 May 2017 17:44:37 +0200 [thread overview]
Message-ID: <20170505154435.GA18161@googlemail.com> (raw)
In-Reply-To: <CA+O4pCJqqSqE_YFDM6unU8pvuVoRJijkNOv64AWD6CPdbxD5qA@mail.gmail.com>
Hi Markus,
Markus Rechberger <mrechberger@gmail.com> schrieb am Fri, 05. May 08:06:
> On Fri, May 5, 2017 at 6:21 AM, Thomas Hollstegge
> <thomas.hollstegge@gmail.com> wrote:
> > Sundtek MediaTV Digital Home is a rebranded MaxMedia UB425-TC with the
> > following components:
> >
> > USB bridge: Empia EM2874B
> > Demodulator: Micronas DRX 3913KA2
> > Tuner: NXP TDA18271HDC2
> >
>
> Not that it matters a lot anymore for those units however the USB ID
> is allocated for multiple different units, this patch will break some
> of them.
I searched the kernel sources for USB IDs but didn't find any mention.
So what exactly will break with this commit? Is there a better way to
detect different devices besides USB IDs?
> If you want to use that use the unit with this driver you're on your
> own and have to assign it via sysfs and usb/bind.
I did, and it works fine. However, it would be nice if the driver
supported the devices directly.
> It was a joint project many years ago before we also started to design
> and manufacture our own units.
Interesting, thanks for sharing this insight!
Cheers
Thomas
next prev parent reply other threads:[~2017-05-05 15:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-04 22:21 [PATCH] [media] em28xx: support for Sundtek MediaTV Digital Home Thomas Hollstegge
2017-05-05 0:06 ` Markus Rechberger
2017-05-05 15:44 ` Thomas Hollstegge [this message]
2017-05-05 16:33 ` Markus Rechberger
2017-05-05 19:50 ` Thomas Hollstegge
2017-05-06 6:53 ` Markus Rechberger
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=20170505154435.GA18161@googlemail.com \
--to=thomas.hollstegge@gmail.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=mrechberger@gmail.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;
as well as URLs for NNTP newsgroup(s).