linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Erdfelt <johannes@erdfelt.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Kelledin Tane <runesong@earthlink.net>, linux-kernel@vger.kernel.org
Subject: Re: drivers/usb/ov511.c does not compile
Date: Fri, 15 Jun 2001 16:52:04 -0400	[thread overview]
Message-ID: <20010615165204.C30332@sventech.com> (raw)
In-Reply-To: <20010615160518.A30332@sventech.com> <E15B0IP-00073f-00@the-village.bc.nu>
In-Reply-To: <E15B0IP-00073f-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Fri, Jun 15, 2001 at 09:34:21PM +0100

On Fri, Jun 15, 2001, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> > > the developer's blessing on this, and also nice to know exactly what
> > > version number to give this driver in 2.4.5 stock.
> > 
> > This has already been fixed in the 2.4.5 pre patches.
> 
> .6 I assume.

Yes, you're absolutely correct. Typo on my part.

> ov511 still has some bad bugs in it - it doesnt work with some uhci drivers
> and it also does precisely the wrong thing when you set the capture size and
> breaks stuff like ffserver. The comments are right but the code picks the
> size which is bigger than the capture, not the nearest smaller size..

Hmm, I'll see if I can produce a patch to fix that.

JE


  reply	other threads:[~2001-06-15 20:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-15 19:54 drivers/usb/ov511.c does not compile Kelledin Tane
2001-06-15 20:05 ` Johannes Erdfelt
2001-06-15 20:34   ` Alan Cox
2001-06-15 20:52     ` Johannes Erdfelt [this message]
2001-06-15 21:23       ` Kernel 2.0.35 limits Paul Faure
2001-06-15 21:27         ` Alan Cox
2001-06-16  5:27           ` Paul Faure
2001-06-16 12:11           ` Thomas Bogendoerfer
2001-06-15 21:35         ` Alexander Viro
2001-06-15 20:11 ` drivers/usb/ov511.c does not compile Kelledin Tane

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=20010615165204.C30332@sventech.com \
    --to=johannes@erdfelt.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=runesong@earthlink.net \
    /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;
as well as URLs for NNTP newsgroup(s).