From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: "Frank Schäfer" <fschaefer.oss@googlemail.com>
Cc: Mr Goldcove <goldcove@gmail.com>,
Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: Wrongly identified easycap em28xx
Date: Tue, 19 Feb 2013 10:06:14 -0300 [thread overview]
Message-ID: <20130219100614.508af9e2@redhat.com> (raw)
In-Reply-To: <51229C2D.8060700@googlemail.com>
Em Mon, 18 Feb 2013 22:25:01 +0100
Frank Schäfer <fschaefer.oss@googlemail.com> escreveu:
> Am 18.02.2013 21:53, schrieb Mr Goldcove:
> > "Easy Cap DC-60++"
> > Wrongly identified as card 19 "EM2860/SAA711X Reference Design",
> > resulting in no audio.
> > Works perfectly when using card 64 "Easy Cap Capture DC-60"
>
> Video inputs work fine, right ?
> Does this device has any buttons / LEDs ?
>
> The driver doesn't handle devices with generic IDs very well.
> In this case we can conclude from the USB PID that the device has audio
> support (which is actually the only difference to board
> EM2860_BOARD_SAA711X_REFERENCE_DESIGN).
> But I would like to think twice about it, because this kind of changes
> has very a high potential to cause regressions for other boards...
While em28xx driver tries to do its best to detect, devices without
EEPROM will always have issues, as there are lots of similar devices
with small differences on how they were wired up.
That's why em28xx has the "card" modprobe parameter.
Ok, it likely makes sense to add an additional hint based on has_audio.
>
> Regards,
> Frank
>
> >
> > **Interim solution**
> > load module (before inserting the EasyCap. I'm having trouble if the
> > module is loaded/unloaded with different cards...)
> > modprobe em28xx card=64
> > or
> > add "options em28xx card=64" to /etc/modprobe.d/local.conf
That is the right thing to do. It makes sense to have it documented at the
Wiki, in order to help others with similar boards.
Regards,
Mauro
> >
> > **hw info**
> > Bus 002 Device 005: ID eb1a:2861 eMPIA Technology, Inc.
> >
> > Chips:
> > Empia EM2860 P7JY8-011 201023-01AG
> > NXP SAA7113H
> > RMC ALC653 89G06K1 G909A
The driver could be detecting if Realtek alc653 is found, in order to
hint it as "EasyCap":
[ 5568.813055] em28xx #0: AC97 vendor ID = 0x414c4761
If I'm not mistaken, someone wrote at the ML that "EasyCap" is actually
just a generic name used by some Chinese companies to indicate a video
capture USB device. The fact is that there are EasyCap devices using
even completely different chipsets.
Cheers,
Mauro
prev parent reply other threads:[~2013-02-19 13:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 20:53 Wrongly identified easycap em28xx Mr Goldcove
2013-02-18 21:25 ` Frank Schäfer
2013-02-18 22:36 ` Mr Goldcove
2013-02-19 16:02 ` Frank Schäfer
2013-02-19 16:51 ` Mr Goldcove
2013-02-19 16:47 ` Frank Schäfer
2013-02-19 18:30 ` Mauro Carvalho Chehab
2013-02-19 18:45 ` Frank Schäfer
2013-02-19 18:53 ` Mauro Carvalho Chehab
2013-02-19 19:45 ` Frank Schäfer
2013-02-19 20:03 ` Mauro Carvalho Chehab
2013-02-19 22:14 ` Frank Schäfer
2013-02-19 22:42 ` Mauro Carvalho Chehab
2013-02-20 18:15 ` Frank Schäfer
2013-02-20 5:09 ` Theodore Kilgore
2013-02-20 10:49 ` Andy Walls
2013-02-20 10:51 ` Mauro Carvalho Chehab
2013-02-20 18:23 ` Frank Schäfer
2013-02-20 18:20 ` Frank Schäfer
2013-02-20 19:12 ` Mauro Carvalho Chehab
2013-02-21 18:39 ` Frank Schäfer
2013-02-19 13:06 ` Mauro Carvalho Chehab [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=20130219100614.508af9e2@redhat.com \
--to=mchehab@redhat.com \
--cc=fschaefer.oss@googlemail.com \
--cc=goldcove@gmail.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;
as well as URLs for NNTP newsgroup(s).