- 10 Oct, 2007 40 commits
-
-
Steven Toth authored
I wanted to document the NMI assert issue inside the code, even though it's already documented in the patch history. If/when the next cx23887 revision appears, is may need to be enabled on that also. Signed-off-by:
Steven Toth <stoth@hauppauge.com> Signed-off-by:
Michael Krufky <mkrufky@linuxtv.org> Signed-off-by:
Mauro Carvalho Chehab <mchehab@infradead.org>
-
Steven Toth authored
A number of Hauppauge boards share the same tuner and demod configurations. This patch removes duplicate structures. Signed-off-by:
-
Steven Toth authored
Moving some defines into the correct header file. Signed-off-by:
-
Steven Toth authored
Removed unused code. Signed-off-by:
-
Steven Toth authored
Unused code is removed. Signed-off-by:
-
Steven Toth authored
Adding support for the Hauppauge HVR1250 PCIe ATSC board. Signed-off-by:
-
Steven Toth authored
Changed the pci_quirks function to detech the bridge type before setting the NMI clear bit, rather than detecting based on unique board id. Signed-off-by:
-
Steven Toth authored
The pci_quirks function was being called too early during initialisation, it needs to be called after the board has been identified. Signed-off-by:
-
Michael Krufky authored
Signed-off-by:
-
Michael Krufky authored
Turn off i2c_debug by default, to make the driver less verbose. Signed-off-by:
-
Michael Krufky authored
Signed-off-by:
-
Michael Krufky authored
Signed-off-by:
-
Michael Krufky authored
The dvb-pll module is not being used by this driver. Remove the unneeded #include. Signed-off-by:
-
Steven Toth authored
Removed if 0'd code, removed cx88 references. Signed-off-by:
-
Steven Toth authored
The mt2131 tuner reports lock even when the hardware should not lock. This patch allows the s5h1409 demodulator to be configured to query either the tuner driver for status, or the demodulator status when the application requests lock status. This avoids returning false CARRIER and/or SIGNAL lock status. S5H1409 and MT2131 drivers. This is the remainder of the changeset, which only touches cx23885-dvb.c Signed-off-by:
-
Steven Toth authored
Moved the field from cx23885_board to cx23885_dev and added code to iautomatically set the bridge type based on the pci device id. Signed-off-by:
-
Steven Toth authored
This is required to support the cx258xx family of audio and video decoders. Signed-off-by:
-
Steven Toth authored
The cx23885 and cx23887 family use two different memory maps which govern how the internal SRAM is configured. This patch streamlines the access to those structures. Signed-off-by:
-
Steven Toth authored
The sram allocations for the cx23887 differ slightly from the cx23885. This patch modifies the cx23887 specific sram memory map to reflect this. As a result, interrupts and DMA handling have also been enabled in cx23885_start_dma() for 887 specific boards. ATSC streaming is now available on cx23885 and cx23887 bridges. Signed-off-by:
-
Steven Toth authored
I2C bus 3 was being initialised with the incorrect address register. Signed-off-by:
-
Michael Krufky authored
- fix #include for <media/video-buf-dvb.h> - fix cx23885_irq declaration for 2.6.19 and later Signed-off-by:
-
Michael Krufky authored
Signed-off-by:
-
Steven Toth authored
This is a new framework to support boards based on the CX23885/7 PCIe bridge. The framework supports digital (no analog yet) Signed-off-by:
-
Steven Toth authored
Signed-off-by:
-
Michael Krufky authored
Fix the following build warning: CC [M] cx25840-core.o cx25840-core.c: In function 'init_dll1': cx25840-core.c:147: warning: implicit declaration of function 'udelay' Signed-off-by:
-
Michael Krufky authored
Signed-off-by:
-
Michael Krufky authored
Signed-off-by:
-
Michael Krufky authored
Signed-off-by:
-
Michael Krufky authored
Signed-off-by:
-
Michael Krufky authored
Signed-off-by:
-
Michael Krufky authored
Add get_rf_strength function pointer to dvb_tuner_ops, so that rf signal strength can be read directly from the tuner driver by the dvb demodulator driver and / or the analog tuning system. This is an internal api addition -- userspace is not affected. Signed-off-by:
Manu Abraham <manu@linuxtv.org> Signed-off-by:
-
Michael Krufky authored
Break tuner.ko into separate modules. This was a quick change - Tuner sub-drivers are still static-linked to tuner.ko, this will change after using dvb_attach and removing the probing functions. After this change, one can deselect undesired tuner sub-drivers via Kconfig. Signed-off-by:
Hans Verkuil <hverkuil@xs4all.nl> Acked-by:
Mike Isely <isely@pobox.com> Acked-by:
Patrick Boettcher <pb@linuxtv.org> Acked-by:
Jarod Wilson <jwilson@redhat.com> Acked-by:
Trent Piepho <xyzzy@speakeasy.org> Signed-off-by:
-
Michael Krufky authored
Signed-off-by:
-
Michael Krufky authored
Signed-off-by:
-
Michael Krufky authored
Signed-off-by:
-
Michael Krufky authored
Signed-off-by:
-
Michael Krufky authored
Signed-off-by:
-
Michael Krufky authored
Prepare tuner-core for conversion of tuner sub-drivers into dvb_frontend modules Signed-off-by:
Oliver Endriss <o.endriss@gmx.de> Acked-by:
-
Michael Krufky authored
To ease the conversion of the analog tuner sub-drivers into dvb_frontend style tuner modules, we must remove the i2c_client interface. dvb_frontend style tuner modules use i2c_transfer directly on the i2c_adapter. This change only alters the interface between tuner.ko and the tuner sub-drivers. The v4l2 / i2c_client interface to tuner.ko remains intact. This patch adds inline functions tuner_i2c_xfer_send, and tuner_i2c_xfer_recv, to replace i2c_master_send and i2c_master_recv inside the tuner sub-drivers. Signed-off-by:
-
Michael Krufky authored
The tuner module has a rather aggressive range of possible i2c addresses. As per the specs available, it appears as if there are no 4-byte tuners that actually use i2c addresses in the range 0x64 thru 0x6f, yet, tuner-core claims the address range 0x60 thru 0x6f. Allowing tuner.ko to probe these addresses can cause potential damage to certain IR receivers, RTC chips or any other IC's that might otherwise reside on the i2c bus using one of these addresses. The plan is to remove these i2c addresses from the i2c address range of the tuner module. If any devices are discovered that actually do have tuners at one of these addresses, the newer i2c probing methods will be used to handle those cases. In order to collect this information and avoid any potential regressions, the following warning has been added upon successful detection of a tuner using an i2c address in the range 0x64 thru 0x6f: ====================== WARNING! ====================== Support for tuners in i2c address range 0x64 thru 0x6f will soon be dropped. This message indicates that your hardware has a {tuner name} tuner at i2c address {addr}. To ensure continued support for your device, please send a copy of this message, along with full dmesg output to v4l-dvb-maintainer@linuxtv.org Please use subject line: "obsolete tuner i2c address." ====================== WARNING! ====================== Signed-off-by:
-
