diff options
Diffstat (limited to 'v4l_experimental/pvrusb2/README')
| -rw-r--r-- | v4l_experimental/pvrusb2/README | 31 |
1 files changed, 26 insertions, 5 deletions
diff --git a/v4l_experimental/pvrusb2/README b/v4l_experimental/pvrusb2/README index dc93b7750..073491307 100644 --- a/v4l_experimental/pvrusb2/README +++ b/v4l_experimental/pvrusb2/README @@ -1,5 +1,5 @@ -$Id: README,v 1.1 2005/11/14 13:31:24 mchehab Exp $ +$Id: README,v 1.2 2006/01/01 08:26:03 mcisely Exp $ Mike Isely <isely@pobox.com> pvrusb2 driver @@ -132,13 +132,33 @@ Source file list / functional overview: (Policy, instantiation, and arbitration of pvrusb2 devices fall within the jurisdiction of pvrusb-context not here). - pvrusb2-i2c.[ch] - This module provides an implementation of a + pvrusb2-i2c-chips-*.c - These modules implement the glue logic to + tie together and configure various I2C modules as they attach to + the I2C bus. There are two versions of this file. The "v4l2" + version is intended to be used in-tree alongside V4L, where we + implement just the logic that makes sense for a pure V4L + environment. The "all" version is intended for use outside of + V4L, where we might encounter other possibly "challenging" modules + from ivtv or older kernel snapshots (or even the support modules + in the standalone snapshot). + + pvrusb2-i2c-cmd-v4l1.[ch] - This module implements generic V4L1 + compatible commands to the I2C modules. It is here where state + changes inside the pvrusb2 driver are translated into V4L1 + commands that are in turn send to the various I2C modules. + + pvrusb2-i2c-cmd-v4l2.[ch] - This module implements generic V4L2 + compatible commands to the I2C modules. It is here where state + changes inside the pvrusb2 driver are translated into V4L2 + commands that are in turn send to the various I2C modules. + + pvrusb2-i2c-core.[ch] - This module provides an implementation of a kernel-friendly I2C adaptor driver, through which other external I2C client drivers (e.g. msp3400, tuner, lirc) may connect and operate corresponding chips within the the pvrusb2 device. It is through here that other V4L modules can reach into this driver to operate specific pieces (and those modules are in turn driven by - glue logic here which is coordinated by pvrusb2-hdw, doled out by + glue logic which is coordinated by pvrusb2-hdw, doled out by pvrusb2-context, and then ultimately made available to users through one of the high level interfaces). @@ -176,10 +196,11 @@ Source file list / functional overview: ways. Note that **ALL** V4L functionality is published only through here and nowhere else. - pvrusb2-video.[ch] - This is glue logic that resides between this + pvrusb2-video-*.[ch] - This is glue logic that resides between this driver and the saa711x.ko I2C client driver (which is found elsewhere in V4L). Note that saa711x.ko used to be known as - saa7115.ko in ivtv. + saa7115.ko in ivtv. There are two versions of this; one is + selected depending on the particular saa711[5x].ko that is found. pvrusb2.h - This header contains compile time tunable parameters (and at the moment the driver has very little that needs to be |