From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takashi Iwai Subject: Re: Bug 000384 & debugging ALSA drivers. Date: Mon, 02 Aug 2004 12:46:29 +0200 Sender: alsa-devel-admin@lists.sourceforge.net Message-ID: References: <5B596E67A1B90F48A466D8DF19E1F49703713CF2@ECOWV06M.Telewest.Internal> Mime-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII Return-path: In-Reply-To: <5B596E67A1B90F48A466D8DF19E1F49703713CF2@ECOWV06M.Telewest.Internal> Errors-To: alsa-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: bbennetts@blueyonder.co.uk Cc: alsa-devel@lists.sourceforge.net List-Id: alsa-devel@alsa-project.org At Fri, 30 Jul 2004 12:04:22 +0100, 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