Messages in this thread | | | Date | Thu, 16 Mar 2000 13:02:57 +0100 | From | Martin Mares <> | Subject | Re: 2.4.x jobs (updated) |
| |
Hello!
> pci_set_master should have a per-architecture implementation to > do deal with issues, such as this one. > > For example, I may know that if I set the latency timer on a PCI > devices higher than X there is a bug which can be triggered to > lockup the PCI host bridge, and crap like this. > > It really should not be generic. > > Martin, want to cook up a patch for this?
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 pci_dev).
Have a nice fortnight -- Martin `MJ' Mares <mj@ucw.cz> <mj@suse.cz> http://atrey.karlin.mff.cuni.cz/~mj/ "My computer isn't that nervous, it's just a bit ANSI."
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |