All of lore.kernel.org
 help / color / mirror / Atom feed
From: Abramo Bagnara <abramo@alsa-project.org>
To: Paul Davis <pbd@op.net>
Cc: Takashi Iwai <tiwai@suse.de>, Jaroslav Kysela <perex@suse.cz>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: how to define a 2-index control element?
Date: Wed, 08 May 2002 00:06:20 +0200	[thread overview]
Message-ID: <3CD84FDC.1056ACA1@alsa-project.org> (raw)
In-Reply-To: 200205071717.g47HH3D25608@post2.fast.net

Paul Davis wrote:
> 
> >> If someone has hardware with 1400+ controls, than memory allocation issue
> >> is out of question. I wrote that we can optimize current code - add some
> >> hash tables for faster lookups for example.
> >
> >well, about 200kB is not so big nowadays :)
> >
> >i thought the hardware doesn't need allocate 1400 controls - the
> >controls are identical but have different indices.
> >in such a case, the indexed-access would be most straightforward.
> >no hash, no list.
> 
> precisely. in fact, there are:
> 
>            1456 mixer controls
>            52   RMS meters
>            80   peak meters
> 
> for the mixer controls, they form a matrix that is accessed by
> index. for the meters, they form unidimensional arrays that are also
> accessed by index.
> 
> i think any talk of allocating 1 control per "semantic control" is
> crazy. its clear that these controls should be accessed as a matrix
> type. they were designed by the h/w people as a matrix, and its been
> ALSA's policy to have the kernel API mirror h/w designs and
> capabilities.

Sorry to say that, but I think this is a nonsense.

Many cards have element organized in register with an index (you might
say an "array"), but this is definitely not a reason to implement it in
a different way.

We have well designed control keys (id) and I don't see any reason to
change something that's perfectly suitable (without any compromise) for
the job.

We have the sane association one control / one value and just because
this card has many controls, you seems to wish to go toward a different
(IMO insane and confusing) solution.

Consider that independently from how you represent the data this card
will ever have many controls (i.e. many values to show/change).

I definitely don't see your point, sorry.

-- 
Abramo Bagnara                       mailto:abramo@alsa-project.org

Opera Unica                          Phone: +39.546.656023
Via Emilia Interna, 140
48014 Castel Bolognese (RA) - Italy

ALSA project               http://www.alsa-project.org
It sounds good!

_______________________________________________________________

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: bandwidth@sourceforge.net

  reply	other threads:[~2002-05-07 22:06 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-04 12:45 how to define a 2-index control element? Paul Davis
2002-05-04 13:18 ` Abramo Bagnara
2002-05-05 13:48   ` Paul Davis
2002-05-05 15:50     ` Jaroslav Kysela
2002-05-06  1:32       ` Paul Davis
2002-05-06  6:46         ` Jaroslav Kysela
2002-05-06 11:22           ` Paul Davis
2002-05-06 11:44             ` Jaroslav Kysela
2002-05-06 12:03         ` Takashi Iwai
2002-05-06 12:19           ` Abramo Bagnara
2002-05-06 12:53             ` Takashi Iwai
2002-05-06 19:11               ` Abramo Bagnara
2002-05-07  9:29                 ` Takashi Iwai
2002-05-07  9:55                   ` Jaroslav Kysela
2002-05-07 10:34                     ` Takashi Iwai
2002-05-07 17:17                       ` Paul Davis
2002-05-07 22:06                         ` Abramo Bagnara [this message]
2002-05-08  0:00                           ` Paul Davis
     [not found] <20020508000005.EB5AC59D35D@kerberos.suse.cz>
2002-05-08  7:52 ` Jaroslav Kysela
2002-05-08  9:52   ` 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=3CD84FDC.1056ACA1@alsa-project.org \
    --to=abramo@alsa-project.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=pbd@op.net \
    --cc=perex@suse.cz \
    --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.