Alsa-Devel Archive on 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>,
	James Courtier-Dutton <James@superbug.co.uk>
Subject: Re: [PATCH] emu10k1: add per-voice PTR register dump	to /proc entry
Date: Fri, 19 Nov 2004 19:10:24 -0500	[thread overview]
Message-ID: <1100909425.13712.50.camel@krustophenia.net> (raw)
In-Reply-To: <s5hmzxfqok5.wl@alsa2.suse.de>

On Thu, 2004-11-18 at 14:22 +0100, Takashi Iwai wrote:
> > 
> > Sure, will do.  One file per voice for the PTR registers (and one file
> > for FN0) might actually be most useful.  This way you can diff them.
> 
> Yes, that makes sense.
> 

OK regarding the previous message, I figured out how to create a
directory under the card root (just set S_IFDIR).  However there is no
way to create files under that directory because snd_card_proc_new makes
the following assumption (from alsa-kernel/core/info.c):

    852  *
    853  * The parent is assumed as card->proc_root.
    854  *

So, I think the API has to be modified to allow a parent to be
specified.

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-20  0:10 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 [this message]
2004-11-22 10:40         ` Takashi Iwai
2004-11-17 17:51   ` Lee Revell
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=1100909425.13712.50.camel@krustophenia.net \
    --to=rlrevell@joe-job.com \
    --cc=James@superbug.co.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox