From: Antti Palosaari <crope@iki.fi>
To: "Frank Schäfer" <fschaefer.oss@googlemail.com>
Cc: linux-media@vger.kernel.org
Subject: Re: Mysterious USB device ID change on Hauppauge HVR-900 (em28xx)
Date: Fri, 23 Nov 2012 19:20:27 +0200 [thread overview]
Message-ID: <50AFB05B.6020209@iki.fi> (raw)
In-Reply-To: <50AFABDA.9050309@googlemail.com>
On 11/23/2012 07:01 PM, Frank Schäfer wrote:
> Hi,
>
> I've got a Hauppauge HVR-900 (65008/A1C0) today. First, the device
> showed up as USB device 7640:edc1 (even after several unplug - replug
> cycles), so I decided to add this VID:PID to the em28xx driver to see
> what happens.
> That worked fine, em2882/em2883, tuner xc2028/3028 etc. were detected
> properly.
> Later I noticed, that the device now shows up as 2040:6500, which is the
> expected ID for this device.
> Since then, the device maintains this ID. I also checked if Windows is
> involved, but it shows up with the same ID there.
>
> Does anyone have an idea what could have happened ???
> I wonder if we should add this ID to the em28xx driver...
em28xx chip reads USB ID from the external eeprom using I2C just after
it was powered. After USB ID is got it connects to the USB bus using
that ID. If there is no external eeprom it uses chipset default USB ID,
which is 0xeb1a as vendor ID and some other number defined for chip
model as device ID. In that case those wrong IDs seems to be total
garbage, which indicates there is some hardware problems when
communicating towards eeprom.
That method is not only Empia USB interface chips but almost all chipset
uses just similar method.
regard
Antti
--
http://palosaari.fi/
next prev parent reply other threads:[~2012-11-23 17:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-23 17:01 Mysterious USB device ID change on Hauppauge HVR-900 (em28xx) Frank Schäfer
2012-11-23 17:20 ` Antti Palosaari [this message]
2012-11-23 19:24 ` Frank Schäfer
2012-11-23 20:10 ` 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=50AFB05B.6020209@iki.fi \
--to=crope@iki.fi \
--cc=fschaefer.oss@googlemail.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