public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: salvador <salvador@inti.gov.ar>
To: Raul Sanchez Sanchez <raul@dif.um.es>
Cc: Paul Lorenz <p1orenz@yahoo.com>,
	Jeremy Lumbroso <j.lumbroso@noos.fr>,
	ignacio@adesx.com, rubio@adesx.com,
	Jorge Carminati <jcarminati@yahoo.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Driver via ac97 sound problem (VT82C686) Compaq Presario 700
Date: Thu, 17 Jan 2002 18:06:03 -0300	[thread overview]
Message-ID: <3C473CBB.47EFBED8@inti.gov.ar> (raw)
In-Reply-To: <20020114194209.90225.qmail@web20905.mail.yahoo.com>  <3C4342DA.5D19601A@inti.gov.ar> <1011045793.1847.3.camel@raul>  <3C441F7E.FD8A345C@inti.gov.ar> <1011100904.535.2.camel@raul>  <3C448071.7109C9E5@inti.gov.ar> <1011137857.504.16.camel@raul>  <3C459995.A8EF423A@inti.gov.ar> <1011253737.502.22.camel@raul>

Raul Sanchez Sanchez wrote:

>         But my question is, later i set up 1886 chip, does via inicialization
> change my configuration of it?

Try putting some printk in the function that sets the codec registers.

> If i try to print all the register of the
> 1886 in via_card_init_proc it fails :( and i can't be sure that via code
> doesn't change them.

No if the routine to write the registers isn't called *and* the initialization
doesn't reset the codec.
The first can be verified with printks, for the second examine the code. But
via_init_one is the one to check, it calls all the initializations.

> As you can see, the register are well written in ad1886, so this are my
> question,
> ---- Does via code inicialization change any value of ad1886?
> ---- Is possible that ad1886 works fine and the problem were with via
> chipset?

Jeff Garzik should know better ;-)
The only strange thing is the code is for the A version of the chip (desktop?)
and you have the B version (mobile?).
I got the 82C686A data sheet, but not the one for 82C686B.

SET

--
Salvador Eduardo Tropea (SET). (Electronics Engineer)
Visit my home page: http://welcome.to/SetSoft or
http://www.geocities.com/SiliconValley/Vista/6552/
Alternative e-mail: set@computer.org set@ieee.org
Address: Curapaligue 2124, Caseros, 3 de Febrero
Buenos Aires, (1678), ARGENTINA Phone: +(5411) 4759 0013




      reply	other threads:[~2002-01-17 21:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20020114194209.90225.qmail@web20905.mail.yahoo.com>
     [not found] ` <3C4342DA.5D19601A@inti.gov.ar>
     [not found]   ` <1011045793.1847.3.camel@raul>
     [not found]     ` <3C441F7E.FD8A345C@inti.gov.ar>
     [not found]       ` <1011100904.535.2.camel@raul>
     [not found]         ` <3C448071.7109C9E5@inti.gov.ar>
     [not found]           ` <1011137857.504.16.camel@raul>
     [not found]             ` <3C459995.A8EF423A@inti.gov.ar>
2002-01-17  7:48               ` Driver via ac97 sound problem (VT82C686) Compaq Presario 700 Raul Sanchez Sanchez
2002-01-17 21:06                 ` salvador [this message]

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=3C473CBB.47EFBED8@inti.gov.ar \
    --to=salvador@inti.gov.ar \
    --cc=ignacio@adesx.com \
    --cc=j.lumbroso@noos.fr \
    --cc=jcarminati@yahoo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=p1orenz@yahoo.com \
    --cc=raul@dif.um.es \
    --cc=rubio@adesx.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