From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: "Nemosoft Unv." <nemosoft@smcc.demon.nl>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
johannes@erdfelt.com, linux-usb-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org,
Erik Mouw <J.A.K.Mouw@ITS.TUDelft.NL>,
randy.dunlap@intel.com
Subject: Re: ac15 and 2.4.5-pre6, pwc format conversion
Date: Fri, 25 May 2001 15:51:02 -0400 [thread overview]
Message-ID: <3B0EB7A6.E0B17C79@mandrakesoft.com> (raw)
In-Reply-To: <XFMail.010525213709.nemosoft@smcc.demon.nl>
"Nemosoft Unv." wrote:
> On 25-May-01 Alan Cox wrote:
> > It breaks apps by doing conversions, and it breaks important apps like H263
> > codecs not silly little camera viewers, because you trash the performance
>
> This is a NULL argument. First, it doesn´t break anything; I think H263 is
> smart to pick a YUV format if it´s available. Second, conversion has to be
> done at one point or another. If the native format of the camera is RGB,
> H263 will have to convert to YUV. Wether or not this is done in kernel space
> or user space doesn´t matter: it has to be done. And in case the native
> format of the camera doesn´t resemble anything in V4L, you will have TWO
> conversion: first, in kernel from native to V4L palette, and then in your
> tool from V4L to whatever format you need, while maybe the driver could do
> it all in one stage.
Sorry this is a slippery slope argument and it won't wash.
The kernel is intended as the arbiter between userspace and hardware,
and userspace and userspace. Format conversion has nothing to do with
arbitration.
Format conversion in kernelspace is far less flexible than userspace:
you cannot replace your algorithms at will nor fix bugs at will. You
cannot support assembly optimizations for format conversions without
bloating the kernel.
Finally, the example you describe is invalid. If your tool is doing
-two- format conversions, then [again] the tool should be fixed. The
kernel most definitely should not work around stupid shortcomings of
userspace software.
> Anyway, I am not going to debate this any further at this point. Johannes,
> please remove my webcam driver from the USB source tree,
whatever. I don't see Alan or Linus accepting such a change, even if
Johannes does.
> until the software
> YUV/RGB conversion has been removed from ALL other video devices (preferably
> all at the same time).
Send a patch for this instead!
Format conversion should not be in the kernel...
Jeff
--
Jeff Garzik | "Are you the police?"
Building 1024 | "No, ma'am. We're musicians."
MandrakeSoft |
next prev parent reply other threads:[~2001-05-25 19:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-25 6:50 ac15 and 2.4.5-pre6, pwc format conversion Norbert Preining
2001-05-25 8:48 ` Nemosoft Unv.
2001-05-25 11:15 ` Erik Mouw
2001-05-25 13:22 ` Nemosoft Unv.
2001-05-25 15:58 ` Alan Cox
2001-05-25 19:37 ` Nemosoft Unv.
2001-05-25 19:51 ` Jeff Garzik [this message]
2001-05-25 20:12 ` The difference between Linus's kernel and Alan Cox's kernel Thiago Vinhas de Moraes
2001-05-25 21:32 ` Erik Mouw
2001-05-25 21:40 ` CaT
2001-05-25 21:50 ` Erik Mouw
2001-05-25 23:05 ` Alan Cox
2001-05-28 15:50 ` Thiago Vinhas de Moraes
2001-05-25 23:03 ` ac15 and 2.4.5-pre6, pwc format conversion Alan Cox
2001-05-25 16:52 ` Erik Mouw
2001-05-25 11:00 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2001-05-25 15:37 Dunlap, Randy
2001-05-25 16:03 ` Alan Cox
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=3B0EB7A6.E0B17C79@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=J.A.K.Mouw@ITS.TUDelft.NL \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=johannes@erdfelt.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=nemosoft@smcc.demon.nl \
--cc=randy.dunlap@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox