public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: michel Xhaard <mxhaard@magic.fr>
To: Adrian Bunk <bunk@stusta.de>,
	Luca Risolia <luca.risolia@studio.unibo.it>
Cc: linux-usb-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [linux-usb-devel] Re: status of the USB w9968cf.c driver in kernel 2.6?
Date: Fri, 4 Mar 2005 18:17:30 +0100	[thread overview]
Message-ID: <200503041817.30757.mxhaard@magic.fr> (raw)
In-Reply-To: <20050303152908.GC4608@stusta.de>

Le Jeudi 3 Mars 2005 16:29, Adrian Bunk a écrit :
> On Tue, Mar 01, 2005 at 06:46:03PM +0100, Luca Risolia wrote:
> > Scrive Adrian Bunk <bunk@stusta.de>:
> > > I noticed the following regarding the drivers/usb/media/ov511.c driver:
> >
> >                                                           ^^^^^^^
> >
> > > - it's not updated compared to upstream:
> >
> > Could you provide more details?
>
> Sorry, my fault.
> I confused this with a different driver.
>
> > > - 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?
>
> Is it useful or not?
>
> > Regards,
> >       Luca
>
> cu
> Adrian

it is :) 
-- 
Michel Xhaard


      parent reply	other threads:[~2005-03-04 17:26 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
2005-03-04 17:17     ` michel Xhaard [this message]

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=200503041817.30757.mxhaard@magic.fr \
    --to=mxhaard@magic.fr \
    --cc=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