From: Andrew Morton <akpm@osdl.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: rlrevell@joe-job.com, mchehab@brturbo.com.br,
alsa-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
nshmyrev@yandex.ru, v4l@cerqueira.org
Subject: Re: [Alsa-devel] Re: + v4l-720-alsa-support-for-saa7134-that-should-work-fix.patch added to -mm tree
Date: Mon, 7 Nov 2005 11:48:43 -0800 [thread overview]
Message-ID: <20051107114843.0a476d90.akpm@osdl.org> (raw)
In-Reply-To: <s5h4q6opi5t.wl%tiwai@suse.de>
Takashi Iwai <tiwai@suse.de> wrote:
>
> > OK, a brief review:
> >
> > - Why couldn't you use ALSA's DMA API?
>
> This is OK, IMO. Basically, it's up to the driver.
>
>
> > - The DMA must be stopped and started in the trigger callback, not the
> > prepare callback.
> >
> > - If this device lacks a volume control alsa-lib can emulate it in
> > software, just create a proper /usr/share/alsa/cards/your_card.conf
> > file.
> >
> > - By ALSA convention the acceptable formats, sample rates, etc should
> > be directly defined in the snd_pcm_hardware_t structure.
> >
> > - dev->oss needs to go.
>
> Agreed about the rest.
Thanks, guys.
Despite all that, I am inclined to merge this patch into 2.6.15. Because
it's in the middle of a 192-patch series and we do need to get the v4l tree
synced up.
Mauro&co, if we do that, do you think the above points can be addressed
inside the next four weeks or so?
next prev parent reply other threads:[~2005-11-07 19:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200511060743.jA67hpZa018948@shell0.pdx.osdl.net>
2005-11-06 8:12 ` Andrew Morton
2005-11-06 18:33 ` Lee Revell
2005-11-07 6:26 ` Mauro Carvalho Chehab
2005-11-07 15:33 ` Lee Revell
2005-11-07 15:54 ` [Alsa-devel] " Takashi Iwai
2005-11-07 19:48 ` Andrew Morton [this message]
2005-11-07 20:19 ` Lee Revell
2005-11-07 20:36 ` Mauro Carvalho Chehab
2005-11-07 6:39 ` Mauro Carvalho Chehab
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=20051107114843.0a476d90.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=alsa-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@brturbo.com.br \
--cc=nshmyrev@yandex.ru \
--cc=rlrevell@joe-job.com \
--cc=tiwai@suse.de \
--cc=v4l@cerqueira.org \
/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
all inboxes | Powered by JetHome®