From: Takashi Iwai Subject: Re: atiixp: Problems making it work on SB400 Date: Mon, 27 Jun 2005 16:18:02 +0200 Message-ID: References: <20050624165908.GL19928@sunbeam.de.gnumonks.org> <20050624201652.GO19928@sunbeam.de.gnumonks.org> Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Return-path: In-Reply-To: <20050624201652.GO19928@sunbeam.de.gnumonks.org> Sender: alsa-devel-admin@lists.sourceforge.net Errors-To: alsa-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: Harald Welte Cc: alsa-devel@lists.sourceforge.net List-Id: alsa-devel@alsa-project.org At Fri, 24 Jun 2005 22:16:52 +0200, Harald Welte wrote: > > Hi Takashi! > > On Fri, Jun 24, 2005 at 07:47:42PM +0200, Takashi Iwai wrote: > > After a quick look at your information, I couldn't find anything > > wrong. The ac97 register values look OK (compared with ALC658 > > datasheet). > > Yes, I meanwhile obtained the datasheet, too (and played with GPIO > output and EAPD bits, but at no success). > > > Just to be sure, could you install alsa-driver-1.0.9b? > > I tried that, too (forgot to mention it in my initial mail. > > > There have been some bug reports with ATIIXP-laptop, and interestingly > > someone reported that it was fixed by disabling ACPI. But, his case > > was only for the speaker output, so not 100% identical with your > > case. > > For some strange reason, the headphone output now works. I don't really > know what I did different from my first tries where it wasn't working. > > So it seems like I'm observing the same bug. Yes, it sounds so... > Booting with acpi=off didn't change the behaviour, and the BIOS config > is so stripped-down that it has no option to disable ACPI. OK, then the report might be a false positive. > The only thing that I could find was that the atiixp (not ac97) > registers 0x10 and 0x14 change when inserting/removing a plug into the > headphone jack. Unfortunately there is no public datasheed for the > SB400 :( The reg 0x10 is the register for reading an ac97 register value. Hence it's volatile. The reg 0x14 is the read-only register indicating which ac97 slots (3-12, corresponding bit 0-9) are enabled for the next frame. So, this looks also irrelevant, too. Sorry, currently I have no more clue. I'll try to ask ATI guys. Takashi ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click