From: Adrian Bunk <bunk@stusta.de>
To: Luca Risolia <luca.risolia@studio.unibo.it>
Cc: linux-usb-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: status of the USB w9968cf.c driver in kernel 2.6?
Date: Sat, 12 Mar 2005 00:03:12 +0100 [thread overview]
Message-ID: <20050311230312.GR3723@stusta.de> (raw)
In-Reply-To: <1109930313.42283149b4ae6@posta.studio.unibo.it>
On Fri, Mar 04, 2005 at 10:58:33AM +0100, Luca Risolia wrote:
> Scrive Adrian Bunk <bunk@stusta.de>:
>
> > On Tue, Mar 01, 2005 at 06:46:03PM +0100, Luca Risolia wrote:
> > > Scrive Adrian Bunk <bunk@stusta.de>:
>...
> > > > - there's no w9968cf-vpp module in the kernel sources
> > >
> > > w9968cf-vpp is an optional, gpl'ed module, which can not be included in the
> >
> > > mainline kernel, as I explained in the documentation of the driver.
> >
> > Please keep in mind that official kernels do not include the second
> > module for performance purposes.
> >
> > What exactly does this mean?
>
> Frame decoding/decompression should be done in userspace, although you can
> still download and use a separate kernel module.
>...
If it's deprecated to do this in a kernel module, shouldn't at some time
the EXPORT_SYMBOL's for the decoding/decompression module be removed
from the kernel?
> Regards,
> Luca
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2005-03-11 23:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-28 23:14 status of the USB w9968cf.c driver in kernel 2.6? Adrian Bunk
2005-03-01 5:43 ` [linux-usb-devel] " Greg KH
2005-03-01 17:46 ` Luca Risolia
2005-03-03 15:29 ` Adrian Bunk
2005-03-04 9:58 ` Luca Risolia
2005-03-11 23:03 ` Adrian Bunk [this message]
2005-03-04 17:17 ` [linux-usb-devel] " michel Xhaard
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=20050311230312.GR3723@stusta.de \
--to=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=luca.risolia@studio.unibo.it \
/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