As I definitely have artefacts with 64 but not with 128 (no wonder as SAA7164 demands at least 3750 ns), I want to ask if the code has been changed or will be changed.
I don't want to offend you, but you can easily find this out by yourself. Because I don't remember having put something like that into my original saa7146 driver from which the av7110 driver was split off,
I did this in the DVB tree:
michael DVB # grep -ir "latency" *
driver/av7110/saa7146_core.c: unsigned char latency;
driver/av7110/saa7146_core.c: /* Set PCI latency timer */
driver/av7110/saa7146_core.c: pci_read_config_byte(saa->device, PCI_LATENCY_TIMER, &latency);
driver/av7110/saa7146_core.c: if (latency != 64) {
driver/av7110/saa7146_core.c: printk(KERN_INFO "saa7146_core.o: adjusting pci latency to 64\n");
driver/av7110/saa7146_core.c: pci_write_config_byte(saa->device, PCI_LATENCY_TIMER, 64);
So, yes, it's still in there, and no, I don't know why this was added. Anyway, it's not in "dvb-kernel".
Currently I'm using "pre-install dvb-ttpci /usr/bin/setpci -d 1131:7146 latency_timer=80" in modules.conf, but this often fails if the driver is reloaded by any reason.
If noone objects within the next few days, IMHO this can be deleted. If anyone needs a different latency setting, it can be done via setpci just like you did.
It would be cool if you could prepare a patch then which can be applied to the DVB tree.
CU Michael.
-- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
