From: "Frank Schäfer" <fschaefer.oss@googlemail.com>
To: Mr Goldcove <goldcove@gmail.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: Wrongly identified easycap em28xx
Date: Mon, 18 Feb 2013 22:25:01 +0100 [thread overview]
Message-ID: <51229C2D.8060700@googlemail.com> (raw)
In-Reply-To: <512294CA.3050401@gmail.com>
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...
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
>
> **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
>
> **logs**
> [ 5567.367883] em28xx: New device @ 480 Mbps (eb1a:2861, interface 0,
> class 0)
> [ 5567.367985] em28xx #0: chip ID is em2860
> [ 5567.380645] IR MCE Keyboard/mouse protocol handler initialized
> [ 5567.384202] lirc_dev: IR Remote Control driver registered, major 249
> [ 5567.385468] IR LIRC bridge handler initialized
> [ 5567.460386] em28xx #0: board has no eeprom
> [ 5567.534612] em28xx #0: found i2c device @ 0x4a [saa7113h]
> [ 5567.568303] em28xx #0: Your board has no unique USB ID.
> [ 5567.568308] em28xx #0: A hint were successfully done, based on i2c
> devicelist hash.
> [ 5567.568312] em28xx #0: This method is not 100% failproof.
> [ 5567.568314] em28xx #0: If the board were missdetected, please email
> this log to:
> [ 5567.568317] em28xx #0: V4L Mailing List
> <linux-media@vger.kernel.org>
> [ 5567.568321] em28xx #0: Board detected as EM2860/SAA711X Reference Design
> [ 5567.647433] em28xx #0: Identified as EM2860/SAA711X Reference Design
> (card=19)
> [ 5567.647438] em28xx #0: Registering snapshot button...
> [ 5567.647531] input: em28xx snapshot button as
> /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/input/input11
> [ 5568.019310] saa7115 15-0025: saa7113 found (1f7113d0e100000) @ 0x4a
> (em28xx #0)
> [ 5568.789385] em28xx #0: Config register raw data: 0x10
> [ 5568.813055] em28xx #0: AC97 vendor ID = 0x414c4761
> [ 5568.825074] em28xx #0: AC97 features = 0x0000
> [ 5568.825078] em28xx #0: Unknown AC97 audio processor detected!
> [ 5569.284137] em28xx #0: v4l2 driver version 0.1.3
> [ 5570.305831] em28xx #0: V4L2 video device registered as video1
> [ 5570.305835] em28xx #0: V4L2 VBI device registered as vbi0
> [ 5570.305862] em28xx audio device (eb1a:2861): interface 1, class 1
> [ 5570.305877] em28xx audio device (eb1a:2861): interface 2, class 1
> [ 5570.305906] usbcore: registered new interface driver em28xx
> [ 5570.305909] em28xx driver loaded
> [ 5570.392917] usbcore: registered new interface driver snd-usb-audio
> [ 7903.785365] em28xx #0: vidioc_s_fmt_vid_cap queue busy
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-02-18 21:24 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 [this message]
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
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=51229C2D.8060700@googlemail.com \
--to=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).