From: Takashi Iwai <tiwai@suse.de>
To: Guilhem Tardy <guilhem_tardy@yahoo.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: snd_pcm_hardware_t NOT pre-initialized
Date: Fri, 06 Sep 2002 18:43:47 +0200 [thread overview]
Message-ID: <s5h8z2f1324.wl@alsa2.suse.de> (raw)
In-Reply-To: <20020906162801.82599.qmail@web11504.mail.yahoo.com>
At Fri, 6 Sep 2002 09:28:01 -0700 (PDT),
Guilhem Tardy wrote:
>
> Hi,
>
> snd_pcm_hardware_t is NOT pre-initialized, and drivers are responsible to
> define ALL fields necessary. This is too bad, because it essentially means that
> a new constraint (i.e. period_size_min + period_size_max) will need to be
> supported by all drivers.
well, but drivers supporting G72x are very rare.
then why bother to change the common code to affect every driver?
>
> I have tested successfully such a new constraint (patch in attachment), and
> hope that you'll incorporate it in the cvs anyway.
it'd be better to add the constraint only if the period_size_min and
max are non-zero, since most of drivers do NOT want to use this
constraint.
the similar should be applied to the period_bytes constraint if we
add period_size constraint, because they may conflict with each
other.
ciao,
Takashi
-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
next prev parent reply other threads:[~2002-09-06 16:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <s5hsn0z9h55.wl@alsa2.suse.de>
2002-08-29 20:57 ` struct _snd_pcm_hardware Guilhem Tardy
2002-08-30 15:53 ` Jaroslav Kysela
2002-09-06 16:28 ` snd_pcm_hardware_t NOT pre-initialized Guilhem Tardy
2002-09-06 16:43 ` Takashi Iwai [this message]
2002-09-06 16:58 ` Guilhem Tardy
2002-09-09 14:22 ` Jaroslav Kysela
2002-09-10 15:29 ` updated patch for period_size constraint Guilhem Tardy
2002-09-10 16:47 ` Takashi Iwai
2002-09-10 17:06 ` Guilhem Tardy
2002-09-10 17:11 ` 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=s5h8z2f1324.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=guilhem_tardy@yahoo.com \
/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.