Skip to contentSkip to conversation

status of the USB ov511.c driver in kernel 2.6?

DISCUSSION Adrian Bunk 3 participants 3 messages Feb 28, 2005 – Mar 1, 2005

lore
Share & tools
lore
#0 lore raw

I noticed the following regarding the drivers/usb/media/ov511.c driver:
- it's not updated compared to upstream:
- version 1.64 is neither version 2 nor the latest 1.x version 1.65
- there's no *_decomp.c module in the kernel sources

Are there any reasons why the upstream driver can't be resynced with the kernel?

cu
Adrian

Signature · 4 lines
       "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
#1 lore raw
Quoted 1 line · Adrian Bunk

- there's no *_decomp.c module in the kernel sources

If I remember correctly people are bit uneasy about putting decompression of proprietary codecs into to the kernel.

See
http://www.mail-archive.com/[email protected]/msg04778.html

Every kernel release I end up building an external module just to get my OV518 usb webcam to work. (It requires decompression support) Not cool.

Quoted 2 lines

Are there any reasons why the upstream driver can't be resynced with the kernel?

I think ovcamchip is from the development branch, but ov511 is from the stable branch. Not sure about that. Best bet is contact Mark McClelland (maintainer) here:

mmcclell <atsign> calpoly.edu
or mark <atsign> alpha.dyndns.org

Richard Hughes

Signature · 1 line
http://www.hughsie.com/PUBLIC-KEY
#2 lore raw
In reply to Adrian Bunk
Quoted 7 lines · Adrian Bunk

I noticed the following regarding the drivers/usb/media/ov511.c driver:
- it's not updated compared to upstream:
- version 1.64 is neither version 2 nor the latest 1.x version 1.65
- there's no *_decomp.c module in the kernel sources

Are there any reasons why the upstream driver can't be resynced with the kernel?

No one has sent me patches :(

greg k-h