All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benny Sjostrand <gorm@cucumelo.org>
To: kasper@303.nu
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: es18xx - 1869 not working, debugging ALSA drivers
Date: Tue, 05 Nov 2002 22:56:30 +0100	[thread overview]
Message-ID: <3DC83E8E.1000703@cucumelo.org> (raw)
In-Reply-To: 200211052033.16712.kasper@303.nu

>
>
>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)
>  
>
Yeah,.., I feel familiar with that method -:) I guess I'm not the only one
Probably you can add a point:
 3.5) If the computer totally freezes (course change to the source was 
very wrong and bad) restart computer, and go to 1) + (I hate ext2 
filesystems)

 I don't known any better method, maybe just yet another point:
1.5) review changes yet one more time and go back to 1 or 1.5 a couple 
of times
       to try prevent moment "3.5"

But, stuffs like the tool  "ksymoops", the alsa functions/macros:  
snd_assert(...),
snd_magic_cast(...), snd_printk(...), snd_printdd(...), etc. helps a lot!

/Benny





-------------------------------------------------------
This sf.net email is sponsored by: See the NEW Palm 
Tungsten T handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en

  reply	other threads:[~2002-11-05 21:56 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 [this message]
2002-11-28 17:22 ` Takashi Iwai
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=3DC83E8E.1000703@cucumelo.org \
    --to=gorm@cucumelo.org \
    --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 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.