All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: [PATCH] emu10k1: add per-voice PTR register dump to /proc entry
Date: Wed, 17 Nov 2004 12:51:29 -0500	[thread overview]
Message-ID: <1100713890.6930.26.camel@krustophenia.net> (raw)
In-Reply-To: <s5hlld0smj2.wl@alsa2.suse.de>

On Wed, 2004-11-17 at 13:11 +0100, Takashi Iwai wrote:
> At Sat, 13 Nov 2004 20:01:26 -0500,
> Lee Revell wrote:
> > 
> > Summary: This patch adds a register dump for each voice to the /proc
> > entry.  This functionality will be key for improving the voice allocator
> > for multichannel support.  Currently these all go in the main file; I
> > can split these into a file per voice if desired.
> 
> I feel it'd be better to create another proc file.  Not necessarily
> per voice, though.  The dump seems not matching with the current
> emu10k1 proc file contents.
> 

Hey, it looks like if I write routines to dump all registers, then
suspend/resume is halfway finished, right?

https://bugtrack.alsa-project.org/alsa-bug/view.php?id=227

Lee



-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8

  parent reply	other threads:[~2004-11-17 17:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-14  1:01 [PATCH] emu10k1: add per-voice PTR register dump to /proc entry Lee Revell
2004-11-17 12:11 ` Takashi Iwai
2004-11-17 16:31   ` Lee Revell
2004-11-18 13:22     ` Takashi Iwai
2004-11-19 22:38       ` Lee Revell
2004-11-20  0:10       ` Lee Revell
2004-11-22 10:40         ` Takashi Iwai
2004-11-17 17:51   ` Lee Revell [this message]
2004-11-18 13:21     ` 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=1100713890.6930.26.camel@krustophenia.net \
    --to=rlrevell@joe-job.com \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=tiwai@suse.de \
    /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.