From: Takashi Iwai <tiwai@suse.de>
To: Cameron Hutchison <camh@xdna.net>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: ens1371/ac97 broken on my machine
Date: Thu, 22 May 2003 11:50:36 +0200 [thread overview]
Message-ID: <s5hznlfqphv.wl@alsa2.suse.de> (raw)
In-Reply-To: <20030522045314.GA24245@imladris>
At Thu, 22 May 2003 14:53:14 +1000,
Cameron Hutchison wrote:
>
> Once upon a time Takashi Iwai said...
> > At Wed, 21 May 2003 16:34:08 +1000,
> > Cameron Hutchison wrote:
> > >
> > > The driver for the ens1371 chipset no longer works on my laptop.
> > > It used to work in version 0.9.0rc3, but in version 0.9.2 and 0.93a, it
> > > no longer works. When I try to run alsamixer, I get the error "No mixer
> > > elems found"
> > >
> > > It seems that snd_ac97_read() does not read back the value 0x8a06 and
> > > never sets AC97_SCAP_AUDIO, which means the mixer elements never get
> > > created.
> >
> > i put a workaround code for ens1371 to avoid this.
> > can you try the cvs version?
>
> Ok. I tried it, but it didnt help. The problem is that AC97_SCAP_AUDIO
> never gets set, so the test you added doesn't do anything - the code
> path ends up being the same as before.
the bit is set in ens1370.c, so it should have been set.
but the change in ac97_codec.c is not prefect. i changed it again a
bit on cvs. could you update the tree?
Takashi
-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge
next prev parent reply other threads:[~2003-05-22 9:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-21 6:34 ens1371/ac97 broken on my machine Cameron Hutchison
2003-05-21 10:59 ` Takashi Iwai
[not found] ` <20030522045314.GA24245@imladris>
2003-05-22 9:50 ` Takashi Iwai [this message]
2003-06-16 4:47 ` Cameron Hutchison
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=s5hznlfqphv.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=camh@xdna.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.