From: "Frank Schäfer" <fschaefer.oss@googlemail.com>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: Theodore Kilgore <kilgota@banach.math.auburn.edu>,
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: Wed, 20 Feb 2013 19:23:24 +0100 [thread overview]
Message-ID: <5125149C.6030208@googlemail.com> (raw)
In-Reply-To: <20130220075134.4d07213f@redhat.com>
<snip>
Am 20.02.2013 11:51, schrieb Mauro Carvalho Chehab:
> Em Tue, 19 Feb 2013 23:09:16 -0600 (CST)
> Theodore Kilgore <kilgota@banach.math.auburn.edu> escreveu:
>
>> On Tue, 19 Feb 2013, Mauro Carvalho Chehab wrote:
>>
>>>> So even if you are are right and the Empia reference design uses an EMP202,
>>>> EM2860_BOARD_SAA711X_REFERENCE_DESIGN might work for devices with other
>>>> AC97-ICs, too.
>>> The vast majority of devices use emp202. There are very few ones using
>>> different models.
>>>
>>> The proposal here is to add a third hint code, that would distinguish
>>> the devices based on the ac97 ID.
>>>
>>>> We should also expect manufacturers to switch between them whenever they
>>>> want (e.g. because of price changes).
>>> Yes, and then we'll need other entries at the hint table.
>>>
>>> Regards
>>> Mauro
>> I see the dilemma. Devices which are not uniquely identifiable. Mauro is
>> right in pinpointing the problem, and he is also right that one can not
>> expect the manufacturers to pay any attention. Mauro is also absolutely
>> right that it is not good to break what works already for some people,
>> hoping to please some others who are presently unhappy. A better solution
>> needs to be found.
>>
>> Could I make a suggestion?
>>
>> Sometimes it is possible to find some undocumented way to identify
>> uniquely which one of two devices you have.
> The hardware is identical, except for the audio decoder. Both devices have
> only 3 chips on it: the em2860 chip, an saa7113 video decoder and the ac97
> audio mixer, that it is different on each device.
>
> One board comes with an ac97 chip ID=0xffffffff [1](emp202, found on the
> reference design and clones). The other one comes with an ac97 chip
> with ID=0x414c4761 (a Realtek ALC653, only found so far on EasyCap DC-60).
>
> Btw, the issue between them is because of the different mixers found:
> the mixer channel used by the DC-60 is different than the mixer channel
> used by the reference design. At the reference design, the audio
> channel is EM28XX_AMUX_VIDEO. At DC-60, it is EM28XX_AMUX_LINE_IN.
Now you got it.
The relevant difference is the _channel_configuration_, not the used
AC97 IC manufacturer+model.
> I can't think on any other way do distinguish between them except by
> checking if the audio decoder matches the expected one.
>
> Adding a logic for such check is simple enough, as the probing logic already
> contains the needed bits for it.
I'm not convinced, for the following reasons:
You can't infer from the usage of a particular AC97 IC how the device is
wired internally / which channel configuration it uses.
We also can't assume a fixed binding between a particular AC97 IC and a
product/board.
So _if_ we really decide to leave the conservative path and take the
risk of regressions for the sake of fixing other devices,
we should at least be sure that we fix more devices than we break. (Even
then it still sucks !)
Regards,
Frank
> [1] There is a variant of emp202 at address 0x83847650.
>
> Regards,
> Mauro
next prev parent reply other threads:[~2013-02-20 18:22 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 [this message]
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=5125149C.6030208@googlemail.com \
--to=fschaefer.oss@googlemail.com \
--cc=dheitmueller@kernellabs.com \
--cc=goldcove@gmail.com \
--cc=kilgota@banach.math.auburn.edu \
--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).