All of lore.kernel.org
 help / color / mirror / Atom feed
From: Clemens Ladisch <clemens@ladisch.de>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>,
	Jay Fenlason <fenlason@redhat.com>
Cc: alsa-devel@alsa-project.org, linux1394-devel@lists.sourceforge.net
Subject: [PATCH 0/2] LaCie Firewire Speakers/Griffin FireWave support
Date: Mon, 07 Feb 2011 10:13:44 +0100	[thread overview]
Message-ID: <4D4FB7C8.7090501@ladisch.de> (raw)
In-Reply-To: <4D46933D.5050609@ladisch.de>

This driver version is, I hope, finished enough so that I can commit it
soon.

The FireWave's low-frequency processing makes me believe that this
device is prepared to accept two- and four-channel data, so I've enabled
this in the driver; but I'd still like to actually know if it works.
(If it does, adding support for the AC-3 decoding will be possible too.)

I haven't yet looked into volume controls.

Jay, are you OK with "Tested-by: Jay Fenlason <fenlason@redhat.com>"?

Stefan, if those firewire core bits are worth your notice :) , please
give an Acked-by for them.  


Regards,
Clemens

       reply	other threads:[~2011-02-07  9:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4D46933D.5050609@ladisch.de>
2011-02-07  9:13 ` Clemens Ladisch [this message]
2011-02-07  9:14   ` [PATCH 1/2] ALSA: add LaCie Firewire Speakers/Griffin FireWave surround driver Clemens Ladisch
2011-02-07 14:40     ` Stefan Richter
2011-02-07 14:56       ` Clemens Ladisch
2011-02-07 21:56       ` Stefan Richter
2011-02-08  8:05         ` Clemens Ladisch
2011-02-08 13:37         ` Clemens Ladisch
2011-02-08 21:10           ` Stefan Richter
2011-02-07 16:49     ` Stefan Richter
2011-02-07 16:57       ` Clemens Ladisch
2011-02-10  9:46     ` [PATCH] " Clemens Ladisch
2011-02-07  9:14   ` [PATCH 2/2] alsa-lib: add LaCie Firewire Speakers/Griffin FireWave Surround driver Clemens Ladisch

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=4D4FB7C8.7090501@ladisch.de \
    --to=clemens@ladisch.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=fenlason@redhat.com \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=stefanr@s5r6.in-berlin.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.