From: "Frank Schäfer" <fschaefer.oss@googlemail.com>
To: oravecz@nytud.mta.hu
Cc: linux-media@vger.kernel.org
Subject: Re: HVR 900 (USB ID 2040:6500) no analogue sound reloaded
Date: Sun, 31 Aug 2014 17:07:00 +0200 [thread overview]
Message-ID: <54033A14.10309@googlemail.com> (raw)
In-Reply-To: <201408221903.s7MJ3IT28956@ny01.nytud.hu>
Am 22.08.2014 um 21:03 schrieb Oravecz Csaba:
> I reported this issue earlier but for some reason it went pretty much
> unnoticed. The essence is that with the newest em28xx drivers now present in
> 3.14 kernels (i'm on stock fedora 3.14.15-100.fc19.i686.PAE) I can't get
> analogue sound from this card.
>
> I see that the code snippet that produced this output in the pre 3.14 versions
>
> em2882/3 #0: Config register raw data: 0x50
> em2882/3 #0: AC97 vendor ID = 0xffffffff
> em2882/3 #0: AC97 features = 0x6a90
> em2882/3 #0: Empia 202 AC97 audio processor detected
>
> is still there in em28xx-core.c, however, there is nothing like that in
> current kernel logs so it seems that this part of the code is just skipped,
> which I tend to think is not the intended behaviour. I have not gone any
> further to investigate the issue, rather I've simply copied the 'old' em28xx
> directory over the current one in the latest source and compiled the drivers
> in this way and so got back the old em28xx version, which is working well in
> the current kernel as well.
>
> I don't consider this an optimal solution so
> I would very much appreciate any help in this issue.
>
> best,
> o.cs.
Thank you for reporting this issue.
I suspect reverting commit b99f0aadd3 "[media] em28xx: check if a device
has audio earlier" will resolve it.
Can you check that ?
Regards,
Frank
next prev parent reply other threads:[~2014-08-31 15:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-22 19:03 HVR 900 (USB ID 2040:6500) no analogue sound reloaded Oravecz Csaba
2014-08-31 15:07 ` Frank Schäfer [this message]
2014-09-01 7:31 ` Oravecz Csaba
2014-09-01 18:18 ` Frank Schäfer
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=54033A14.10309@googlemail.com \
--to=fschaefer.oss@googlemail.com \
--cc=linux-media@vger.kernel.org \
--cc=oravecz@nytud.mta.hu \
/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).