From: Oliver Schinagl <oliver@schinagl.nl>
To: linux-media@vger.kernel.org
Subject: USB ID for Asus U3100MINI Plus DVB-T tuner
Date: Mon, 20 Feb 2012 20:24:33 +0100 [thread overview]
Message-ID: <4F429DF1.3010500@schinagl.nl> (raw)
[-- Attachment #1: Type: text/plain, Size: 2389 bytes --]
Hi,
i'm partial writer of
http://www.linuxtv.org/wiki/index.php/Asus_U3100_Mini_plus_DVB-T and
host the mentioned git repository.
I have noticed that the Asus U3100Mini plus dvb-t tuner still does not
have it's USB ID added to usb-ids.h and thus supply this patch.
The DVB-T tuner uses the "Afa Technologies Inc. AF9035A USB Device" and
has an USB ID of 0b05:1779.
Btw, my /usr/share/misc/usb.ids does list this device properly.
Bus 002 Device 002: ID 0b05:1779 ASUSTek Computer, Inc. My Cinema U3100
Mini Plus [AF9035A]
Also, what is afa's current status in supporting (or not) the af903a and
what specifications are required to piggy back the driver possibly ontop
of the previous afa drivers?
I know afa is 'working on it' as quited from the wiki:
"
For its part, Afatech does not want any of the above driver attempts to
make their way into the kernel, as none of them are very robust in terms
of chip support.
Instead, AFA has embarked upon the development of yet another OSS
driver, which will be generic in that it will be capable of supporting
the entire AF901x family as well as all possible device configurations
permitted. In addition to the expectation that it will be this driver
that is eventually adopted into the kernel, AFA have also signaled that
they intend provide continuous support (i.e. they will stay on as the
driver's maintainer).
Currently, this newest driver has reached a second round of testing in
AFA labs, but that has only been in conjunction (with some peripheral
manufacturers) with a few devices, and, as it stands, the code is still
not particularly generic (due to both the complexities of the chip
itself as well as those involved in getting the various device
configurations to work). So, as of yet, there currently isn't anything
for the end user to test. However, as soon things progress past this
stage, there will be something released for users to test. There is no
specific release timeframe set for this, but hopefully it will be soon,
as the chip manufacturer (as well as everybody else involved) is under
pressure, due to the large adoption of the chip by different peripheral
manufacturers (Avermedia, Terratec, Azurewave, DigitalNow, Pinnacle, as
well as some number of unbranded Chinese manufacturers too). In short, a
lot more devices based on this chipset are expected to materialize."
Oliver
[-- Attachment #2: asus_dvb-usb-ids.h.diff --]
[-- Type: text/x-patch, Size: 422 bytes --]
--- v4l/dvb-usb-ids.h 2011-10-24 09:10:05.000000000 +0200
+++ v4l/dvb-usb-ids.h_asus 2012-02-20 20:06:57.980979949 +0100
@@ -294,6 +294,7 @@
#define USB_PID_ASUS_U3000 0x171f
#define USB_PID_ASUS_U3000H 0x1736
#define USB_PID_ASUS_U3100 0x173f
+#define USB_PID_ASUS_U3100MINI_PLUS 0x1779
#define USB_PID_YUAN_EC372S 0x1edc
#define USB_PID_YUAN_STK7700PH 0x1f08
#define USB_PID_YUAN_PD378S 0x2edc
next reply other threads:[~2012-02-20 19:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-20 19:24 Oliver Schinagl [this message]
2012-03-08 14:23 ` USB ID for Asus U3100MINI Plus DVB-T tuner 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=4F429DF1.3010500@schinagl.nl \
--to=oliver@schinagl.nl \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.