From: Craig Milo Rogers <rogers@isi.edu>
To: Linus Torvalds <torvalds@osdl.org>
Cc: linux-kernel mailing list <linux-kernel@vger.kernel.org>,
greg@kroah.com, nemosoft@smcc.demon.nl,
linux-usb-devel@lists.sourceforge.net
Subject: PWC: A Plea for Grace
Date: Fri, 27 Aug 2004 17:28:06 -0700 [thread overview]
Message-ID: <20040828002806.GH24018@isi.edu> (raw)
Linus, Greg, Nemosoft, and esteemed members of the mailing lists:
I plea for a graceful transition.
Rather than immediately removing the codec registration hook
from the pwc driver, and instantly degrading an up-to-then stable
driver in a now-stable kernel release series, I ask that all concerned
parties consider the following plan:
1) The pwc codec registration hook will be reinstated in the
pwc driver, but the driver will be marked "deprecated"
in appropriate comments, documentation, and perhaps build files.
2) The deprecated driver will be scheduled to be removed from
the next Linux kernel major release series (2.7, 2.8, 3.0,
whatever is next).
1) This will be a firm deadline, and all involved parties,
whether developers or users, will have the opportunity
to be cognizant of it, and prepare for its eventual
arrival.
3) A new driver, say pwc2, will be created that will pass the raw
data stream to user-mode application programs.
1) Nemosoft's present implementation of raw streams can serve
as a baseline implementation.
2) The final raw stream API will be coordinated with l4v2.
4) An API and framework will be constructed to allow user-mode
stream decoding (decompression), with minimum impact on
application programs, as described in my previous message.
1) This design should be coordinated with the v4l2 project,
and adopted as a standard for v4l2, if there are no serious
technical objections to this approach.
5) A team will be assembled to implement this design.
1) The team will need to coordinate with, or be a subset of, the
v4l2 team.
6) Coordinating with this, an effort will be made to talk to
Philips, Logitech, and other concerned manufacturers, and present
them with a rational business case for allowing the open-source
implementation of the currently proprietary codecs.
7) Finally, and admittedly the most fragile link in my proposal,
the current out-of-the-kernel pwcx (closed-source codec) module
will continue to be maintained and offered until the transition to
pwc2 is complete. Please remember, everyone, that without access
to the codecs presently embodied in pwcx, the in-kernel pwc driver
or a reimplemtation of it is of little real interest to most users
of the hardware supported by the pwc driver.
I realize that I'm asking for forebearance, and
let-bygones-be-bygones, from a number of people. In particular, this
plan won't work without Nemosoft's active involvement, as his approval
is needed to properly resurrect the present pwc driver, and he's the
only person at present who can maintain the pwcx module.
Please consider this proposal of graceful transition as a
positive policy evolution for the Linux kernel, and for the Linux
community at large.
Craig Milo Rogers
reply other threads:[~2004-08-28 0:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20040828002806.GH24018@isi.edu \
--to=rogers@isi.edu \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=nemosoft@smcc.demon.nl \
--cc=torvalds@osdl.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