On 11/28/2009 11:31 AM, Michael Buesch wrote: > On Saturday 28 November 2009 18:12:20 Larry Finger wrote: >> Thanks for testing the other patch. To try to test the differences, >> I also dumped the PCI configuration writes and found one that wl does. >> >> Please see if this one helps. >> >> Larry >> >> ==================== >> >> >> Index: wireless-testing/drivers/ssb/driver_pcicore.c >> =================================================================== >> --- wireless-testing.orig/drivers/ssb/driver_pcicore.c >> +++ wireless-testing/drivers/ssb/driver_pcicore.c >> @@ -325,6 +325,8 @@ static void ssb_pcicore_fixup_pcibridge( >> ssb_printk(KERN_INFO "PCI: Fixing latency timer of device %s to %u\n", >> pci_name(dev), lat); >> pci_write_config_byte(dev, PCI_LATENCY_TIMER, lat); >> + >> + pci_write_config_dword(dev, 0x40, 0x6030001); >> } >> DECLARE_PCI_FIXUP_EARLY(PCI_ANY_ID, PCI_ANY_ID, >> ssb_pcicore_fixup_pcibridge); > > Uhm, this code is for embedded MIPS, only.
On my x86_64 system, I get the "Fixing latency ..." message printed out just before the code writes 0x40 to PCI-E configuration register 0x0d (PCI_LATENCY_TIMER). The wl driver does that same write on my machine. Do you have any knowledge as to why this number is increased from the default of 32? Larry _______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
