Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Eliot Blennerhassett <bigblen@icqmail.com>
Cc: alsa-devel@lists.sourceforge.net, eliot@blennerhassett.gen.nz
Subject: Re: Environments for driver development.
Date: Fri, 16 May 2003 11:17:13 +0200	[thread overview]
Message-ID: <s5hsmrfdzdy.wl@alsa2.suse.de> (raw)
In-Reply-To: <20030515192318.16899.h003.c012.wm@mail.icqmail.com.criticalpath.net>

At Thu, 15 May 2003 19:23:17 -0700 (PDT),
Eliot Blennerhassett wrote:
> 
> Hello,
> 
> I'd like to know what kind of developement environment
> driver developers are using.
> 
> Currently I am just editing in xemacs, and using grep a
> lot to find where various structures, functiosn and so
> forth are defined.
> 
> Do you use an IDE, etags, doxygen etc?

some functions are described in kernel-doc (javadoc like) style in the
driver code.

> 
> I know that there is a Driver API document, but IMHO it
> is only half - it documents the functions, but not the
> data structures.   Are they documented anywhere?

did you take a look at my tutorial?

	http://www.alsa-project.org/~iwai/writing-an-alsa-driver

the source is found in alsa-kernel/Documentation/DocBook.


Takashi


-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com

      reply	other threads:[~2003-05-16  9:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-16  2:23 Environments for driver development Eliot Blennerhassett
2003-05-16  9:17 ` 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=s5hsmrfdzdy.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=bigblen@icqmail.com \
    --cc=eliot@blennerhassett.gen.nz \
    /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