diff options
| author | Frank Schaefer <fschaefer.oss@googlemail.com> | 2013-03-03 15:37:43 -0300 |
|---|---|---|
| committer | Mauro Carvalho Chehab <mchehab@redhat.com> | 2013-03-04 16:29:40 -0300 |
| commit | 510e884c1abb86b060b895ffaf38ee1aac2e7fe4 (patch) | |
| tree | c57dc7c4193d44931dc5d15b957403a21d939310 /drivers/media/dvb-frontends/mb86a20s.c | |
| parent | a217968f919b0574ef59054430d8908aebcf0a35 (diff) | |
[media] em28xx: extract the device configuration dataset from eeproms with 16 bit address width
The new eeproms with 16 address width still have the the device config dataset
(the content of the old 8 bit eeproms) embedded.
Hauppauge also continues to include the tveeprom data structure inside this
dataset in their devices.
The start address of the dataset depends on the start address of the microcode
and a variable additional offset.
It should be mentioned that Camera devices seem to use a different dataset type,
which is not yet supported.
Tested with devices "Hauppauge HVR-930C". I've also checked the USB-log from the
"MSI Digivox ATSC" and it works the same way.
Signed-off-by: Frank Schäfer <fschaefer.oss@googlemail.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
Diffstat (limited to 'drivers/media/dvb-frontends/mb86a20s.c')
0 files changed, 0 insertions, 0 deletions