From: "Frank Schäfer" <fschaefer.oss@googlemail.com>
To: "Michael ." <boycee_@hotmail.com>,
Linux Media Mailing List <linux-media@vger.kernel.org>
Cc: Mauro Carvalho Chehab <mchehab@redhat.com>,
Devin Heitmueller <dheitmueller@kernellabs.com>
Subject: Fwd: Device no longer handled by em28xx kernel drivers
Date: Tue, 23 Apr 2013 17:40:15 +0200 [thread overview]
Message-ID: <5176AB5F.1050901@googlemail.com> (raw)
In-Reply-To: <DUB118-W30802FB90E04796F1FBDE187CF0@phx.gbl>
(forwarding to the linux-media mailing list) (2nd try)
Am 18.04.2013 21:04, schrieb Michael .:
> Hi
>
> I hope you don't mind me contacting you directly.
Issues like this should always be discussed on the linux-media mailing
list, so please CC it in the future.
Neither I'm the em28xx maintainer nor do I know much about issues/things
that happened in the past.
> I have a USB device which I was surprised to find is no longer handled
> by the driver:
What does "no longer handled" mean ?
What was the last kernel that supported this device ?
>
> Bus 001 Device 004: ID 0ccd:0072 TerraTec Electronic GmbH Cinergy Hybrid T
>
> I believe the hardware is em28xx + zl10353 + xc5000 as I can see my
> precise hardware being detected by em28xx in dmesg output here:
Yes, according to http://linux.terratec.de/tv_en.html it uses em2882+xc5000.
>
> http://doc.ubuntu-fr.org/terratec_cinergy_xs
>
> As I understand there might have been two parallel drivers being
> developed.
I never heard of a second driver.
> I just wondered if there is any chance of this support being
> re-instated for this particular one?
> I am surprised to find that a device has gone from supported to
> unsupported!
I don't know. The em28xx driver is generally the right driver and it
already supports other devices with the xc5000 tuner.
If support for this device has really been removed a while ago, then
there must have been good reasons...
Mauro, Devin ?
Regards,
Frank
>
>
> Cheers,
>
> Michael.
next parent reply other threads:[~2013-04-23 15:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <DUB118-W3105CA5468C478D0494A7687CE0@phx.gbl>
[not found] ` <516EF48C.2080804@iki.fi>
[not found] ` <DUB118-W43501C44B9B252CC5A03DD87CE0@phx.gbl>
[not found] ` <DUB118-W30802FB90E04796F1FBDE187CF0@phx.gbl>
2013-04-23 15:40 ` Frank Schäfer [this message]
2013-04-23 16:27 ` Fwd: Device no longer handled by em28xx kernel drivers Mauro Carvalho Chehab
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=5176AB5F.1050901@googlemail.com \
--to=fschaefer.oss@googlemail.com \
--cc=boycee_@hotmail.com \
--cc=dheitmueller@kernellabs.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.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