From: David Henningsson <david.henningsson@canonical.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: chase.douglas@canonical.com, alsa-devel@alsa-project.org,
david.woodhouse@intel.com
Subject: Re: Merging alsa-firmware into linux-firmware
Date: Thu, 22 Jul 2010 14:41:20 +0200 [thread overview]
Message-ID: <4C483C70.9010808@canonical.com> (raw)
In-Reply-To: <s5hsk3bzrsf.wl%tiwai@suse.de>
On 2010-07-22 13:20, Takashi Iwai wrote:
> At Thu, 22 Jul 2010 12:07:33 +0200,
> David Henningsson wrote:
>> usx2yloader however seems to put files outside the /lib/firmware path
>> (/usr/share/alsa/...), and I believe it has a userspace firmware loader
>> triggered by an udev event.
>
> These are basically for 2.2 / 2.4 kernels. Don't touch them unless you
> are 100% sure you do right :)
Assuming you mean the tascam usx2yloader, a little digging shows that,
1) the usx2y driver never calls request_firmware (unless I really missed
something)
2) there is an Ubuntu specific patch which creates an udev rule for
calling tascam_fw and tascam_fpga (from alsa-tools) when a tascam device
is connected.
Are you saying that the tascam devices (us122, us224, us428) no longer
need that firmware?
--
David Henningsson, Canonical Ltd.
http://launchpad.net/~diwic
next prev parent reply other threads:[~2010-07-22 12:41 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
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 [this message]
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=4C483C70.9010808@canonical.com \
--to=david.henningsson@canonical.com \
--cc=alsa-devel@alsa-project.org \
--cc=chase.douglas@canonical.com \
--cc=david.woodhouse@intel.com \
--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.