All of lore.kernel.org
 help / color / mirror / Atom feed
From: Apostolos Dimitromanolakis <apostolos@aei.ca>
To: Giuliano Pochini <pochini@shiny.it>
Cc: Alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: a lot of different cards and controls
Date: Mon, 22 Mar 2004 23:05:11 -0500	[thread overview]
Message-ID: <405FB777.1090908@aei.ca> (raw)
In-Reply-To: <20040322233928.60245c51.pochini@shiny.it>


I believe better structure should be the way to go. And since you're the 
one writing the drivers it is better if you follow the way you find it 
more reasonable and better for other people to understand.


Giuliano Pochini wrote:

>My driver is almost complete and I'm working to make it acceptable for
>inclusion in alsa-driver. It drives 8 different cards and it raises some
>problems. The main file is echoaudio.c and is contains all the control
>interfaces of all cards. It registers only the controls a card has at
>runtime, so there is some useless bloat for some cards. It's not very much
>because the lowlevel functions are defined in <card>Dsp.c and they are just
>empty functions if the card hasn't that feature. I wonder if this is ok.
>Otherwise I could split echoaudio.c into smaller peices and create several
>echoaudio_<card>.c files that contain something like this:
>
>#include "mixer_ctl.c"
>#include "inputclock_ctl.c"
>...
>#include "echoaudio_main.c"
>
>So it compiles only the parts that are really needed, at the cost of having
>a lot more files and a bit less clear structure. What is the preferred
>method ?
>
>
>
>--
>Giuliano.
>
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by: IBM Linux Tutorials
>Free Linux tutorial presented by Daniel Robbins, President and CEO of
>GenToo technologies. Learn everything from fundamentals to system
>administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
>_______________________________________________
>Alsa-devel mailing list
>Alsa-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/alsa-devel
>
>
>  
>



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click

      reply	other threads:[~2004-03-23  4:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-22 22:39 a lot of different cards and controls Giuliano Pochini
2004-03-23  4:05 ` Apostolos Dimitromanolakis [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=405FB777.1090908@aei.ca \
    --to=apostolos@aei.ca \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=pochini@shiny.it \
    /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.