Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: kasper@303.nu
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: es18xx - 1869 not working, debugging ALSA drivers
Date: Thu, 28 Nov 2002 18:22:05 +0100	[thread overview]
Message-ID: <s5hel95zk1u.wl@alsa2.suse.de> (raw)
In-Reply-To: <200211052033.16712.kasper@303.nu>

At Tue, 5 Nov 2002 20:33:16 +0100,
kasper@303.nu wrote:
> 
> Hi,
> 
> I've been trying to get ALSA running on my Compaq Armada 3500 for quite a 
> while now. The soundchip is a es1869, which is supposed to be supported by 
> the es18xx driver. It only works 1 out of 10 times though - and I figured out 
> when it works and when it doesn't... But that didn't help me much until now, 
> I tried to force it to always use the working mode, but that didn't work 
> out...
> 
> The OSS driver is working properly, but I use the Soundblaster driver, which 
> is only half-duplex, and in fact, it's a different mode of the soundchip.

i've seen this on my colleague's laptop.
it seems that the second DAC (which is used for the playback) doesn't
work although it looks as if initialized properly.

perhaps an easy solution is to make a module option to make the driver
work as half-duplex.



> I've been trying to debug the driver, but it's not really my thing... Maybe 
> there are some handy tricks to debug ALSA drivers? Or is it just:
> 1) change the source
> 2) compile the source
> 3) see if it works (by loading the module.. and playing some audio)
> 4) if it doesn't work restart with 1)
> 
> Are there tools to control soundchips without using this laborious cycle? Some 
> kind of framework to check out the stuff that is written in the chip's 
> datasheet?

i'd love to have such a tool :)

btw, if you need to access only i/o ports, then even a user program
can do.  it would be easier than recompiling the driver.


Takashi


-------------------------------------------------------
This SF.net email is sponsored by: Get the new Palm Tungsten T 
handheld. Power & Color in a compact size! 
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en

  parent reply	other threads:[~2002-11-28 17:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-05 19:33 es18xx - 1869 not working, debugging ALSA drivers kasper
2002-11-05 21:56 ` Benny Sjostrand
2002-11-28 17:22 ` Takashi Iwai [this message]
2002-12-02 13:34   ` Takashi Iwai

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=s5hel95zk1u.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=kasper@303.nu \
    /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