- 10 Oct, 2007 40 commits
-
-
Mauro Carvalho Chehab authored
Release code should happen before the cleaning of map variable. Signed-off-by:
Mauro Carvalho Chehab <mchehab@infradead.org>
-
Mauro Carvalho Chehab authored
Signed-off-by:
Mauro Carvalho Chehab <mchehab@infradead.org>
-
Mauro Carvalho Chehab authored
Signed-off-by:
Mauro Carvalho Chehab <mchehab@infradead.org>
-
Mauro Carvalho Chehab authored
Thanks to Michael Krufky for pointing this to me. Signed-off-by:
Mauro Carvalho Chehab <mchehab@infradead.org>
-
Mauro Carvalho Chehab authored
Due to the replace of videobuf_read_one to videobuf_read_stream, poll() method implementation is wrong. This fixes poll() implementation, making read of /dev/video? to work again. With this method, an USB driver can use video-buf, without needing to request memory from the DMA-safe area. Signed-off-by:
Mauro Carvalho Chehab <mchehab@infradead.org>
-
Mauro Carvalho Chehab authored
Signed-off-by:
Mauro Carvalho Chehab <mchehab@infradead.org>
-
Mauro Carvalho Chehab authored
Signed-off-by:
Mauro Carvalho Chehab <mchehab@infradead.org> http://thread.gmane.org/gmane.comp.video.video4linux/34978/focus=34981Reviewed-by:
Ricardo Cerqueira <v4l@cerqueira.org>
-
Mauro Carvalho Chehab authored
This patch removes the usage of videobuf-dma-sg from vivi driver, using instead videobuf-vmalloc. This way, vivi will be useful for testing the newer method. Reverting this patch won't hurt vivi, since both methods work fine. Signed-off-by:
Mauro Carvalho Chehab <mchehab@infradead.org>
-
Mauro Carvalho Chehab authored
Adds a newer videobuf-vmalloc module. This module uses the same videobuf controls, but implements memory allocation based on vmalloc methods. With this method, an USB driver can use video-buf, without needing to request memory from the DMA-safe area. Signed-off-by:
Mauro Carvalho Chehab <mchehab@infradead.org>
-
Mauro Carvalho Chehab authored
Signed-off-by:
Mauro Carvalho Chehab <mchehab@infradead.org>
-
Mauro Carvalho Chehab authored
PCI-dependent videobuf_foo methods were renamed as videobuf_pci_foo. Also, videobuf_dmabuf is now part of videobuf-dma-sg private struct. So, to access it, a subroutine call is needed. This patch renames all occurences of those function calls to be consistent with the video-buf split. Signed-off-by:
Mauro Carvalho Chehab <mchehab@infradead.org> http://thread.gmane.org/gmane.comp.video.video4linux/34978/focus=34981Reviewed-by:
Ricardo Cerqueira <v4l@cerqueira.org>
-
Mauro Carvalho Chehab authored
video-buf currently does two different tasks: - Manages video buffers with a common code that allows implementing all the V4L2 different modes of buffering; - Controls memory allocations While the first task is generic, the second were written to support PCI DMA Scatter/Gather needs. The original approach can't even work for those video capture hardware that don't support scatter/gather. I did one approach to make it more generic. While the approach worked fine for vivi driver, it were not generic enough to handle USB needs. This patch creates two different modules, one containing the generic video buffer handling (videobuf-core) and another with PCI DMA S/G. After this patch, it would be simpler to write an USB video-buf and a non-SG DMA module. Signed-off-by:
Mauro Carvalho Chehab <mchehab@infradead.org> http://thread.gmane.org/gmane.comp.video.video4linux/34978/focus=34981Reviewed-by:
Ricardo Cerqueira <v4l@cerqueira.org>
-
Brett Warden authored
coding-style repairs Signed-off-by:
Andrew Morton <akpm@linux-foundation.org> Signed-off-by:
Mauro Carvalho Chehab <mchehab@infradead.org>
-
Sascha Sommer authored
Adds an entry for the Typhoon Tv-Tuner PCI to bttv-cards.c Signed-off-by:
Sascha Sommer <saschasommer@freenet.de> Signed-off-by:
Mauro Carvalho Chehab <mchehab@infradead.org>
-
Mauro Carvalho Chehab authored
IR workqueue should be disabled during suspend. This avoids some troubles, like the one reported on bug #8689: "The Hauppauge HVR 1100 ir-remote control does not work after resume from suspend to ram or disk." This patch disables IR before suspending, re-enabling it after resume. Thanks to Peter Poklop <Peter.Poklop@gmx.at> for reporting it and helping with the fix. Signed-off-by:
Mauro Carvalho Chehab <mchehab@infradead.org> Reviewed-by:
Peter Poklop <Peter.Poklop@gmx.at>
-
Trent Piepho authored
Redoes the way the control word is stored and set. The existing code was a lot more complicated than it needed to be. Signed-off-by:
Trent Piepho <xyzzy@speakeasy.org> Signed-off-by:
Douglas Schilling Landgraf <dougsland@gmail.com> Signed-off-by:
Mauro Carvalho Chehab <mchehab@infradead.org> Reviewed-by:
Pekka Seppänen <pexu@kapsi.fi>
-
Trent Piepho authored
Frequency calculation to use better math. It's still the same IF offset and step size (which are not the same as the datasheet says) as the code was before. It's just more efficient and accurate. Signed-off-by:
Trent Piepho <xyzzy@speakeasy.org> Reviewed-by:
Pekka Seppänen <pexu@kapsi.fi> Signed-off-by:
Douglas Schilling Landgraf <dougsland@gmail.com> Signed-off-by:
Mauro Carvalho Chehab <mchehab@infradead.org>
-
Pekka Seppanen authored
Code cleanup for GemTek Radio card driver. Removed unnecessary / invalid I/O commands and rewrote code for tuning on-board BU2614FS chip. Adds several new module params for power users. Includes automatic device probing. Signed-off-by:
Pekka Seppanen <pexu@kapsi.fi> Signed-off-by:
Douglas Schilling Landgraf <dougsland@gmail.com> Reviewed-by:
Trent Piepho <xyzzy@speakeasy.org> Signed-off-by:
Mauro Carvalho Chehab <mchehab@infradead.org>
-
Pekka Seppanen authored
Details now match with radio-gemtek.c, eg. no more different ports. Included a short note about cards that should be compatible with radio-gemtek module. Signed-off-by:
Pekka Seppanen <pexu@kapsi.fi> Signed-off-by:
Douglas Schilling Landgraf <dougsland@gmail.com> Reviewed-by:
Trent Piepho <xyzzy@speakeasy.org> Signed-off-by:
Mauro Carvalho Chehab <mchehab@infradead.org>
-
Michael Krufky authored
s/driver/drives/1 Signed-off-by:
Michael Krufky <mkrufky@linuxtv.org> Signed-off-by:
Mauro Carvalho Chehab <mchehab@infradead.org>
-
Brett Warden authored
Fixes use of parport_write_control() to match the newer interface that requires explicit parport_data_reverse() and parport_data_forward() calls. This eliminates the following error message and restores the original intended behavior: parport0 (bw-qcam): use data_reverse for this! Also increases threshold in qc_detect() from 300 to 400, as my camera often results in a count of approx 330. Added a kernel error message to indicate detection failure. Thanks Ray and Randy for your comments, and for pointing out that I needed to reset the port to forward mode! Signed-off-by:
Brett T. Warden <brett.warden@gmail.com> Acked-by:
Alan Cox <alan@redhat.com> Signed-off-by:
Andrew Morton <akpm@linux-foundation.org> Signed-off-by:
Mauro Carvalho Chehab <mchehab@infradead.org>
-
Oliver Neukum authored
The pwc driver is defficient in locking, which can trigger an oops when disconnecting. Signed-off-by:
Oliver Neukum <oneukum@suse.de> CC: Luc Saillard <luc@saillard.org> Signed-off-by:
Mauro Carvalho Chehab <mchehab@infradead.org>
-
Andres Salomon authored
By default, we allocate DMA buffers when actually reading from the video capture device. On a system with 128MB or 256MB of ram, it's very easy for that memory to quickly become fragmented. We've had users report having 30+MB of memory free, but the cafe_ccic driver is still unable to allocate DMA buffers. Our workaround has been to make use of the 'alloc_bufs_at_load' parameter to allocate DMA buffers during device probing. This patch makes DMA buffer allocation happen during device probe by default, and changes the parameter to 'alloc_bufs_at_read'. The camera hardware is there, if the cafe_ccic driver is enabled/loaded it should do its best to ensure that the camera is actually usable; delaying DMA buffer allocation saves an insignicant amount of memory, and causes the driver to be much less useful. Signed-off-by:
Andres Salomon <dilinger@debian.org> Acked-by:
Jonathan Corbet <corbet@lwn.net> Signed-off-by:
Mauro Carvalho Chehab <mchehab@infradead.org>
-
Michael Krufky authored
Signed-off-by:
Michael Krufky <mkrufky@linuxtv.org> Signed-off-by:
Mauro Carvalho Chehab <mchehab@infradead.org>
-
Michael Krufky authored
The name of the pll will be shown if forced via insmod option, or if debug is enabled. Signed-off-by:
Michael Krufky <mkrufky@linuxtv.org> Signed-off-by:
Mauro Carvalho Chehab <mchehab@infradead.org>
-
Michael Krufky authored
Add a module option to force the dvb-pll module to use an alternate dvb-pll description without having to recompile the kernel. Having a module option like this is useful in some cases, where the vendor may release an alternate revision of the hardware using a different tuner, but without changing the pci subsystem / usb device ids. This option is intended for debugging purposes _only_. Signed-off-by:
Michael Krufky <mkrufky@linuxtv.org> Signed-off-by:
Mauro Carvalho Chehab <mchehab@infradead.org>
-
Michael Krufky authored
Increased DVB_PLL_MAX from 16 to a figure that would never be reached in a practical sense. Signed-off-by:
Michael Krufky <mkrufky@linuxtv.org> Signed-off-by:
Mauro Carvalho Chehab <mchehab@infradead.org>
-
Michael Krufky authored
Add a module option to dvb-pll, called "input" to specify which rf input to use on devices with multiple rf inputs. If the module option is not specified, then the driver will autoselect the rf input, as per previous behavior. Signed-off-by:
Michael Krufky <mkrufky@linuxtv.org> Signed-off-by:
Mauro Carvalho Chehab <mchehab@infradead.org>
-
Michael Krufky authored
Store an instance ID in the dvb_pll_priv structure, so that module options specific to a given pll may be used by the functions within the driver. When debug is turned on, print a message indicating which pll was attached and it's instance id. Signed-off-by:
Michael Krufky <mkrufky@linuxtv.org> Signed-off-by:
Mauro Carvalho Chehab <mchehab@infradead.org>
-
Michael Krufky authored
The pll-specific set() function will need access to the dvb_pll_priv structure for new functionality. This patch gives access to this structure to the required functions. Signed-off-by:
Michael Krufky <mkrufky@linuxtv.org> Signed-off-by:
Mauro Carvalho Chehab <mchehab@infradead.org>
-
Stas Sergeev authored
AverTV Studio 307 has only one composite input. Signed-off-by:
Stas Sergeev <stsp@aknet.ru> Acked-by:
Nickolay V. Shmyrev <nshmyrev@yandex.ru> Signed-off-by:
Andrew Morton <akpm@linux-foundation.org> Signed-off-by:
Mauro Carvalho Chehab <mchehab@infradead.org>
-
Michael Krufky authored
Fix the following dependency issue: ERROR: "dvb_dmx_init" [drivers/media/video/video-buf-dvb.ko] undefined! ERROR: "dvb_unregister_adapter" [drivers/media/video/video-buf-dvb.ko] undefined! ERROR: "dvb_register_frontend" [drivers/media/video/video-buf-dvb.ko] undefined! ERROR: "dvb_unregister_frontend" [drivers/media/video/video-buf-dvb.ko] undefined! ERROR: "dvb_net_release" [drivers/media/video/video-buf-dvb.ko] undefined! ERROR: "dvb_frontend_detach" [drivers/media/video/video-buf-dvb.ko] undefined! ERROR: "dvb_dmxdev_release" [drivers/media/video/video-buf-dvb.ko] undefined! ERROR: "dvb_dmx_swfilter" [drivers/media/video/video-buf-dvb.ko] undefined! ERROR: "dvb_net_init" [drivers/media/video/video-buf-dvb.ko] undefined! ERROR: "dvb_dmx_release" [drivers/media/video/video-buf-dvb.ko] undefined! ERROR: "dvb_register_adapter" [drivers/media/video/video-buf-dvb.ko] undefined! ERROR: "dvb_dmxdev_init" [drivers/media/video/video-buf-dvb.ko] undefined! ERROR: "mt2131_attach" [drivers/media/video/cx23885/cx23885.ko] undefined! ERROR: "s5h1409_attach" [drivers/media/video/cx23885/cx23885.ko] undefined! Signed-off-by:
Michael Krufky <mkrufky@linuxtv.org> Signed-off-by:
Mauro Carvalho Chehab <mchehab@infradead.org>
-
Michael Krufky authored
VIDEO_CX23885 must select DVB_PLL if !DVB_FE_CUSTOMISE for FusionHDTV5 Express Signed-off-by:
Michael Krufky <mkrufky@linuxtv.org> Signed-off-by:
Mauro Carvalho Chehab <mchehab@infradead.org>
-
Oliver Endriss authored
DVB-S TT 1500 must use the TT keymap. Signed-off-by:
Oliver Endriss <o.endriss@gmx.de> Signed-off-by:
Mauro Carvalho Chehab <mchehab@infradead.org>
-
Sakari Ailus authored
vidioc_int_g_ifparm returns platform-specific information about the interface settings used by the sensor. Support for [gs]_ext_clk has been removed. Fix indentation and remove useless & characters. Remove experiment for typechecking slave callback function arguments. Signed-off-by:
Sakari Ailus <sakari.ailus@nokia.com> Signed-off-by:
Mauro Carvalho Chehab <mchehab@infradead.org>
-
Sakari Ailus authored
Remove support for g_ext_clk and s_ext_clk. The same functionality is now handled by g_ifparm. Signed-off-by:
Sakari Ailus <sakari.ailus@nokia.com> Signed-off-by:
Mauro Carvalho Chehab <mchehab@infradead.org>
-
Sakari Ailus authored
Signed-off-by:
Sakari Ailus <sakari.ailus@nokia.com> Signed-off-by:
Mauro Carvalho Chehab <mchehab@infradead.org>
-
Sakari Ailus authored
This patch adds BT.656 interface settings for [gs]_ifparm. Signed-off-by:
Sakari Ailus <sakari.ailus@nokia.com> Signed-off-by:
Mauro Carvalho Chehab <mchehab@infradead.org>
-
Sakari Ailus authored
vidioc_int_g_ifparm can be used to obtain hardware-specific information about the interface used by the slave. Rearrange v4l2-int-device.h as well. Also remove useless & characters. Signed-off-by:
Sakari Ailus <sakari.ailus@nokia.com> Signed-off-by:
Mauro Carvalho Chehab <mchehab@infradead.org>
-
Hans-Jürgen Koch authored
There's a serious bug in saa6588.c, it uses a non-initialized spin_lock. Funny thing is that it works fine with bttv, but completly freezes the machine if e.g. saa7134 is loaded. Thanks to Derek Philip for reporting this bug on the rdsd-devel list. This patch adds the missing spin_lock_init(). Signed-off-by:
Hans J. Koch <hjk@linutronix.de> Signed-off-by:
Mauro Carvalho Chehab <mchehab@infradead.org>
-