All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Kasparek Tomas <xkaspa06@stud.fee.vutbr.cz>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Where to find constants for snd_magic_cast()
Date: Fri, 22 Mar 2002 16:53:55 +0100	[thread overview]
Message-ID: <s5hit7oiooc.wl@alsa2.suse.de> (raw)
In-Reply-To: <Pine.BSF.4.44.0203221529500.80535-100000@fest.stud.fee.vutbr.cz>

At Fri, 22 Mar 2002 15:51:31 +0100 (CET),
Kasparek Tomas wrote:
> 
> Hi all,
> 
> Please, I tried to enable debugging for alsa-driver. For this I need to
> add my own constants for snd_magic_cast(). How are these constants
> construct and how this magic function works?
 
you can define the constant as you like, although a kind of rule can
be easily found by looking through the numbers in sndmagic.h :)
just add your new type and increment the number.

magic functions check whether the pointer is valid, i.e. really
allocated via snd_magic_kmalloc().  it's good for a void pointer,
which type can not be known at the compile time.

please note that the buffer allocated via snd_magic_kmalloc must be
released via snd_magic_kfree(), not usual kfree().

> What is actual status of kernel API documentation. Sources are commented
> poorly and there's no notice about kernel API documentation on web.

no, there is none, so far.

> There are rummors about some information unofficialy released - could you
> give me the direction, where to find these?

i'd like to know if really there is one ;)


ciao,

Takashi

_______________________________________________
Alsa-devel mailing list
Alsa-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-devel

      reply	other threads:[~2002-03-22 15:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-22 14:51 Where to find constants for snd_magic_cast() Kasparek Tomas
2002-03-22 15:53 ` 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=s5hit7oiooc.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=xkaspa06@stud.fee.vutbr.cz \
    /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.