diff options
author | Sergei Shtylyov <sshtylyov@ru.mvista.com> | 2007-12-12 23:31:58 +0100 |
---|---|---|
committer | Bartlomiej Zolnierkiewicz <bzolnier@gmail.com> | 2007-12-12 23:31:58 +0100 |
commit | 809b53c4ef7188dc284498ef6e4ec2d4d587a275 (patch) | |
tree | 97f7ccd0330c67de092f0c2e84141dd68d94700f /drivers/media/dvb/dvb-core/dvb_net.c | |
parent | eadb6ecf761166aa55ad44f05b7a29b10ddaba34 (diff) |
hpt366: fix HPT37x PIO mode timings (take 2)
After looking into the HPT370 manual (now that I have it) and re-checking all
the timing tables, here's what I have discovered:
- at 33 MHz clock, PIO mode 0 timings turned to be overclocked, and all other
PIO modes underclocked;
- at 50 MHz clock, PIO modes 0 to 2 turned to be overclocked;
- at 66 MHz clock, PIO mode 0 was overclocked too.
Finally, the taskfile timing (matching PIO mode 0) turned to be overclocked at
all clock frequencies (and in all manuals)...
The new timings have been tested on HPT370 chip (at 33 MHz PCI clock) and on
HPT371N chip (at both 50 and 66 MHz DPLL clock).
Signed-off-by: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Signed-off-by: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Diffstat (limited to 'drivers/media/dvb/dvb-core/dvb_net.c')
0 files changed, 0 insertions, 0 deletions