From: "Adam J. Richter" <adam@yggdrasil.com>
To: steve@steve-parker.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: PWC issue
Date: Sat, 28 Aug 2004 10:50:05 -0700 [thread overview]
Message-ID: <200408281750.i7SHo5C05936@freya.yggdrasil.com> (raw)
>How does the Philips WebCam (pwc/pwcx) issue affect the speedtch
>project? AIUI, that project requires additional proprietary microcode to
>work.
>
>The ramifications are potentially huge...
>
>Steve
>steve@steve-parker.org
>sparkz@users.sourceforge.net
>(current maintainer of speedtouchconf.sf.net; hoping to resign soon as
>the speedtouch.sf.net project gains more steam, or the speedtch module
>becomes more popular - either way, reducing the importance of my
>project, and allowing me to resign ;-)
I am not a lawyer, so please do not use this as legal advice.
You should keep the proprietary module in a file loaded by
a user space utility that should be invoked by hot plug, and not
just for the legal reason that loading a module with proprietary
firmware would have the user illegally create a GPL-infringing work
in memory (there are US court decisions that copying into RAM is
copying for the purposes of copyright infringement). There are
also several technical reasons.
The amount of unswappable kernel memory is reduced, at least
in the case of a kernel that supports USB hot plugging, since the
kernel will keep that blob around in case another Speedtouch USB
device is plugged in. Even on system that have no swap, this still
means that a page or two more of disk files will be cached into
memory, and every once in a blue moon, the user will save 10
milliseconds by not having to reread that page from disk.
The user can upgrade or modify the microcode without needing
to recompile and unload and reload the module.
Unusual customizations are possible, such as having
two devices plugged in running different "microcode", for example
one unit running stable software on an actual internet connection
and the other running a version for, say, turning the unit into
an answering machine, or for debugging or for performance profiling.
By the way, I have a long running dispute with Greg K-H
about his refusal so far to remove replace the GPL incompatible
firmware in certain USB serial drivers with such a user level
loading mechanism. Go figure.
__ ______________
Adam J. Richter \ /
adam@yggdrasil.com | g g d r a s i l
next reply other threads:[~2004-08-28 2:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-28 17:50 Adam J. Richter [this message]
2004-08-28 5:19 ` Greg KH
2004-08-28 15:11 ` Randy.Dunlap
2004-08-28 15:33 ` Kasper Sandberg
2004-08-28 16:12 ` Greg KH
2004-08-28 17:26 ` Randy.Dunlap
-- strict thread matches above, loose matches on Subject: below --
2004-08-29 4:25 Adam J. Richter
2004-08-29 2:06 Adam J. Richter
2004-08-29 5:01 ` Greg KH
2004-08-29 0:20 Adam J. Richter
2004-08-28 0:57 Steve Parker
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=200408281750.i7SHo5C05936@freya.yggdrasil.com \
--to=adam@yggdrasil.com \
--cc=linux-kernel@vger.kernel.org \
--cc=steve@steve-parker.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®