> Yes, of course, but first of all I'd like to know what exactly the
> problems are. I dislike creating yet another architecture specific function
> -- I'd prefer to keep the function generic, but allow the architecture
> to set the right constants (either by macros in pci.h [which can be defined
> to call functions if needed, of course] or by adding a new entry in struct
Its chipset specific. For example setting the latency high on a SIS5598
board trashes your video because it holds off the video fetch from
For PC it should be a PCI quirk. Say we pick 64 as before and pci_quirk
overrides min_pci_latency and max_pci_latency ?
Would that work for you too Dave ?
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Mar 23 2000 - 21:00:19 EST