Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rene Herman <rene.herman@keyaccess.nl>
To: Takashi Iwai <tiwai@suse.de>
Cc: Alsa-devel <alsa-devel@alsa-project.org>,
	Krzysztof Helt <krzysztof.h1@poczta.fm>,
	Massimo Piccioni <alsa@piccio.org>
Subject: Re: [REPOST] opti93x: conversion to use cs4231 library
Date: Thu, 07 Feb 2008 01:09:56 +0100	[thread overview]
Message-ID: <47AA4C54.80305@keyaccess.nl> (raw)
In-Reply-To: <47AA49AB.4060802@keyaccess.nl>

On 07-02-08 00:58, Rene Herman wrote:

> On 30-01-08 01:43, Rene Herman wrote:
> 
>> 931 and 933 work and 930 (a non-PnP chip) is being a royal pain in the 
>> ass again. With the new code, I haven't yet been able to get it to 
>> work -- no IRQ is firing. However, I also experienced this _once_ with 
>> the old driver so I'm not sure what's going on. When I now try to 
>> reproduce with the old one, I can't. Maybe a timing difference.
>>
>> Will need further testing -- I have no time in the next few days.
> 
> Hate it but will need to confirm that this is definitely a regression. OPTi
> 82C930A does not work with the cs4231-lib using driver, does work with the
> current driver. It loads, but gets no interrupts.
> 
> However, relevant -- "does work with the old driver" is conditional on 
> one accepting a definition of "does work" which includes "does not 
> produce any sound". OPTi 930 is a Non-PnP chip, and it seems it might 
> need the same kind of internal switching that the Non-PnP sound galaxies 
> need before the output circuitry is actually connected to the WSS part 
> and not the SB part.

(oh, by the way, that's not a hardware problem -- work fine under DOS)

> Given that for most people sound cards have producing sound as one of 
> their more important characteristics it not in fact doing such no doubt 
> means that this chip isn't used at _all_ by anyone. I have one, but I 
> can't say I've ever found another one either. Could've sworn I tested it 
> before and got it to work but not able to say with certainty either.
> 
> Massimo, do you remember if the driver was ever tested on a 930?
> 
> In any case, it works on 931 and 933, not 930. 931/3 are the chips 
> actually used. No opinion on just integrating this anyway. Debugging 930 
> is going to require some work and time.

Rene.

  reply	other threads:[~2008-02-07  0:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-26  9:44 [REPOST] opti93x: conversion to use cs4231 library Krzysztof Helt
2008-01-28 17:20 ` Takashi Iwai
2008-01-29  1:24   ` Rene Herman
2008-01-30  0:43     ` Rene Herman
2008-02-06 23:58       ` Rene Herman
2008-02-07  0:09         ` Rene Herman [this message]
2008-02-07  1:21         ` Massimo Piccioni
  -- strict thread matches above, loose matches on Subject: below --
2008-01-29  7:09 krzysztof.h1
2008-02-07  7:18 krzysztof.h1

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=47AA4C54.80305@keyaccess.nl \
    --to=rene.herman@keyaccess.nl \
    --cc=alsa-devel@alsa-project.org \
    --cc=alsa@piccio.org \
    --cc=krzysztof.h1@poczta.fm \
    --cc=tiwai@suse.de \
    /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