From: Vinod Koul <vinod.koul@intel.com>
To: Richard Fitzgerald <rf@opensource.wolfsonmicro.com>
Cc: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>,
patches@opensource.wolfsonmicro.com,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
alsa-devel@alsa-project.org
Subject: Re: [PATCH] crec: Add option to specify codec ID
Date: Mon, 28 Nov 2016 21:24:06 +0530 [thread overview]
Message-ID: <20161128155406.GI6408@localhost> (raw)
In-Reply-To: <1480326439.4317.11.camel@rf-debian.wolfsonmicro.main>
On Mon, Nov 28, 2016 at 09:47:19AM +0000, Richard Fitzgerald wrote:
> On Sun, 2016-11-27 at 11:52 -0600, Pierre-Louis Bossart wrote:
> > > I am not Ok to add support for any other format apart from bespoke (file
> > > dump) and PCM wav header and save to file.
> > >
> > > I am okay to add support to dump data to stdio for any format, so that we
> > > dont bother to support those file formats.
> >
> > it's not clear to me why you would make an exception for bespoke, just
> > dump everything to stdio and use a file indirection if you want the raw
> > data in all cases?
> >
>
> Yes, I think that's best. For one thing it's easier to explain in the -h
> help: PCM can go to wav file, everything can go to stdout, stdout is
> always raw.
Yeah lets do that :)
--
~Vinod
prev parent reply other threads:[~2016-11-28 15:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 11:44 [PATCH] crec: Add option to specify codec ID Richard Fitzgerald
2016-11-16 13:05 ` Vinod Koul
2016-11-16 13:07 ` Richard Fitzgerald
2016-11-16 13:48 ` Charles Keepax
2016-11-16 14:53 ` Richard Fitzgerald
2016-11-18 3:53 ` Vinod Koul
2016-11-18 10:11 ` Richard Fitzgerald
2016-11-18 10:29 ` Vinod Koul
2016-11-18 14:39 ` Pierre-Louis Bossart
2016-11-18 16:17 ` Charles Keepax
2016-11-23 3:41 ` Vinod Koul
2016-11-23 10:21 ` Richard Fitzgerald
2016-11-23 10:38 ` Vinod Koul
2016-11-27 17:52 ` Pierre-Louis Bossart
2016-11-28 9:47 ` Richard Fitzgerald
2016-11-28 15:54 ` Vinod Koul [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=20161128155406.GI6408@localhost \
--to=vinod.koul@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=ckeepax@opensource.wolfsonmicro.com \
--cc=patches@opensource.wolfsonmicro.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=rf@opensource.wolfsonmicro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).