From: Takashi Iwai <tiwai@suse.de>
To: bbennetts@blueyonder.co.uk
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Bug 000384 & debugging ALSA drivers.
Date: Mon, 02 Aug 2004 12:46:29 +0200 [thread overview]
Message-ID: <s5h6581u8ai.wl@alsa2.suse.de> (raw)
In-Reply-To: <5B596E67A1B90F48A466D8DF19E1F49703713CF2@ECOWV06M.Telewest.Internal>
At Fri, 30 Jul 2004 12:04:22 +0100,
<bbennetts@blueyonder.co.uk> wrote:
>
> Hi all,
>
> I was considering trying to debug the above problem in the ymfpci
> driver. However, I have never had to work on a driver before and so
> was wondering if anyone had any tips/suggestions on where to start
> (e.g. easiest way to debug the kernel etc) also any known stumbling
> blocks to look out for. If there's a good doc on the web that'd also
> be a big help.
First of all, it'd be better to read a linux device driver book.
A good one is by Alessandro Rubini.
The easiest way for debugging the kernel is traditional - adding
printk() in some points :)
I guess some register initializations are missing, so comparing the
register dumps between ALSA and OSS drivers might help.
(Or PCI register for legacy setting?)
Takashi
-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
prev parent reply other threads:[~2004-08-02 10:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-30 11:04 Bug 000384 & debugging ALSA drivers bbennetts
2004-08-02 10:46 ` Takashi Iwai [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=s5h6581u8ai.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=bbennetts@blueyonder.co.uk \
/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.