From: "Frank Schäfer" <fschaefer.oss@googlemail.com>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: Devin Heitmueller <dheitmueller@kernellabs.com>,
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 19:45:29 +0100 [thread overview]
Message-ID: <5123C849.6080207@googlemail.com> (raw)
In-Reply-To: <20130219153024.6f468d43@redhat.com>
Am 19.02.2013 19:30, schrieb Mauro Carvalho Chehab:
> Em Tue, 19 Feb 2013 17:47:28 +0100
> Frank Schäfer <fschaefer.oss@googlemail.com> escreveu:
>
>> Am 18.02.2013 23:36, schrieb Mr Goldcove:
>>> I've only tried composite video input.
>>> The video/ audio output is good.
>>>
>>> It has the following input:
>>> RCA stereo sound
>>> RCA video
>>> S-video
>>>
>>> It has no push button but has a green led which illuminates when the
>>> device is in use.
>>>
>>>
>>> On 18. feb. 2013 22:25, Frank Schäfer wrote:
>>>> 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
>> After thinking about this for some minutes:
>> The easiest soulution would be, to add .amux = EM28XX_AMUX_LINE_IN lines
>> to input definitions of board EM2860_BOARD_SAA711X_REFERENCE_DESIGN.
>> No additional code lines (check for audio support etc.) would be needed
>> and (as side effect) board EM2860_BOARD_EASYCAP would become obsolete.
>>
>> The last modification of board EM2860_BOARD_SAA711X_REFERENCE_DESIGN was
>> commit 3ed58baf5db4eab553803916a990a3dbca4dc611 from Devin.
>> The commit message says
>>
>> "The device provides the audio through a pass-thru cable, so we don't need
>> an actual audio capture profile (neither the K-World device nor the
>> Pointnix
>> have an onboard audio decoder)"
>>
>> Changing the .amux settings doesn't cause any trouble for devices
>> without audio support
>> (there is actually no way to define _no_ amux, without this line in the
>> input definition .amux is 0 = EM28XX_AMUX_VIDEO).
>>
>> BUT: as we are talking about devices with generic USB IDs, we don't (and
>> will never) know about all other existing devices.
>> There _might_ be some unknown devices with audio support, which are
>> working silently with the current audio settings for board
>> EM2860_BOARD_SAA711X_REFERENCE_DESIGN.
>>
>> OTOH: if we keep the two separate boards and switch from board
>> EM2860_BOARD_SAA711X_REFERENCE_DESIGN to board EM2860_BOARD_EASYCAP when
>> the device has audio support,
>> the same shit can happen.
>>
>> Thoughts ?
>>
>> Does anyone know how the Empia-driver handles devices with generic IDs ?
>> Do you think we can assume their driver uses a single reference board
>> design for the detected combination of USB-ID and subdevices ?
>>
> I don't like the idea of merging those two entries. As far as I remember
> there are devices that works out of the box with
> EM2860_BOARD_SAA711X_REFERENCE_DESIGN. A change like that can break
> the driver for them.
As described above, there is a good chance to break devices with both
solutions.
What's your suggestion ? ;-)
Regards,
Frank
> Regards,
> Mauro
next prev parent reply other threads:[~2013-02-19 18:44 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 [this message]
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=5123C849.6080207@googlemail.com \
--to=fschaefer.oss@googlemail.com \
--cc=dheitmueller@kernellabs.com \
--cc=goldcove@gmail.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;
as well as URLs for NNTP newsgroup(s).