All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Hofman <pavel.hofman@ivitera.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH - aplay 1/1] aplay - option to dump HW	parameters
Date: Mon, 05 Mar 2012 15:43:08 +0100	[thread overview]
Message-ID: <4F54D0FC.60103@ivitera.com> (raw)
In-Reply-To: <s5hfwdn6s90.wl%tiwai@suse.de>

Dne 5.3.2012 15:23, Takashi Iwai napsal(a):
> At Fri,  2 Mar 2012 20:32:58 +0000,
> pavel.hofman@ivitera.com wrote:
>>
>> From: Pavel Hofman <pavel.hofman@ivitera.com>
>>
>> Dumping HW parameters of the current device with snd_pcm_hw_params_dump,
>> a new option --dump-hw-params added.
> 
> Well, the purpose and the actual operation of this option is a bit
> unclear with such a short description.  Your patch adds the output of
> the pre-config state of the hw_params.  It makes sense since the
> post-config state is shown via -v option.  If this is the intended
> behavior, please write a bit more details in the man page.
> 
> 

Takashi, thanks for your reply. Could I call it hardware capabilities of
the device? Because that is what I think it is. E.g. I fixed that
ice1724 rate-lock incompletion with help of this dump and people have
been asking me about listing similar to ossinfo -v4.

Pavel.

  reply	other threads:[~2012-03-05 14:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-02 20:32 [PATCH - aplay 1/1] aplay - option to dump HW parameters pavel.hofman
2012-03-05 14:23 ` Takashi Iwai
2012-03-05 14:43   ` Pavel Hofman [this message]
2012-03-05 15:01     ` Takashi Iwai
2012-03-05 15:02       ` Takashi Iwai
2012-03-05 15:06         ` Pavel Hofman
2012-03-05 15:37           ` Takashi Iwai
  -- strict thread matches above, loose matches on Subject: below --
2012-03-05 21:27 pavel.hofman
2012-03-06  9:42 ` 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=4F54D0FC.60103@ivitera.com \
    --to=pavel.hofman@ivitera.com \
    --cc=alsa-devel@alsa-project.org \
    --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.