From: John Sullivan <johns@fsf.org>
To: alsa-devel@lists.sourceforge.net
Subject: Making firmware licensing info more prominent (Matrix)
Date: Fri, 30 Jun 2006 13:45:00 -0400 [thread overview]
Message-ID: <87odwa5yhv.fsf@spider.localnet> (raw)
(I checked the archives and didn't see any obvious discussion of this
question; apologies if I missed it, I don't usually follow the list.)
Many of the people using the ALSA matrix are committed to using free
software, and they consult the matrix in order to find sound devices
that will be compatible with their systems. It's a great resource for
that.
But some of the USB devices, while supported by ALSA, require firmware
that is nonfree in licensing.
http://www.alsa-project.org/alsa-doc/doc-php/template.php?company=Midiman%2FMAudio&card=USB+Midisport+4x4.&chip=Cypress+AN2131XX&module=usb-audio
is one example.
While the licensing information for the module is displayed on this
page, the licensing information for the firmware and the firmware
loader is not. It looks like the loader in this case is free software,
but the firmware is proprietary.
Can this information be made more prominent? I think it would be
helpful to many of the people using the matrix.
--
John Sullivan
Free Software Foundation
Program Administrator | Phone: (617)542-5942 x23
51 Franklin Street, 5th Fl. | Fax: (617)542-2652
Boston, MA 02110-1301 USA | GPG: AE8600B6
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
next reply other threads:[~2006-06-30 17:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-30 17:45 John Sullivan [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-30 17:51 Making firmware licensing info more prominent (Matrix) John Sullivan
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=87odwa5yhv.fsf@spider.localnet \
--to=johns@fsf.org \
--cc=alsa-devel@lists.sourceforge.net \
/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.