From: Clemens Ladisch <clemens@ladisch.de>
To: David Henningsson <david.henningsson@canonical.com>
Cc: Chase Douglas <chase.douglas@canonical.com>,
alsa-devel@alsa-project.org,
David Woodhouse <david.woodhouse@intel.com>
Subject: Re: Merging alsa-firmware into linux-firmware
Date: Tue, 20 Jul 2010 15:31:36 +0200 [thread overview]
Message-ID: <4C45A538.2060704@ladisch.de> (raw)
In-Reply-To: <4C457C89.5040209@canonical.com>
David Henningsson wrote:
> Chase Douglas (@canonical) and I plan to take what's left of
> alsa-firmware and try to merge it into linux-firmware, this might happen
> now or in the coming weeks. This will make alsa-firmware obsolete as all
> firmware will be provided by linux-firmware instead.
Good idea; these packages have exactly the same purpose.
> Any words of ... warnings
I wonder what you're going to do about the multisound firmware files;
the /lib/firmware/turtlebeach/*.bin files are just symbolic links to
the actual files in /etc/sound that owners of these cards (if any such
still exist) are supposed to have.
The stuff in emi_26_62 isn't used. (Er, wasn't there a regression
introduced in the emi62 firmware in 2.6.27?)
Regards,
Clemens
next prev parent reply other threads:[~2010-07-20 13:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-20 10:38 Merging alsa-firmware into linux-firmware David Henningsson
2010-07-20 10:51 ` David Woodhouse
2010-07-21 9:29 ` David Henningsson
2010-07-21 9:31 ` David Woodhouse
2010-07-26 8:15 ` David Henningsson
2010-07-26 8:36 ` Takashi Iwai
2010-07-20 13:31 ` Clemens Ladisch [this message]
2010-07-20 15:47 ` David Henningsson
2010-07-21 6:53 ` Clemens Ladisch
2010-07-21 13:31 ` David Henningsson
2010-07-21 14:02 ` David Woodhouse
2010-07-21 14:30 ` David Henningsson
2010-07-20 13:36 ` Takashi Iwai
2010-07-22 10:07 ` David Henningsson
2010-07-22 11:20 ` Takashi Iwai
2010-07-22 12:41 ` David Henningsson
2010-07-22 12:46 ` 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=4C45A538.2060704@ladisch.de \
--to=clemens@ladisch.de \
--cc=alsa-devel@alsa-project.org \
--cc=chase.douglas@canonical.com \
--cc=david.henningsson@canonical.com \
--cc=david.woodhouse@intel.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.